SC Meeting Minutes

[Rex Brooks <rexb@starbourne.com>]

Hi Folks,

Here are today's minutes:

Draft minutes 02/01/05 EM-MSG SC telecon

1.  Roll Call.
 
Rex Brooks
Gary Ham
Tom Merkle
Michelle Raymond
Carl Reed
 Kon Wilms

A quorum was present.

1.  Art was traveling, and due to workload, Rex was unable to post
an agenda beyond citing the necessity for any last comments on CAP 1.1
before the next TC meeting, when it is scheduled to be voted for
Committee Draft status. No one had any comments beyond noting that we
need to see the last language changes before we conduct final discussions
and vote.

2.  EDXL – There were also no specific issues raised with the EDXL
Draft Distribution Specification.

 

3. EDXL – We discussed the Emergency Data Exchange Language (EDXL)
General Functional Requirements Proposed 11/4/04 
4.1
Define a modular vocabulary of individual and compound data elements that
can be applied in a variety of message formats and transactions,
including values and their definitions for enumerated elements (i.e.,
elements for which the allowable values are constrained to a finite
list).
 
The purpose was to drill down into the message formats and transactions
so that they can be specified in the Requirements Document.
 
Rex noted that the W3C has released three new recommendations which deal
with messaging:
 
“25 January 2005 -- The World Wide Web Consortium
(W3C) has published three new Web
Services Recommendations:
XML-binary
Optimized Packaging (XOP),
SOAP
Message Transmission Optimization Mechanism (MTOM), and
Resource
Representation SOAP Header Block (RRSHB).”
 
Gary commented that DMIS is nearing completion of an improved version of
the prototype EDXL Interop API to implement the EDXL Distribution XSD
against. Additionally, he noted that work is needed to make clear what is
meant by ‘Resources’ in an EDXL context, specifically noting that this
follows the practice inherent in ICS 201.
 
He said that NIMS is working on a specific translation of ICS201 and Rex
indicated that he had produced a prototype schema for ICS 201 early in
2003, and agreed to make it available so it is both attached to this
email and available in the EM TC Document Repository:
 
http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/5915/ICS-201-draft0.2.xsd
 
Specifically, the term Resources in this context is meant to refer
physical or actual resources, such as firetrucks as opposed to web
resources such as namespaces or document locations.
 
Michelle reported that she had started work on researching the current
usages of the terms ‘resource v. asset’ and ‘incident v. event’ which
pose similar challenges for clarification in specific usages.
 
These concerns underlie this discussion about specifying message formats
and the need to be specific in requirements.
 
Kon said he would write up a brief description of the current practices
in broadcast for acknowledgements and forwarding opaque alerting
content.
 
Tom said he would review the core components data model he received today
and will notify us of any specific issues we need to consider. Rex asked
if this was different from the Request for Information (RFI)
On Data Model Harmonization and Visualization Tools
released by the Core Data Types Working Group quoted below*. It is
different. The RFI reflects our work in clarifying the terms mentioned
above.

Meeting adjourned
 
*Background
 
The Inter-agency Core Data Types Working Group is chartered to define and
develop core data models for use in cross-agency information
exchanges.  A core data model is a data model applicable across more
than one information domain.  To facilitate the rapid development of
such core data models the group seeks information from vendors on tool
support for data model harmonization and visualization.

Rex Brooks
President, CEO, Starbourne Communications Design
Executive Director, Humanmarkup.org, Inc.
1361-A Addison
Berkeley, CA 94702
510-849-2309

