Generally the top-level structures will have a UID, and the other nodes can be reached with a path from there. So a UID plus path combination should make all features possible. It’s already recommended to set the uid on those top-level structures.
Setting an uid on all locatables is quite a lot of overhead. What are you trying to do that cannot be solved with a top-level UID plus a path? Regards, Pieter Bos Nedap Healthcare From: openEHR-technical <[email protected]> on behalf of Seref Arikan <[email protected]> Reply-To: For openEHR technical discussions <[email protected]> Date: Tuesday 13 December 2016 at 12:18 To: For openEHR technical discussions <[email protected]> Subject: Could the specs group consider making uid mandatory? Greetings, Apologies if I missed a discussion about this, but as per http://www.openehr.org/releases/RM/latest/docs/common/common.html#_unique_node_identification "LOCATABLE descendants may have a uid, containing a GUID" The optional/recommended nature of uid makes it impossible to implement some features that I have in mind because I can't rely on all implementations to follow the same approach. However I realise that making it mandatory could introduce compatibility issues with existing data so it is not simply making a decision and putting it into specs. Has this been discussed anywhere? All the best Seref _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
