Darrel,
Here is an example from TEP on setting up the default values.
In main body of TEP …
<xs:choice>
<xs:element
name="gender"
type="ct:ValueKeyType"/>
<xs:element
name="genderDefault"
type="ctep:GenderDefaultType"/>
… note that there is a separate namespace for common TEP types which are in another xsd file…
</xs:choice>
In associated TEP Defaults file …
<xs:simpleType
name="GenderDefaultValues">
<xs:restriction
base="ct:ValueType">
<xs:enumeration
value="Male"/>
<xs:enumeration
value="Female"/>
<xs:enumeration
value="Unknown"/>
</xs:restriction>
</xs:simpleType>
I would suggest this for HAVE…
<xs:element
name="code"
type="ServiceCodeDefaultType"/>
…
<xs:simpleType
name=" ServiceCodeDefaultType
">
<xs:restriction
base="ct:ValueType">
<xs:enumeration
value="value1"/>
<xs:enumeration
value="value2"/>
<xs:enumeration
value="value3"/>
</xs:restriction>
</xs:simpleType>
Brian M Wilkins
From: emergency-have@lists.oasis-open.org [mailto:emergency-have@lists.oasis-open.org]
On Behalf Of Darrell O'Donnell
Sent: Tuesday, July 02, 2013 1:58 PM
To: HAVE SC
Subject: [emergency-have] 4PM EDT - OASIS EDXL HAVE meeting
Folks - looking forward to today's meeting at 4PM EDT (1PM PDT). The schema is largely complete with only minor work on establishing some default values - I need some guidance on that to make sure I get it done
correctly.
Largely I would like to focus on feedback from the schema (and associated PDF) that I circulated 2 weeks ago. If we are all largely in agreement we can transition to getting the standard doc going and push out HAVE
2.0!
cheers,
Darrell
--
Darrell O'Donnell, P.Eng.
OASIS Member (volunteer) -
www.oasis-open.org
OASIS EM TC, RIM SC - Member
OASIS EM HAVE SC - Co-Chair
