Hi Seref,
Not sure I understand your point anymore.
The quote you have reference seems to indicate that it is part of a greater
explanation of the purpose of node ID. Semantics is one, and as a
distinguisher is another. For me, the speed limit example is the second and
because DV_QUANTITY has
Hi Thomas,
I actually didn't even consider the fact that DV_QUANTITY didn't have a node
ID property, but good point. My point was that the units property provides
the information required to determine if a speed limit value was mph or
km/h.
Not sure I like the idea of adding the property
Hi Heath,
Maybe semantics is not the right word for it, but it is what would help
me/my code easily express that the interest is in a particular element,
given a bunch of options. The lack of node identifier is thus at least lack
of information, if not semantics.
Not to suggest that you're wrong
On 15/08/2012 01:10, Heath Frankel wrote:
Hi Seref/Thomas,
Node IDs at0022 and at0023 have no semantic significance, they are
just a value of a speed limit element no matter if they are in km/h or
mph. These are just alternative value constraints on the value due to
different units
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
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
Hi Thomas,
Just thinking...
Why not make node ID mandatory for all nodes?
Since this will be handled by tools, I don't see the point of having to worry
about if the node has an id or not: the tool just put some node ID on each node
and us as developers use that fact to query and process data.
On 14/08/2012 18:46, pablo pazos wrote:
Hi Thomas,
Just thinking...
Why not make node ID mandatory for all nodes?
Since this will be handled by tools, I don't see the point of having
to worry about if the node has an id or not: the tool just put some
node ID on each node and us as
Thank Tom,
Somehow the text gave me the impression that use of archetype Node Id was
optional, which is clearly not the case.
Kind regards
Seref
On Tue, Aug 14, 2012 at 5:37 PM, Thomas Beale
thomas.beale at oceaninformatics.com wrote:
On 14/08/2012 10:34, Seref Arikan wrote:
Greetings,
Hi Thomas, thanks for the answer. (now I see the problem of doublign the number
of node ids)
I understood the Seref's problem as a case that could not be decided
automatically by a system, i.e. when to use and when not use the nodeID to
query and to get the desired node.
Re-reading your
10 matches
Mail list logo
