Ids for M3 Elements

[enikao]

Which ids are we using for M3 elements?

Option A: Use fully qualified name the element

Example: LIonCore.Concept

• Makes M2 serializations human-readable, as we know whether an entry is a Concept, Containment, etc.
• M3 ids never change (part of specification)
• Need to be the same in all implementations

Option B: Use arbitarily chosen ids

Examples: 23948723 or ALkdlkh-sdfkl_32

• In Repo API: Node IDs #31, we said that ids should not carry any meaning (i.e. should not be interpretable).
  We would violate our own guideline.

-> Decision: Option A (use FQNs)

[dslmeinte]

Experimentation in the TypeScript-implementation going on in PR #

[dslmeinte]

So, FQNs would be LIonCore.M3.Metamodel, LIonCore.M3.Concept, etc., right? (LIonCore.M3. is always the prefix.)

[enikao]

So, FQNs would be LIonCore.M3.Metamodel, LIonCore.M3.Concept, etc., right? (LIonCore.M3. is always the prefix.)

These are not valid ids (because of the dot).

[dslmeinte]

So, FQNs would be LIonCore.M3.Metamodel, LIonCore.M3.Concept, etc., right? (LIonCore.M3. is always the prefix.)

These are not valid ids (because of the dot).

Where did we document the criteria of valid IDs again?

[enikao]

Where did we document the criteria of valid IDs again?

#31

[dslmeinte]

OK, I fixed the invalid IDs in LionWeb-io/lionweb-typescript#25

[enikao]

OK, I fixed the invalid IDs in LIonWeb-org/lioncore-typescript#25

For the record: This PR implies the FQNs would be like LIonCore_M3_Metamodel_qualifiedName

[enikao]

All ids are listed at https://github.com/LIonWeb-org/organization/blob/main/lioncore/metametamodel.adoc#ids-of-m3-elements (after #79 merged)