Direction 

**************************************- 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.
**************************************-
 

**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-

Attribute Information

Used By

Attribute Group TransportationRoleGroup

Source 

<xs:attribute name="Direction" type="DirectionCodeType" use="optional">
  <xs:annotation>
    <xs:documentation>**************************************- 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. **************************************-</xs:documentation>
    <xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment copied from type definition **************************************-</xs:documentation>
  </xs:annotation>
</xs:attribute>

Sample