https://openehr.atlassian.net/projects/SPECPR/issues/SPECPR-91?filter=allopenissues
On 13/12/2016 23:01, Boštjan Lah wrote:
On 13 Dec 2016, at 12:36, Thomas Beale <[email protected]> wrote:
On 13/12/2016 22:27, Pieter Bos wrote:
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.
that's pretty much the view we have on this to date...
- thomas
There was a discussion about introducing an additional identifier for nodes
besides UID, something lighter.
Current generation of paths to uniquely identify an element within a
composition is difficult and it became even more difficult when name uniqueness
was dropped.
Think of identifying a specific POINT_EVENT in a HISTORY.
There was a suggestion to use other attributes, for example for POINT_EVENT it
would be 'time' but this makes things even worse as one would need to use
different attribute depending on the node type.
I would welcome the idea of having some kind of lightweight identifier on every
node in order to make unique path generation easier.
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
