HiLang 2.5.43

dotnet add package HiLang --version 2.5.43
                    
NuGet\Install-Package HiLang -Version 2.5.43
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="HiLang" Version="2.5.43" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="HiLang" Version="2.5.43" />
                    
Directory.Packages.props
<PackageReference Include="HiLang" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add HiLang --version 2.5.43
                    
#r "nuget: HiLang, 2.5.43"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package HiLang@2.5.43
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=HiLang&version=2.5.43
                    
Install as a Cake Addin
#tool nuget:?package=HiLang&version=2.5.43
                    
Install as a Cake Tool

HiLang

HiLang is a minimal high-level language to describe the schema of a domain, taking inspiration from protobuf (.proto models) for hierarchical structures and SQL DML for entities, relations and views.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on HiLang:

Package Downloads
Hiperspace.SQL

Package Description

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.5.43 48 4/1/2026
2.5.39 104 3/20/2026
2.5.35 127 2/27/2026
2.5.33 721 2/14/2026
2.5.32 2,588 1/30/2026
2.5.29 3,951 1/17/2026
2.5.28 5,666 12/31/2025
2.5.26 6,690 12/21/2025
2.5.21 8,879 12/10/2025
2.5.18 10,941 12/3/2025
2.5.8 10,428 11/15/2025
2.5.2 10,447 11/6/2025
2.5.1 10,421 10/23/2025
2.5.0 10,430 10/20/2025
2.4.6 10,445 9/23/2025
2.4.4 10,526 8/7/2025
2.4.2 10,402 7/28/2025
2.4.0 10,428 7/10/2025
2.3.8 10,412 7/1/2025
2.3.7 10,441 6/18/2025
Loading failed

https://www.cepheis.com/hiperspace/20260401
# Overview
This release includes minor enhancement to the graph functionality when used with **Hiperspace.DB** graph view.  **Hiperspace.DB** provides a *graph* view that aggregates alll databases, so that graph shows all connections both local and foreign.   In the following example *Togaf.Has.WorkPackage*  includes a value *ProjectKey* that could be a stringified `SKey` reference to a project plan in another database.  When the *project* is viewed as a graph in  **Hiperspace.DB**, the graph includes paths between a *project plan* and *strategic goals*.

```
segment Togaf.Has.WorkPackage : Togaf.Base
   = Node        ( SKey = SKey, Name = Name, TypeName = "AF-WorkPackage"),
     Edge        (From = owner, To = this, Name = Name, TypeName = "AF-Has-WorkPackage"),
     Togaf.Edge_ (To = owner, From = this, Name = Name, TypeName = "AF-WorkPackage-For"),
     Togaf.Edges (From = this, To = Project, Name = Name, FromTypeName = "AF-WorkPackage-Plan", ToTypeName = "AF-Plan-WorkPackage"),
     Graph.HiperEdge = StrategicEdges #2675
{
   ProjectKey      : String #29
}
[
   "All Togaf.Edges that can be projected as Transitative Togaf.Edges to a Business Goal"
   @Once
   StrategicEdges  = StrategicEdge(this),
   Project         = externalnode(ProjectKey)
];
```
For efficiency, the `SKey` property has been changed from a [Base64](https://en.wikipedia.org/wiki/Base64) encoding of the *key* to add the option of a database prefix.  The `Node SKey` "Togaf.ascxyz==" will only search for matching items "abcxyz==" in the *Togaf* database.  Within the *Togaf* database, only the specific segment is searched because the *key* includes the `#Id` of the element set.

the following SQL query would return a table of all *project plans* and *Goals* that can be reached through the {component, service, function, process, capability, etc} that are in some way associated with the *Work Package*
```
SELECT project.Name AS "Project Name"
    , goal.Name AS "Goal Name"
    , project.SKey as "Project Id"
    , goal.SKey as "Goal Id"
FROM   Nodes as project
    , project.Tos as planedge
    , planedge.To as workpackage
    , workpackage.Tos as workedge
    , workedge.To as goal
WHERE  project.TypeName = 'Plan'
 AND  planedge.TypeName = 'AF-Plan-WorkPackage'
 AND  workpackage.TypeName = 'AF-WorkPackage'
 AND  workedge.TypeName = 'Strategic-Goal'
 AND  goal.TypeName = 'AF-Goal';
```
NB the five table join uses *implicit* joins in  `Hiperspace.SQL` because `project.Tos` and `workpackage.Tos` are `Set<Edge>` properties that are *implicitly* filtered by the source `Node`