ical-bounces at lists.openehr.org] On Behalf Of Thomas
Beale
Sent: Wednesday, 15 August 2012 8:02 PM
To: openehr-technical at lists.openehr.org
Subject: Re: Should not node identifiers in runtime paths be mandatory?
On 15/08/2012 01:10, Heath Frankel wrote:
Hi Seref/Thomas,
Node IDs at0022 and
r-technical-bounces at lists.openehr.org] On Behalf Of Thomas
Beale
Sent: Wednesday, 15 August 2012 2:07 AM
To: openehr-technical at lists.openehr.org
Subject: Re: Should not node identifiers in runtime paths be mandatory?
On 14/08/2012 10:34, Seref Arikan wrote:
Greetings,
According to adl
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
ode in the instance to differentiate
> which alternative is being used.****
>
> ** **
>
> Heath
>
> ** **
>
> *From:* openehr-technical-bounces at lists.openehr.org [mailto:
> openehr-technical-bounces at lists.openehr.org] *On Behalf Of *Thomas Beale
> *Sent:* Wednesday
[mailto:openehr-technical-bounces at lists.openehr.org] On Behalf Of Thomas
Beale
Sent: Wednesday, 15 August 2012 2:07 AM
To: openehr-technical at lists.openehr.org
Subject: Re: Should not node identifiers in runtime paths be mandatory?
On 14/08/2012 10:34, Seref Arikan wrote:
Greetings,
Acco
On 14/08/2012 21:42, pablo pazos wrote:
> 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 a
tierrez
> Blog: http://informatica-medica.blogspot.com/
> Twitter: http://twitter.com/ppazos <http://twitter.com/ppazos>
>
> --
> Date: Tue, 14 Aug 2012 19:44:53 +0100
>
> From: thomas.beale at oceaninformatics.com
> To: openehr-technical at lis
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
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
linkedin.com/in/pablopazosgutierrez
Blog: http://informatica-medica.blogspot.com/
Twitter: http://twitter.com/ppazos
Date: Tue, 14 Aug 2012 19:44:53 +0100
From: thomas.be...@oceaninformatics.com
To: openehr-technical at lists.openehr.org
Subject: Re: Should not node identifiers in runtime pat
On 14/08/2012 10:34, Seref Arikan 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
e: Tue, 14 Aug 2012 17:37:02 +0100
From: thomas.be...@oceaninformatics.com
To: openehr-technical at lists.openehr.org
Subject: Re: Should not node identifiers in runtime paths be mandatory?
On 14/08/2012 10:34, Seref Arikan
wrote:
Greetings,
According
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
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 wh
14 matches
Mail list logo
