Component Identification
Revision as of 06:45, 13 October 2015 by Tuukka Lehtonen (talk | contribs) (Created page with "= Basic concepts = == Rationale == TODO: unique identifiers for entities like structural components, really making sure that an entity is the same as another in distributed...")
Contents
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.
TODO
