Re: AOM 1.4 - Archetype.uid a UUID or OID?

How about the idea of using the same UUID ofr the build_uid- and uid-property, but then extended with a version number? Giving a different UUID to the build_uid makes it impossible to a machine to relate the build_uid to the original archetype.uid. It seems that the build_uid is quite useless

Re: AOM 1.4 - Archetype.uid a UUID or OID?

On 16/06/2017 21:13, Bert Verhees wrote: UID can also be INTERNET_ID, and the "extension" and double colon are not required, so the HIER_OBJECT_ID cannot represent anything, but it is a lot. Of course it is a matter of taste, maybe there are good arguments to make the archetype.uid

Re: AOM 1.4 - Archetype.uid a UUID or OID?

On 16-06-17 21:12, Thomas Beale wrote: It's not correct to say that HIER_OBJECT_ID can represent anything. It can represent ids that are made of a UID root (either a UUID or OID or domain name or reverse domain name) and a String extension. While the String part could be abused, it isn't in

Re: AOM 1.4 - Archetype.uid a UUID or OID?

It's not correct to say that HIER_OBJECT_ID can represent anything. It can represent ids that are made of a UID root (either a UUID or OID or domain name or reverse domain name) and a String extension. While the String part could be abused, it isn't in properly built software. As can be seen

Re: AOM 1.4 - Archetype.uid a UUID or OID?

Wouldn't it be a good idea to have the build_uid of type HIER_OBJECT_ID, and have it the same UUID as the uid-property and behind the UUID the double colon and then the buildnumber? It would do right to the HIER_OBJECT_ID nature of being hierarchical in the way that it would represent a

Re: AOM 1.4 - Archetype.uid a UUID or OID?

I have a few thoughts, although the question has become less urgent to me, because I can use the HIER_OBJECT_ID to store a UUID. Which is a bit funny, but it is correct following the OpenEHR specs, so I can convince others that it is right. On 16-06-17 01:36, Heath Frankel wrote: No one

Re: AOM 1.4 - Archetype.uid a UUID or OID?

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

Re: AOM 1.4 - Archetype.uid a UUID or OID?

from here : 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/|,

Re: AOM 1.4 - Archetype.uid a UUID or OID?

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? Op 15 jun. 2017 19:41 schreef "Pablo Pazos"

Re: AOM 1.4 - Archetype.uid a UUID or OID?

In 1.4 the description of Archetype.uid saying "OID..." is incorrect. It should say "UID root with no extension". On Jun 15, 2017 7:50 AM, "Thomas Beale" wrote: > > On 15/06/2017 02:17, Heath Frankel wrote: > > Hi Thomas, > > Your statement that the use of

Re: AOM 1.4 - Archetype.uid a UUID or OID?

Hi Bert, when using ISO OIDs, UUIDs are not one arc OIDs since they have to start with a specific arc 1. or 2. http://www.oid-info.com/cgi-bin/display?tree= On Jun 15, 2017 4:33 AM, "Bert Verhees" wrote: > Although the OID and UUID as used in the archetypes are (in the

Re: AOM 1.4 - Archetype.uid a UUID or OID?

On 15-06-17 12:49, Thomas Beale wrote: On 15/06/2017 02:17, Heath Frankel wrote: Hi Thomas, Your statement that the use of HIER_OBJECT_ID in the AOM1.4 spec is used for OIDs is incorrect. HIER_OBJECT_ID is a complex type with a value attribute of type UID, which may be either UUID,

Re: AOM 1.4 - Archetype.uid a UUID or OID?

On 15/06/2017 02:17, Heath Frankel wrote: Hi Thomas, Your statement that the use of HIER_OBJECT_ID in the AOM1.4 spec is used for OIDs is incorrect. HIER_OBJECT_ID is a complex type with a value attribute of type UID, which may be either UUID, ISO_OID or INTERNET_ID. Right. I was

Re: AOM 1.4 - Archetype.uid a UUID or OID?

Although the OID and UUID as used in the archetypes are (in the most simple (one arc) OID-occurrence) technical interchangeable is their semantical meaning completely different. So what do we want to express here? Is it ever used in the way a OID is meant to be used? (to trace back the

RE: AOM 1.4 - Archetype.uid a UUID or OID?

Hi Thomas, Your statement that the use of HIER_OBJECT_ID in the AOM1.4 spec is used for OIDs is incorrect. HIER_OBJECT_ID is a complex type with a value attribute of type UID, which may be either UUID, ISO_OID or INTERNET_ID. The bigger issue is the HIER_OBJECT_ID is incompatible with UUID from

Re: AOM 1.4 - Archetype.uid a UUID or OID?

Never saw an OID in any tool I tested and I tested most of the open tools. I would say UUID is the industry standard here :) On Wed, Jun 14, 2017 at 5:09 PM, Thomas Beale wrote: > > Bert picked up an anomaly in this PR >