My preferred scenario would be to have an identifier on every node indeed. Not having that, I could live with identifiers for at least some types, such as entry subtypes and a few more. If it cannot be UID, so be it.
What is the meaning of overhead here? Processing time? Memory/disk space? According to which criteria the overhead is quantified as "quite a lot"? You can see I'm not really convinced here :) On Tue, Dec 13, 2016 at 12:01 PM, Boštjan Lah <bostjan....@marand.si> wrote: > > > On 13 Dec 2016, at 12:36, Thomas Beale <thomas.be...@openehr.org> 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. > > Bostjan > > > > >> > >> What are you trying to do that cannot be solved with a top-level UID > plus a path? > >> > > > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical@lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
