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 <[email protected]> wrote: > > Bert picked up an anomaly in this PR > <https://openehr.atlassian.net/browse/SPECPR-219> that I think should > probably be fixed. ARCHETYPE.uid is of type UUID in the AOM2 spec, but of > type HIER_OBJECT_ID in the AOM1.4 spec (the latter type is the openEHR type > for OIDs). However it appears that all ADL1.4 archetypes that have a uid > have it as a Guid (i.e. UUID), and I assume the various tools do as well. > We avoid Oids like the plague in openEHR, and I am not aware of them being > used anywhere. > > If we can verify that everything assumes a UUID for this field, then the > spec is wrong, and we should update it from 1.4.2 to 1.4.3, i.e. treat this > as an error correction. > > Could tool makers check this issue and report here? > > thanks > > - thomas > > -- > Thomas Beale > Principal, Ars Semantica <http://www.arssemantica.com> > Consultant, ABD Team, Intermountain Healthcare > <https://intermountainhealthcare.org/> > Management Board, Specifications Program Lead, openEHR Foundation > <http://www.openehr.org> > Chartered IT Professional Fellow, BCS, British Computer Society > <http://www.bcs.org/category/6044> > Health IT blog <http://wolandscat.net/> | Culture blog > <http://wolandsothercat.net/> > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org > -- Ing. Pablo Pazos Gutiérrez Cel:(00598) 99 043 145 Skype: cabolabs <http://cabolabs.com/> http://www.cabolabs.com [email protected] Subscribe to our newsletter <http://eepurl.com/b_w_tj>
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
