| Issue 2: | phone element |
1 of 31
Next ›
|
| 1 person starred this issue and may be notified of changes. | Back to list |
The phone element is actually used as an integer type, however maybe the users want to write a phone number compound not only by numbers.
Example:
5555555 ext. 1234
+57 (2) 2222222 ext. 1111
this line:
<xs:element name="phone" type="xs:integer">
should be replaced by:
<xs:element name="phone" type="xs:string">
There is another problem here. In the official EML Schema the phone element has a complex type and its data type extends of string.
<xs:element name="phone" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="phonetype" type="xs:string" use="optional" default="voice">
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
But in the GBIF Schema, the data type is directly expressed.
<xs:element name="phone" type="xs:string">
</xs:element>
Should I add this corrections too?
by the way, we are not using the attribute named "phonetype". This can be ommitted. right?
Sep 24, 2010
Project Member
#1
htobon
Owner:
wixner
Sep 27, 2010
as we dont use the phonetype we can stick with the simple xs:string type. All the complextype in the original does is adding the optional phonetype attribute
Status:
Invalid
Labels: -Type-Defect
Sep 27, 2010
set status wrong. Its still an issue to change it to xs:string
Status:
Accepted
|