<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY 2004 U (http://www.xmlspy.com) by Rex Brooks (Humanmarkup.org, Inc) -->
<xs:schema targetNamespace="http://www.oasis-open.org/committees/emergency/schema/ICS-201-drat0.2.xsd";  xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns="http://www.oasis-open.org/committees/emergency/schema/ICS-201-drat0.2.xsd"; elementFormDefault="qualified" attributeFormDefault="unqualified">
	<!--<xs:import namespace="http://www.fdgc.gov/metadata/fdgc-std-001-1998.dtd"/>
	<xs:import namespace="urn:oasis:names:tc:emergency:xsdschema:CAP2.0" schemaLocation="CAP1.0.xsd"/>-->
	<xs:element name="ICS-201-Form">
		<xs:annotation>
			<xs:documentation>ICS-201-Form is Incident Command System 201 Form, a set of standard datatypes for elements and attributes with acceptable values to describe a common operational procedure for handling information related to emergency incidents by public governmental and private respondent agencies.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:annotation>
		<xs:documentation xml:lang="en">
			ICS-201-Form Incident Briefing Schema, Version 1.0
			Copyright 2002 The Organization for the Advancement of Structured Information Standards. All rights reserved.  
			This schema provides a standard container for common usage among public and private agencies tasked with responding to emergency incidents. It takes the name of the United States of America Federal Government container-form for the same uses and purposes and applies it universally for expedient interoperability. It does not replace the form of the same name, nor does it belong to the numerical sequence of forms in the ICS200 set of forms related to Incident Command Systems. That does not presume that it will not do so, simply that it does not at the time of this schema's creation. Note this is the first working draft.
			OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.
			OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.
			This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
			This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
			OASIS has been notified of intellectual property rights claimed in regard to some or all of the contents of this specification. For more information consult the online list of claimed rights.
		</xs:documentation>
		<xs:appinfo>NONE</xs:appinfo>
	</xs:annotation>
	
	<!-- Global Section -->
	
	<!-- Begin Simple Types	
	
	<xs:simpleType name="range">
		<xs:restriction base="xs:decimal">
			<xs:minInclusive value="0"/>
			<xs:maxInclusive value="1"/>
		</xs:restriction>
	</xs:simpleType>-->
	
	<!-- End Simple Types -->
	
	<!-- Begin Attribute Groups -->
	
	<xs:attributeGroup name="ics201Atts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Attributes
				This ICS-201-Form term ics201Atts is used for identifier uniqueness in ICS-201-Form element
				names. It is separate from the ICS-201-Form "Identifier" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="id" type="xs:ID" use="required"/>
		<xs:attribute name="ICS-201-FormName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201IncidentAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Incident Attributes
				This ICS-201-Form term isc201IncidentAtts is used for identifer uniqueness in ICS-201-Form
				element names. It is separate from the ICS-201-Form "Incident" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="id" type="xs:ID" use="required"/>
		<xs:attribute name="ics201IncidentlName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201SummaryAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Summary Attributes
				This ICS-201-Form term ics201SummaryAtts is used for identifier uniqueness in ICS-201-Form
				element names. It is separate from the ICS-201-Form "Summary" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ICS-201-SummaryName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201ObjectiveAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Objective Attributes
				This ICS-201-Form term ics201ObjectiveAtts is used for identifier uniqueness in ICS-201-Form
				element names. It is separate from the ICS-201-Form "Objective" element.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ics201ObjectiveName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201ActionAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Action Attributes
				This ICS-201-Form term ics201ActionAtts is used for identifier uniqueness in ICS-201-Form
				element names. It is separate from the ICS-201-Form "Action" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ICS-201-FormActionName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201ResourcesAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Resources Attributes
				This ICS-201-Form term ics201ResourcesAtts is used for identifier uniqueness in ICS-201
				Form element names. It is separate from the ICS-201-Form "Action" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ICS-201-FormResourceName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201AssetAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Asset Attributes
				This ICS-201-Form term ics201AssetAtts is used for identifier uniqueness in ICS-201-Form
				element names. It is separate from the ICS-201-Form "Asset" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ICS-201-FormAssetName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201OrganizationAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Organization Attributes
				This ICS-201-Form term ics201OrganizationAtts is used for identifier uniqueness in ICS-201
				Form element names. It is separate from the ICS-201-Form "Organization" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ICS-201-FormOrganizationName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201PositionAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Position Attributes
				This ICS-201-Form term ics201PoisitonAtts is used for identifier uniqueness in ICS-201-Form
				element names. It is separate from the ICS-201-Form "Position" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ICS-201-FormPositionName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201LocationAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Location Attributes
				This ICS-201-Form term ics201LocationAtts is used for identifier uniqueness in ICS-201-Form
				element names. It is separate from the ICS-201-Form "Location" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ICS-201-FormLocationName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201AreaAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form Area Attributes
				This ICS-201-Form term ics201AreaAtts is used for identifier uniqueness in ICS-201-Form
				element names. It is separate from the ICS-201-Form "Area" element.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ICS-201-FormAreaName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="ics201MapSketchAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				ICS-201-Form MapSketch Attributes
				This ICS-201-Form term ics201MapSketchAtts is used for identifier uniqueness inICS-201-Form
				element names. It is separate from the ICS-201-Form "Identifier" element which provides a
				name label for a specific incident.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="ICS-201-FormMapSketchName" type="xs:string" use="required"/>
		<!--We need to add in all the specific datatypes as attributes.-->
	</xs:attributeGroup>
	
	<!-- End Attribute Groups -->
	
	<!-- Begin Phsyical Dimensions-->

	<!-- Begin Global Attributes
	
	<xs:attribute name="intensity">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Intensity
				This is a positive number between 0 and 1 used to set a relative scale 
            of the intensity or strength of some condition, capable of conversion to and from measurement and/or evaluation systems such as DHS threat level, severity of weather or other natural phenomena such as earthquakes and volcanic eruptions. Uses the simpleType "range."
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
	</xs:attribute>
	End Global Attributes -->
	
	<!-- Begin Complex Types -->
	
	<!--<xs:complexType name="MeasurementUnit">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Measurement Unit
				Used to create measurement values.  
				This complexType is used to establish the use of a recognized measurement system.    Systems of measurement vary by unit, name (for example English units vs metric units) and measurement type.  For example, for radius used to determine proximity some unit of distance is needed. We anticipate a corresponding RDF Schema to act as a facility for connecting a resource reference to an application that wishes to use this and the subsequent huml schema. We may decide to include elements from such reference schemata or to import the namespaces of such measurement system standards.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
	</xs:complexType>-->
	
	<!-- End Physical Dimensions--><!--This section could also be used for location, area, etc and it might be more efficient since it could be copied, cited or imported into another schema as needed -->
	
	<!-- Begin ics201 Briefing Message section-->
	
	<xs:complexType name="Identifier">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Identifier
				(1) A number or string uniquely identifying this message, assigned by the sender
				(2) No spaces or restricted characters <!--(< and &)-->
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201Atts"/>
	</xs:complexType>
	<xs:complexType name="Sender">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1) Identifies the originator of this message. Guaranteed by assigner to be unique globally;
				e.g., may be based on an Internet domain name
				(2) No spaces or restricted characters  <!--(< and &)-->
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201Atts"/>
	</xs:complexType>
	<xs:simpleType name="Sent">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The date and time is represented in ISO 8601 format (e. g., "2002-05-24T16:49:00-07:00" for
				24 May 2002 at 16: 49 PDT).
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:restriction base="xs:dateTime">
		</xs:restriction>	
	</xs:simpleType>
	<xs:complexType name="Status">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Status denotes the  ICS-201-Form Incident Briefing Message Status
				Code Values:
				•	“Actual” - Actionable by all targeted recipients
				•	“Exercise”- Actionable only by designated exercise participants; exercise identifier should
					appear in <!--<note>-->
				•	“System” - For messages that support message network internal functions.
				•	“Test” - Technical testing only, all recipients disregard
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
			<xs:attribute name="chronemicType">
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:enumeration value="Actual"/>
						<xs:enumeration value="Exercise"/>
						<xs:enumeration value="System"/>
						<xs:enumeration value="Test"/>
					</xs:restriction>
				</xs:simpleType>
			</xs:attribute>
		<xs:attributeGroup ref="ics201Atts"/>
	</xs:complexType>
	<xs:complexType name="MsgType">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				MsgType is the abbreviation for ICS-201-Form Incident Briefing Message Type
				Code Values:
				•	“Alert” - Initial information requiring attention by targeted recipients
				•	“Update” - Updates and supercedes the earlier message(s) identified in <!--<reference>-->
				•	“Cancel” - Cancels the earlier message(s) identified in <!--<reference>-->
				•	“Ack” - Acknowledges receipt and acceptance of the message(s)) identified in
					<!--<reference>-->
				•	“Error” indicates rejection of the message(s) identified in <!--<reference>-->; explanation
					should appear in <!--<note>-->
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="chronemicType">
				<xs:simpleType>
					<xs:restriction base="xs:string">			
						<xs:enumeration value="Alert"/>
						<xs:enumeration value="Update"/>
						<xs:enumeration value="Cancel"/>
						<xs:enumeration value="Ack"/>
						<xs:enumeration value="Error"/>
					</xs:restriction>
				</xs:simpleType>
			</xs:attribute>
		<xs:attributeGroup ref="ics201Atts"/>
	</xs:complexType>
	<xs:complexType name="Reference">
	<xs:annotation>
		<xs:documentation xml:lang="en">
				(1) The extended message identifier(s) (in the form identifier/ sender) of an earlier message or
				 messages referenced by this one.
				 (2) If multiple messages are referenced, they are separated by whitespace.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201Atts"/>
	</xs:complexType>

	<!-- End ics201 Briefing Message section -->
	
	<!-- Begin ics201 Briefing Incident section -->
	
	<xs:complexType name="Incident" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1)	Surrounds incident element sub-elements. 
				(2)	In addition to the specified sub-elements, may contain one or more <!--<resources>-->
				 blocks and one or more <!--<organization>--> blocks and one or more <!--<location>-->
				 blocks and one or more <!--<summary>--> blocks.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201IncidentAtts"/>
	</xs:complexType>
	<xs:complexType name="IncidentName">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The human-readable name assigned to the incident that this message pertains to.			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201IncidentAtts"/>
	</xs:complexType>
	<xs:simpleType name="Prepared">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The date and time is represented in ISO 8601 format (e. g., "2002-05-24T16:49:00-07:00" for
				24 May 2002 at 16: 49 PDT).
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:restriction base="xs:dateTime">
		</xs:restriction>
	</xs:simpleType>
	<xs:complexType name="PreparedName">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The human-readable name of the person that prepared this message.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201IncidentAtts"/>
	</xs:complexType>
	<xs:complexType name="PreparedPosition">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The human-readable ICS positionof the person that prepared this message.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201IncidentAtts"/>
	</xs:complexType>
	<xs:complexType name="PreparedAgency">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The human-readable name of the agency or authority that prepared this message.				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201IncidentAtts"/>
	</xs:complexType>
	<xs:complexType name="Contact">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The human-readable name of the agency or authority that prepared this message.The text
				 describing the contact for follow-up and confirmation of this ics201 message 				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201IncidentAtts"/>
	</xs:complexType>
	<xs:complexType name="Web">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				A full, absolute URI for an HTML page or other text resource with additional or reference
				 information regarding this message
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201IncidentAtts"/>
	</xs:complexType>
	
	<!-- End ics201 Briefing Incident section -->
	
	<!-- Begin ics201 Briefing Summary section -->
		
	<xs:complexType name="Summary">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1)	Surrounds summary sub-elements. 
				(2)	In addition to the specified sub-elements, will contain one or more <!--<objective>--> blocks
				and may contain one or more <!--<action>--> blocks
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201SummaryAtts"/>
	</xs:complexType>	
		
	<!-- End ics201 Briefing Summary section -->
	
	<!-- Begin ics201 Briefing Objective section -->
	
	<xs:complexType name="Objective">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Description of the strategy and tactics used on the incident including any specific problem
				areas.			
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201ObjectiveAtts"/>
	</xs:complexType>
	
	<!-- End ics201 Briefing Objecdtive section -->
	
	<!-- Begin ics201 Briefing Action section -->
	
	<xs:complexType name="Action">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Description of the strategy and tactics used on the incident including any specific problem
				areas.			
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201ActionAtts"/>
	</xs:complexType>

	<!-- End ics201 Briefing Action section -->
	
	<!-- Begin ics201 Briefing Resource section -->
	
	<xs:complexType name="Resources">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1)	Surrounds resources sub-elements. 
				(2)	In addition to the specified sub-elements, will contain one or more <!--<asset>--> blocks.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201ResourcesAtts"/>
	</xs:complexType>

	<!-- End ics201 Briefing Resource section -->
	
	<!-- Begin ics201 Briefing Asset section -->
	
	<xs:complexType name="Asset">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1)	Surrounds asset sub-elements. 
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201AssetAtts"/>
	</xs:complexType>
	<xs:complexType name="ResourceDesc">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The number and type of resources ordered.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201AssetAtts"/>
	</xs:complexType>
	<xs:complexType name="ResourceID">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The agency three letter designator, S/T, Kind/Type, resource designator, and S/T letter
				designator code.		
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201AssetAtts"/>
	</xs:complexType>
	<xs:simpleType name="ResourceExpected">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The date and time is represented in ISO 8601 format (e. g., "2002-05-24T16:49:00-07:00" for
				24 May 2002 at 16: 49 PDT).
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:restriction base="xs:dateTime">
		</xs:restriction>	
	</xs:simpleType>
	<xs:simpleType name="IsOnScene">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				True = Resource has arrived at incident location.
				False = Resource not arrived at incident location.
				(MAY ALSO NEED TO HANDLE “UNKNOWN”).
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:restriction base="xs:boolean">
		</xs:restriction>	
	</xs:simpleType>
	<xs:complexType name="ResourceAssign">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Assigned location of the resource and/or the actual location.			
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201AssetAtts"/>
	</xs:complexType>
	
	<!-- End ics201 Briefing Asset section -->
	
	<!-- Begin ics201 Briefing Organization section -->
	
	<xs:complexType name="Organization">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1)	Surrounds organization sub-elements.
				(2)	In addition to the specified sub-elements, will contain one or more <!--<position>--> blocks.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201OrganizationAtts"/>
	</xs:complexType>
	
	<!-- End ics201 Briefing Organization section -->
	
	<!-- Begin ics201 Briefing Position section -->
	
	<xs:complexType name="Position">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1)	Surrounds position sub-elements
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201PositionAtts"/>
	</xs:complexType>
	<xs:complexType name="PositionTitle">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Position name and/or text description of the ICS organization position being described by this
				<!--<position>--> block. 				
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201PositionAtts"/>
	</xs:complexType>
	<xs:complexType name="PositionReports">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(Position Name and/or text description of the ICS organization position that the position being
				described by this <!--<position>--> block reports to within the ICS organization hierarchy for
				this incident .				
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201PositionAtts"/>
	</xs:complexType>
	<xs:complexType name="Name">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Name of an individual who is executing the role of the ICS organization position being
				described by this <!--<position>--> block. May also include other descriptive information about
				the individual				
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201PositionAtts"/>
	</xs:complexType>
	<xs:complexType name="Agency">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Agency name of an individual who is executing the role of the ICS organization position being
				described by this <!--<position>--> block			
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201PositionAtts"/>
	</xs:complexType>

	<!-- End ics201 Briefing Position section -->
	
	<!-- Begin ics201 Briefing Location section -->
	
	<xs:complexType name="Location">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1)	Surrounds location sub-elements. 
				(2)	In addition to the specified sub-elements, will contain one or more <!--<area>--> blocks and
				may contain one or more <!--<mapSketch>--> blocks.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201LocationAtts"/>
	</xs:complexType>
	
	<!-- End ics201 Briefing Location section -->
	
	<!-- Begin ics201 Briefing Area section -->
	
	<xs:complexType name="Area">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1)	Surrounds area sub-elements. 
				(2)	May contain one or multiple instances of <!--<polygon>, <circle> or <geocode>-->. If
				multiple <!--<polygon>, <circle> or <geocode>--> elements are included, the area described by
				this <!--<area>--> is the union of those represented by the included elements.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201AreaAtts"/>
	</xs:complexType>
	<xs:complexType name="AreaDesc">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				A text description of the affected area.		
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201AreaAtts"/>
	</xs:complexType>
	<xs:complexType name="Polygon">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1) Code Values: The geographic polygon is represented by a whitespace-delimited list of
				WGS-84 coordinate values [see WGS-84 Note].
				(2) The first and last pairs of coordinates must be the same.
				(3) See Coordinate Precision Note, below.
				(4) Multiple instances may occur within an <!--<area>-->.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201PositionAtts"/>
	</xs:complexType>
	<xs:complexType name="Circle">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1) Code Values: The circular area is represented by a central point given as a WGS-84
				coordinate value [see WGS-84 Note], followed by a space character and a radius value in
				kilometers.
				(2) See Coordinate Precision Note, below.
				(3) Multiple instances may occur within an <!--<area>-->.
		
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201PositionAtts"/>
	</xs:complexType>
	<xs:complexType name="Geocode">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1) Code Values: Any geographically-based code to describe message target area, in the form
				"code_type=code" where "code_type" is a user-assigned abbreviation for the target system
				(e. g,, "fips6=06003").
				(2) Multiple instances may occur within an <!--<area>-->.
				(3) Use of this element presumes knowledge of the coding system on the part of recipients;
				therefore, for interoperability, it should be used in concert with an equivalent description in the
				more universally understood <!--<polygon>--> and <!--<circle>--> forms whenever possible.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201AreaAtts"/>
	</xs:complexType>
	<xs:complexType name="Altitude">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1) If used with the <!--<ceiling>--> element this value is the lower limit of a range. Otherwise,
				this value specifies a specific altitude.
				(2) The altitude measure is in feet above mean sea level (per WGS-84 datum).
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201AreaAtts"/>
	</xs:complexType>
	<xs:complexType name="Ceiling">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1) May only be used in combination with the <!--<altitude>--> element
				(2) The altitude measure is in feet above mean sea level (per WGS-84 datum).
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201AreaAtts"/>
	</xs:complexType>

	<!-- End ics201 Briefing Area section -->
	
	<!-- Begin ics201 Briefing MapSketch section -->

	<xs:complexType name="MapSketch">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				(1)	Surrounds map sub-elements.
				(2)	Multiple occurrences permitted, in which case the target area for the <!--<location>-->
				 block is the union of all the included <!--<mapSketch>--> blocks.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201MapSketchAtts"/>
	</xs:complexType>
	<xs:complexType name="MimeType">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				MIME content type and sub-type as described in RFC 1521
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201MapSketchAtts"/>
	</xs:complexType>
	<xs:complexType name="Size">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Approximate size in bytes.
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201MapSketchAtts"/>
	</xs:complexType>
	<xs:complexType name="URL">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				A full absolute URI, typically a Uniform Resource Locator that can be used to retrieve the
				resource file over the Internet.		
				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201MapSketchAtts"/>
	</xs:complexType>
	<xs:complexType name="Digest">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				The code representing the digital digest (“hash”) computed from the resource file (optional)
				Calculated using the Secure Hash Algorithm (SHA-1) per FIPS Publication 180-1				</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="ics201MapSketchAtts"/>
	</xs:complexType>
	<!-- End Complex Types -->
	<!-- End Global Section -->
</xs:schema>