Thomas and Koray,
The Operational Template XML schema used by the Ocean Template Designer has
a view constraints element, which is a sibling of the description and
definition elements. It is used to represent the Template Designer's hide
on form property (labelled more generically as pass_through in the OPT view
constraints). This was designed to support GUI (and other view) directives.
The type of the view element is defined as follows.
<xs:complexType name="T_VIEW">
<xs:sequence>
<xs:element name="constraints" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="items" maxOccurs="unbounded" >
<xs:complexType>
<xs:sequence>
<xs:element name="value" type="xs:anySimpleType"/>
</xs:sequence>
<xs:attribute name="id" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="path" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
An example of its use is below.
<view>
<constraints path="/context/other_context[at0001]">
<items id="pass_through">
<value>true</value>
</items>
</constraints>
<constraints path="/context/other_context[at0001]/items[at0002]">
<items id="pass_through">
<value>true</value>
</items>
</constraints>
...
</view>
Regards
Heath Frankel
Product Development Manager
Ocean Informatics
From: [email protected]
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Thomas Beale
Sent: Thursday, 30 December 2010 10:40 AM
To: openehr-technical at openehr.org
Subject: Re: Archetype & Template ANNOTATIONS - requirements?
On 29/12/2010 23:53, Koray Atalag wrote:
Hi Tom, a very comprehensive set of questions to determine the
requirements...
I will provide my point by point feedback shortly but I have one
objection/suggestion re using annotations for GUI matters.
As name implies annotations seem to me something for the humans; providing
context and additional information about a particular data point. Exploiting
this section for GUI generation which will be consumed by GUI
tools/generators do not seem all too appropriate to me. What I have in mind
is a separate section for GUI Directives or at least introduce a reserved
keyword for this purpose within annotations section. I think that'll ensure
more consistent and safe implementations by different groups. Both support
your points about tag standardisation...
Hi Koray,
the annotations section is not connected with GUI directives. I think we are
all agreed they will be in a completely separate artefact.
- thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101230/8dfce5e9/attachment.html>
