HiLang 2.5.35

.NET Standard 2.0 This package targets .NET Standard 2.0. The package is compatible with this framework or higher. 
dotnet add package HiLang --version 2.5.35
                    


                    

                
NuGet\Install-Package HiLang -Version 2.5.35
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.35" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="HiLang" Version="2.5.35" />
                    


                            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.35
                    


                    

                
#r "nuget: HiLang, 2.5.35"
#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.35
#: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.35
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=HiLang&version=2.5.35
                    


                            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.35 0 2/27/2026
2.5.33 109 2/14/2026
2.5.32 95 1/30/2026
2.5.29 1,292 1/17/2026
2.5.28 3,005 12/31/2025
2.5.26 4,032 12/21/2025
2.5.21 6,215 12/10/2025
2.5.18 8,284 12/3/2025
2.5.8 7,772 11/15/2025
2.5.2 7,790 11/6/2025
2.5.1 7,766 10/23/2025
2.5.0 7,770 10/20/2025
2.4.6 7,786 9/23/2025
2.4.4 7,869 8/7/2025
2.4.2 7,749 7/28/2025
2.4.0 7,770 7/10/2025
2.3.8 7,757 7/1/2025
2.3.7 7,788 6/18/2025
2.3.4 7,780 6/5/2025
2.2.2 7,774 5/5/2025
Loading failed

https://www.cepheis.com/hiperspace/20260227
# Overview
## Cube Enhancements
A minor enhancement has been made to fully qualify references to **Hiperspace.Functions**. This prevents naming conflicts when a domain also uses **Functions**.

When one of a Cube’s **Dimensions** is `Node`, the `Node` view is added to the Cube along with `Edge` definitions that represent navigation between the **Dimension** and the Cube. In this release, the naming of these edges has been updated to ensure consistent navigation through a HiperGraph, using a common TypeName convention:

* TypeName `Cube:Drilldown` for navigation from a  *Dimension* to the *Cube*.
* TypeName `Cube:Dimension` for navigation from the *Cube* to a *Dimension*.

### Example
In the [Cube Example](https://github.com/channell/Hiperspace/blob/master/examples/Cube/Cube.hilang) ***Customer Sector*** and ***Product*** are *Dimensions* that can also be viewed as `Nodes`. The ***Contract Cube*** therefore has `Node` and `Edges` added as a views because.

[image]blogs/Blogs/Butterfly/product-model.png[/image]

* ***Contact*** (*Cube*) has one ***Account*** and ***Account*** has one ***Customer*** and ***Customer*** has one ***Sector*** (*Dimension*), it is inferred that  ***Sector*** is a *Dimension* of *Cube* ***Contact***.
*  ***Contact*** (*Cube*) has one ***Instrument*** and ***Instrument*** has one ***Product***, it is inferred that ***Product*** is a *Dimension* of *Cube* ***Contract***.

When viewed through a **HiperGraph** the *Cube* becomes a `Node` that links ***Sector*** *node* to ***Product*** *Node*

If you *drilldown* from ***Product*** to ***Contact_Cube*** and *drilldown* to ***Sector***, the shortest *HiperEdge* from ***Product*** to ***Sector*** is through the ***Contract_Cube*** slice that summarizes the connection between the two `Nodes`.  We call this combination of *HiperGraph* and *Cube* "*HiperCube*", and is useful for **AI** prompts like *"which sector uses most widgets?"*

[image]blogs/Blogs/Butterfly/product-graph.png[/image]