To comment on my own query: Section 5.3.12 of the same document says that node identifiers are mandatory for the case I've referred to in 5.3.6.3, but there is no explicit metion of runtime paths. So does this rule cover runtime paths too? I think it should, not due to ambiguity, but due to loss of semantics
Regards Seref On Tue, Aug 14, 2012 at 10:34 AM, Seref Arikan < serefarikan at kurumsalteknoloji.com> wrote: > Greetings, > According to adl 1.5 document on the openEHR web site (issued 25 Jan > 2012), Section 5.3.6.3, the runtime paths for single valued attributes can > omit node identifer. > The example given in the document uses miles per hour and km per hour > alternatives. The thing is, if the runtime path is what is going to be > persisted (and I can't see any other practical cases), the persisted data > will have no information to mark the semantics of the selection of an > option among alternatives. > > In case of a query such as get me all Xs where value is expressed as km > per hour, the system can not know what which option was used: kmph or mph, > because there is not node identifier. > In decision support/ machine learning use cases, having different units of > measurements would lead to mayhem etc etc. > > So there is a potential loss of information here, in exchange for > flexibility, but what is the use of that flexibility? Should not the node > identifier be mandatory in runtime paths when there is a decision among > alternatives? > > Kind regards > Seref > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120814/50305db0/attachment-0001.html>
