Difference between revisions of "Component Identification"

From Developer Documents
Jump to navigation Jump to search
Line 22: Line 22:
 
</pre>
 
</pre>
 
* The version identifier is a binary GUID and its values can be handled using the utility bean class <code>org.simantics.datatypes.literal</code>.
 
* The version identifier is a binary GUID and its values can be handled using the utility bean class <code>org.simantics.datatypes.literal</code>.
* Identifiers are only given to structural configuration components in a model configuration.
+
* Identifiers are only given to structural configuration components in a model configuration, not diagram elements. This makes it possible to perform global comparisons between versions of a model.
  
 
  TODO
 
  TODO

Revision as of 06:47, 13 October 2015

Basic concepts

Rationale

TODO: unique identifiers for entities like structural components, really making sure that an entity is the same as another in distributed team work

Use cases

TODO
  • Management of shared modelling concepts using export/import or shared repository
  • Full-featured inspection of old versions
  • Version comparison analysis tools

Technical details

  • A unique identifier can be attached to any resource with the L0.identifier relation:
    >-- L0.identifier <R L0.HasProperty : L0.FunctionalRelation
        L0.HasLabel "Identifier"
        --> L0.GUID
  • The version identifier is a binary GUID and its values can be handled using the utility bean class org.simantics.datatypes.literal.
  • Identifiers are only given to structural configuration components in a model configuration, not diagram elements. This makes it possible to perform global comparisons between versions of a model.
TODO

Examples

Open Questions