**************************************- Maintenance: DF/2003-11-13: Comment corrected **************************************- Used to qualify transportation segments (both in Requests and Responses) or application rules (such as for stops) types and direction are tightly linked together: One Ways are always Outbound (but it is not required to specify it) The other types can combine Outbound and Inbound sub segments. If all segments are expressed on the same level, the tree can still be created through the use of references. Both = Inbound and Outbound. This is usually used in rules, not in segments **************************************- |
<xs:simpleType name="DirectionCodeType"> <xs:annotation> <xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment corrected **************************************- Used to qualify transportation segments (both in Requests and Responses) or application rules (such as for stops) types and direction are tightly linked together: One Ways are always Outbound (but it is not required to specify it) The other types can combine Outbound and Inbound sub segments. If all segments are expressed on the same level, the tree can still be created through the use of references. Both = Inbound and Outbound. This is usually used in rules, not in segments **************************************-</xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="Both"/> <xs:enumeration value="Inbound"/> <xs:enumeration value="NotApplicable"/> <xs:enumeration value="Outbound"/> </xs:restriction> </xs:simpleType> |