<complexType name="PointOfInterestType">
<annotation>
<appinfo source="ADT.xsd" />
</annotation>
<complexContent>
<extension base="xls:AbstractPOIType">
<sequence>
<annotation>
<documentation> We need to look more closely at this choice block (it's too restrictive). Since we don't have a getCapabilities, there is really no way that a client can discover the information a Directory Service could possibly return. Also, clients have no way to specify which of these information types they want returned (ReferenceSystem, POIInfoList, Point, and/or Address), like we do for GeoCode. Plus, when a Directory Service has two or more of these types, with the choice block there is no way for the a client to receive the full information set. Do we want to change this to a sequence block and/or change POIAttributeList and/or Point to optional? Also, we need to examine the role of POI in this form since it may not return a Point or Address and therefore may not have sufficient info to be used in location services that require a position of some sort.
[MM] 17/3/03. Made the change from a choice block to a sequence block. Made the elements optional inside the sequence block
</documentation>
</annotation>
<element ref="xls:POIAttributeList" minOccurs="0" />
<element ref="gml:Point" minOccurs="0" />
<element ref="xls:Address" minOccurs="0" />
<!-- ref="xls:Point"/> -->
</sequence>
<attribute name="ID" type="string" use="required" />
<attribute name="POIName" type="string" use="optional" />
<attribute name="phoneNumber" type="string" use="optional" />
<attribute name="description" type="string" use="optional" />
</extension>
</complexContent>
</complexType>
|
XSD Schema Diagram:
