The standard library contains classifiers Node and INamed, and primitive types Boolean, String, Integer

Contents

Known issues

M3 (lioncore.json) Mismatched child vs. node id

Details: lioncore.json: Mismatched child vs. node id -id-Classifier-features-2024-1 #412

-id-Classifier-features-2024-1

lioncore.json line 1484 mentions id -id-Classifier-features-2024-1 as child.

"containments": [
  {
    "containment": {
      "language": "LionCore-M3",
      "version": "2024.1",
      "key": "Classifier-features"
    },
    "children": [
      "-id-Classifier-features-2024-1"
    ]
  }
],

However, the intended child node id in line 1515 spells -id-Classifier-feature-2024-1 (singular "feature").

{
  "id": "-id-Classifier-feature-2024-1",
  "classifier": {
    "language": "LionCore-M3",
    "version": "2024.1",
    "key": "Containment"
  },

They both MUST be the same, i.e. -id-Classifier-features-2024-1.

-id-Language-dependsOn-2024-1

lioncore.json line 1816 mentions id -id-Language-dependsOn-2024-1 as child.

"containments": [
  {
    "containment": {
      "language": "LionCore-M3",
      "version": "2024.1",
      "key": "Classifier-features"
    },
    "children": [
      "-id-Language-version-2024-1",
      "-id-Language-dependsOn-2024-1",
      "-id-Language-entities-2024-1"
    ]
  }
],

However, the intended child node id in line 1848 spells -id-Language-dependsO-2024-1 (missing "n" at the end of "dependsOn").

{
  "id": "-id-Language-dependsO-2024-1",
  "classifier": {
    "language": "LionCore-M3",
    "version": "2024.1",
    "key": "Reference"
  },

They both MUST be the same, i.e. -id-Language-dependsOn-2024-1.

-id-IKeyed-key-2024-1

lioncore.json line 2129 mentions id -id-IKeyed-key-2024-1 as child.

"containments": [
  {
    "containment": {
      "language": "LionCore-M3",
      "version": "2024.1",
      "key": "Classifier-features"
    },
    "children": [
      "-id-IKeyed-key-2024-1"
    ]
  }
],

However, the intended child node id in line 2152 spells -id-IKeyed-key (missing "-2041-1" suffix).

{
  "id": "-id-IKeyed-key",
  "classifier": {
    "language": "LionCore-M3",
    "version": "2024.1",
    "key": "Property"
  },

They both MUST be the same, i.e. -id-IKeyed-key-2024-1.

Misspelling of “data type”

The official, correct spelling of “data type” is as two words. Version 2024.1 of the serialization specification uses “datatype” in various places. This has been left in as this version has been published.

Meta-metamodel: Inconsistent stability claims for pre-defined keys and resolveInfos

Issue

The language hosting built-in elements has id and key LionCore-builtins[1], its name is LionCore_builtins[2].

Every language implicitly depends on this language.[3] Thus, the ids in this language MUST be stable. This means the id MUST be identical to the key for each node in this language.

— Meta-metamodel
section Keys and resolveInfos of built-in elements

This contradicts Meta-metamodel doc, section 3.4 Pre-defined keys and resolveInfos on the value of pre-defined node ids:

We can serialize languages as regular nodes. To keep the serialized form of the language compatible with multiple LionWeb versions, we SHOULD serialize references to M3 elements and builtins without target reference id, and include the resolveInfo as listed in this section.[4]

— Meta-metamodel
section Pre-defined keys and resolveInfos

Correction

Section 3.4 is correct. We revised section 3.4.2, and added clarifications at the end of sections 3.4 and 3.5.

The revised sections read:

3.4 Pre-defined keys and resolveInfos

We can serialize languages as regular nodes. To keep the serialized form of the language compatible with multiple LionWeb versions, we SHOULD serialize references to M3 elements and builtins without target reference id, and include the resolveInfo as listed in this section.[4]

We aim at keeping pre-defined keys and resolveInfos stable over different LionWeb versions. The ids of pre-defined elements are NOT stable, but CAN differ between LionWeb versions.[4]

3.4.1 Keys and resolveInfos of built-in elements

The language hosting built-in elements has key LionCore-builtins[1], its name is LionCore_builtins[2].

3.5 Built-in elements

Each LionWeb implementation ships with a set of built-in elements, akin to a standard library.[2] These elements are part of the M2 language LionCore_builtins. It can be used in any user-defined Language.[5] Every language implicitly depends on this language.[3]

Diagram

1. Key of builtin stdlib #141
2. Change builtins language name? #195
3. Discussion on implicitly importing stdlib
4. Make LionCore M3 and builtins language definitions have version-dependent IDs #279
5. Metalevel of builtin standard library #196