TransportationRoleGroup 

To qualify the role of the transportation, such as Feeder
Outbound

Attribute Group Information

Attributes

QName Type Fixed Default Use Inheritable Annotation
Category TransportationCategoryCodeType optional
Direction DirectionCodeType optional 
**************************************- 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
**************************************-
Role TransportationRoleCodeType optional
Type TransportationTypeCodeType optional 
**************************************- to express in Requests or
Responses whether transportation is One way, return or more complex Type and
Direction are tightly linked data : A return flight has 2 directions for
instance. **> OneWay and return are obvious **> Circular is a multi leg
circular trip **> Complex is a multi leg trip in general (From To From To2
From To3 To4 From) would qualify for a complex non circular trip **> World is
for Round the World trips **************************************-
 
**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-

Used By

Complex Type SegmentTransportationType

Source 

<xs:attributeGroup name="TransportationRoleGroup">
  <xs:annotation>
    <xs:documentation>To qualify the role of the transportation, such as Feeder Outbound</xs:documentation>
  </xs:annotation>
  <xs:attribute name="Type" type="TransportationTypeCodeType" use="optional">
    <xs:annotation>
      <xs:documentation>**************************************- to express in Requests or Responses whether transportation is One way, return or more complex Type and Direction are tightly linked data : A return flight has 2 directions for instance. **> OneWay and return are obvious **> Circular is a multi leg circular trip **> Complex is a multi leg trip in general (From To From To2 From To3 To4 From) would qualify for a complex non circular trip **> World is for Round the World trips **************************************-</xs:documentation>
      <xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment copied from type definition **************************************-</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <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>
  <xs:attribute name="Role" type="TransportationRoleCodeType" use="optional"/>
  <xs:attribute name="Category" type="TransportationCategoryCodeType" use="optional"/>
</xs:attributeGroup>