First reaction, I need to reread your reply carefully. We also have an MD5 key as part of the archetype to detect changes. What does the build_uid add to this? I discovered that the template - editor uses the MD5 key for that purpose.
But I come back to this tomorrow. Bert Op vr 16 jun. 2017 00:24 schreef Thomas Beale <[email protected]>: > from here > <http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_machine_identifiers> > : > > Two machine identifiers are defined for archetypes. The ARCHETYPE.*uid* > attribute > defines a machine identifier equivalent to the human readable ARCHETYPE. > *archetype_id*.*semantic_id* , i.e. ARCHETYPE_HRID up to its major > version, and changes whenever the latter does. It is defined as optional > but to be practically useful would need to be mandatory for all archetypes > within a custodian organisation where this identifier was in use. It could > in principle be synthesised at any time for a custodian that decided to > implement it. > > The ARCHETYPE.*build_uid* attribute is also optional, and if used, is > intended to provide a unique identifier that corresponds to any change in > version of the artefact. At a minimum, this means generating a new UUID for > each change to: > > - > > ARCHETYPE.*archetype_id*.*release_version*; > - > > ARCHETYPE.*archetype_id*.*build_count*; > - > > ARCHETYPE.*description*.*lifecycle_state*. > > For every change made to an archetype inside a controlled repository (for > example, addition or update of meta-data fields), this field should be > updated with a new UUID value, generated in the normal way. > - thomas > > > On 15/06/2017 23:09, Bert Verhees wrote: > > Seems that the story is not finished yet. Someone in a project I work made > the joke to rename HIER_OBJECT_ID to ANY_KIND_OF_ID, because it can > represent almost any type of id. > > What is the official defined purpose of the Archetype.uid property? > > > _______________________________________________ > openEHR-technical mailing list > [email protected] > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
