complexType Evacuation
diagram
namespace http://www.IM-Draft-03-00-44a
children header evacuationData routeSets localEvacuation
used by
elements TrafficControlPlan/evacuations/evacuation MobileIDXWrapper/evacuation IDX-Wrapper/evacuationReports/evacuationReport
annotation
documentation
      
            Evacuation Data sub message,   "Evacuation information",
        
source <xs:complexType name="Evacuation">
  <xs:annotation>
    <xs:documentation>      
            Evacuation Data sub message,   &amp;quot;Evacuation information&amp;quot;,
         </xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="header" type="Header"/>
    <!-- if an inner element is not present then
         the header content of the message which
         carries this DF shall be applied to the
         context of this message. The header has the
         data creator,  time stamps,  location,
         and what to do when the message becomes
         old  (how to get a fresh one)  and the
         reference ID of this message or submessage -->
    <xs:element name="evacuationData" type="EvacuationData"/>
    <!-- consists of the area that may need to be evacuated
         coded list of cause of concern
         text expressing likelihood of need to evacuate -->
    <xs:element name="routeSets" minOccurs="0">
      <xs:complexType>
        <xs:sequence maxOccurs="32">
          <xs:element name="routeSet" type="RouteSet"/>
          <!-- the route itself,  enclosing routes as per SAE work as well as detours and itineraries this structure also provides a human name for the route and a set of start and end date-times -->
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="localEvacuation" type="local:Evacuation" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>

element Evacuation/header
diagram
type Header
properties
isRef 0
content complex
children senderIncidentID inReplyTo pedigreeSequence sender basics issueTime updateTime expiryTime onExpiry urgency testMessage localHeader
source <xs:element name="header" type="Header"/>

element Evacuation/evacuationData
diagram
type EvacuationData
properties
isRef 0
content complex
children evacuationData-item
source <xs:element name="evacuationData" type="EvacuationData"/>

element Evacuation/routeSets
diagram
properties
isRef 0
minOcc 0
maxOcc 1
content complex
children routeSet
source <xs:element name="routeSets" minOccurs="0">
  <xs:complexType>
    <xs:sequence maxOccurs="32">
      <xs:element name="routeSet" type="RouteSet"/>
      <!-- the route itself,  enclosing routes as per SAE work as well as detours and itineraries this structure also provides a human name for the route and a set of start and end date-times -->
    </xs:sequence>
  </xs:complexType>
</xs:element>

element Evacuation/routeSets/routeSet
diagram
type RouteSet
properties
isRef 0
content complex
children id name whenStart whenEnd involvedResources routes detours furtherData localRouteSet
source <xs:element name="routeSet" type="RouteSet"/>

element Evacuation/localEvacuation
diagram
type local:Evacuation
properties
isRef 0
minOcc 0
maxOcc 1
content complex
children yourName
source <xs:element name="localEvacuation" type="local:Evacuation" minOccurs="0"/>


XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy