Hi Tom and Erik,
that's two innovative ideas in one post - you must have had a great
christmas ;-)
1. in the 'languages' space, allow formalisms as well - e.g. "rdf"
2. the annotation structure, simple as it is, is in fact sufficient (or
close) to support representation of RDF-like triples.
[HKF: ] I think we are overloading the use of the annotations for two
different purposes and should look at the distinction made in XML Schema
where they have documentation and appinfo, where the former is used by
humans and the later by applications for things such as GUI directives.
I can't really comment on these ideas other than to say they look quite
interesting - I had not thought of either before. The main decision for the
ADL 1.5 spec and implementation is: whether to stick with annotations as a
hash of Strings, with String keys, or to make the keys some kind of codes,
defined elsewhere in the archetype. At the moment I am inclined to leave it
as all Strings, let people experiment with it, and decide to enhance it once
people have messed around with it.
[HKF: ] I agree with this (as per my other email)
Maybe Koray and other implementers might want to work on some of their own
ideas, plus Erik's, within some archetypes. The next ADL workbench beta (any
day now) will support String-only annotations, arranged per language as
shown in an earlier post. We don't have an XML version of this yet, and
would rather hold off on the XML version until we are more slid with the ADL
version. But - advice, disagreement from others is welcome (or even better
if others want to mess around with the XML on their own and feed it back in
here).
[HKF: ] The Operational Template XML schema used by the Ocean Template
Designer defines an annotations element, which is a sibling of the
description and definitions elements. The type of the annotations element
is defined as follows where the StringDictionaryItem is defined in the
existing openEHR Resource.xsd.
<xs:complexType name="ANNOTATION">
<xs:sequence>
<xs:element name="items" type="StringDictionaryItem"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="path" type="xs:string" use="required"/>
</xs:complexType>
Regards
Heath Frankel
Product Development Manager
Ocean Informatics
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110104/180b7ed8/attachment.html>
