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

Contents

  • Serialization format html pdf

  • Meta-metamodel html pdf

  • Bulk Repository Access API html pdf

  • Delta Repository Access API html pdf

Known issues

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