Hello,
I'm trying to figure out which reference model Ocean's achetype editor follows.
I have an example regarding the data type Quantity, see below. There seems to
be great differences depending on what reference model the archetypes follow.
Background:
I'm trying to figure out how to get the property of a quantity but this doesn't
seem to be supported by the java kernel I'm using, so I'm asking if anyone has
a good idea on how to support this in other ways.
The current problem is that the java adl parser returns a CQuantity object
whenever it recognizes the string "quantity", but when it's something else,
e.g. C_QUANTITY, it returns a CComplexObject.
Idea:
I could solve this by looking up the RM type names and the attribute names to
figure out if the ComplexObject represents something that can be interpreted as
a Quantity data type. In this way I can support the various known structures of
the data type that currently exist. Any suggestions?
By the way, shouldn't the property attribute represent a CODED_TEXT object that
can be linked to a local or external terminology? This seems to be the case
according the specifications and it goes all the way back to version 0.9 that I
think the current version of the java kernel supports (partly at least). I
would really like to know what RM Ocean's archetypes follows.
Ocean Archetype Editor archetype:
C_QUANTITY <
property = <"Acceleration">
list = <
["1"] = <
units = <"cm/s2">
magnitude = <|< 0.0|>
>
["2"] = <
units = <"ft/s2">
magnitude = <|>= 0.0|>
>
>
>
>
Ref impl java kernel archetype:
QUANTITY matches {
magnitude matches {|<0.0|}
units matches {"cm/s2"}
}
Acode ADLParser test achetype:
REAL_QUANTITY matches {
property matches {"Acceleration"}
units cardinality matches {1} matches {
UNIT matches {
unit_string matches {"cm/s2"}
magnitude matches {|< 0.0|}
}
UNIT matches {
unit_string matches {"ft/s2"}
magnitude matches {|>= 0.0|}
}
}
}
Regards,
Mattias Forss
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051114/6a5af7f2/attachment.html>
