Thinking a little about node identifiers I have thought some
problematic use cases.
First, this is the current 'rule' in the wiki
(http://www.openehr.org/wiki/pages/viewpage.action?pageId=196633) for
when node identifiers are really needed. I copy the relevant part for
ease the discussion:
On 08/27/2013 07:20 PM, Diego Bosc? wrote:
Do we need at-codes when
we create siblings such as DV_TEXT and DV_CODED_TEXT?
In which circumstance can a sibling occur of a DataValue? Certainly not
in an ELEMENT.
I either cannot imagine another circumstance.
So why use a node-value? Write a nodeId
:(
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130827/5aaedc44/attachment.html
Good to know. I think the only remaining issue could be the one to
confirm if a specialized object should always have at-code.
And regarding use_node, I would also add that you have to be careful
not to create an internal reference from a sibling (and if you do then
you MUST put an at-code)
On 27/08/2013 18:20, Diego Bosc? wrote:
The problem with this rules come with the (explicit or implicit)
specialization of single attributes. take this example:
ELEMENT[at0009] occurrences matches {0..1} matches { -- Position
value existence matches
I don't think archetype ontology would be more complicated at all.
There are currently archetypes with different set of properties in
each at code and tools can handle it well (if I remember correctly,
NEHTA archetypes have extra properties). I'm pretty sure tools are
currently robust enough to
--
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130827/a0860ddd/attachment.html
-- next part --
A non-text attachment was scrubbed...
Name: ocean_full_small.jpg
Type: image/jpeg
Size
on the opposite premise.
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130827/cf4326ee/attachment.html
8 matches
Mail list logo