Emergency Data Exchange Language (EDXL) Distribution Element, v. 1.0

Committee Specification, 14 March 2006

Document Identifier:

EDXL-DE-V1.0

OASIS Identifier:

{EMTC}-{EDXL-DE}-{1.0} (HTML) (Word) (PDF)

Location:

This Version: http://docs.oasis-open.org/emergency/EDXL-DE/V1.0

Technical Committee:

OASIS Emergency Management TC

Chair(s):

Elysa Jones, Warning Systems, Inc. - mailto:ejones@warningsystems.com

Editor(s):

Michelle Raymond, Individual

Sylvia Webb, Individual

Patti Iles Aymond, IEM, Inc. - mailto:patti.aymond@iem.com

Subject / Keywords:

distribution element, dissemination, routing, payload, alert, resource message, emergency, information sharing, data exchange, emergency response, emergency management, geospatial, political, target area, message delivery, message sender, message recipient, distribution status, distribution type, sender role, recipient role, response type, event cause, confidentiality, circle, polygon, location, content object, consumer role, notification, XML message, distribution type, geography, incident, sender identification, sender id, recipient identification, recipient id, inter-agency, emergency information, functional role, recipient address, hazard, distribution status, distribution type, event type, event etiology, message processor, event stage, resource code and response type

Related Work:

This specification is related to:

CAP 1.1 - http://www.oasis-open.org/committees/emergency

The Common Alerting Protocol (CAP) provides an open, non-proprietary digital message format for all types of alerts and notifications. CAP messages are recommended as one of the standardized forms for XML based message content, to be distributed by this Distribution Element.

Abstract:

This Distribution Element specification describes a standard message distribution framework for data sharing among emergency information systems using the XML-based Emergency Data Exchange Language (EDXL). This format may be used over any data transmission system, including but not limited to the SOAP HTTP binding.

Status:

This document was last revised or approved by the Emergency Management Technical Committee on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committee’s web page at www.oasis-open.org/committees/emergency.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page at www.oasis-open.org/committees/emergency/ipr.php.

Notices

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 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 implementers or users of this specification, can be obtained from the OASIS President.

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

Copyright © OASIS Open 2006. All Rights Reserved.

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

Table of Contents

1. Introduction.................................................................................................................................................. 5

1.1 Purpose.......................................................................................................................................................... 5

1.2 History.......................................................................................................................................................... 5

1.3 Structure of the EDXL Distribution Element...................................................................... 6

1.3.1 <EDXLDistribution>.............................................................................................................................. 6

1.3.2 <targetArea>........................................................................................................................................... 6

1.3.3 <contentObject>..................................................................................................................................... 6

1.4 Applications of the EDXL Distribution Element................................................................. 6

1.5 Terminology.............................................................................................................................................. 6

1.6 Normative References........................................................................................................................ 7

1.7 Non-Normative References.............................................................................................................. 7

2. Design Principles and Concepts (non-normative).............................................................. 8

2.1 Design Philosophy.................................................................................................................................. 8

2.2 Requirements for Design................................................................................................................... 8

2.3 Example Usage Scenarios.................................................................................................................. 9

2.3.1 Distribution of Emergency Message/s or Alerts Based on Geographic Delivery Area and Incident Type..................................................................................................................................................... 9

2.3.2 Encapsulation and Distribution of One or More Emergency Messages or Alerts or Notifications....................................................................................................................................................... 9

2.3.3 Distribution of Resource Messages or Reports.................................................................................. 9

2.3.4 Distribution of Well-Formed XML Messages...................................................................................... 9

3. EDXLDistribution Element Structure (normative)........................................................ 10

3.1 Document Object Model.................................................................................................................. 10

3.2 Data Dictionary................................................................................................................................... 11

3.2.1 EDXLDistribution Element and Sub-elements.................................................................................. 11

3.2.2 targetArea Element and Sub-elements............................................................................................... 18

3.2.3 contentObject Element and Sub-elements......................................................................................... 21

3.2.4 nonXMLContent Element and Sub-elements..................................................................................... 26

3.2.5 xmlContent Element and Sub-elements.............................................................................................. 26

3.2.6 List and Associated Value(s)............................................................................................................... 26

3.2.7 Explicit Addressing............................................................................................................................... 26

Appendix A. XML Schema for the EDXLDistribution Element....................................... 26

Appendix B. EDXL-DE Examples............................................................................................................... 26

B.1 EDXL-DE With CAP Payload.............................................................................................................. 26

B.2 EDXL-DE With Multiple Encrypted Payloads...................................................................... 26

Appendix C. Acknowledgments........................................................................................................... 26

C.1 OASIS Emergency Management Technical Committee:................................................ 26

Appendix D. Revision History................................................................................................................ 26


1. Introduction

1.1 Purpose

The primary purpose of the Distribution Element is to facilitate the routing of any properly formatted XML emergency message to recipients. The Distribution Element may be thought of as a "container". It provides the information to route "payload" message sets (such as Alerts or Resource Messages), by including key routing information such as distribution type, geography, incident, and sender/recipient IDs.

1.2 History

The Disaster Management eGov Initiative of the Department of Homeland Security (DHS) determined in 2004 to launch a project to develop interagency emergency data communications standards. It called together a group of national emergency response practitioner leaders and sought their guidance on requirements for such standards. In June, 2004 the first such meeting identified the need for a common distribution element for all emergency messages. Subsequent meetings of a Standards Working Group developed detailed requirements and a draft specification for such a distribution element (DE).

During the same period the DM Initiative was forming a partnership with industry members of the Emergency Interoperability Consortium (EIC) to cooperate in the development of emergency standards. EIC had been a leading sponsor of the Common Alerting Protocol (CAP). Both organizations desired to develop an expanded family of data formats for exchanging operational information beyond warning.

EIC members participated in the development of the DE, and in the broader design of the design of a process for the development of additional standards. This was named Emergency Data Exchange Language (EDXL).

The goal of the EDXL project is to facilitate emergency information sharing and data exchange across the local, state, tribal, national and non-governmental organizations of different professions that provide emergency response and management services. EDXL will accomplish this goal by focusing on the standardization of specific messages (messaging interfaces) to facilitate emergency communication and coordination particularly when more than one profession is involved. It is not just an "emergency management" domain exercise.

It is a national effort including a diverse and representative group of local, state and federal emergency response organizations and professionals, following a multi-step process. Just as a data-focused effort targets shared data elements, the EDXL process looks for shared message needs, which are common across a broad number of organizations. The objective is to rapidly deliver implementable standard messages, in an incremental fashion, directly to emergency response agencies in the trenches, providing seamless communication and coordination supporting each particular process. The effort first addresses the most urgent needs and proceeds to subsequent message sets in a prioritized fashion. The goal is to incrementally develop and deliver standards.

EDXL is intended as a suite of emergency data message types including resource queries and requests, situation status, message routing instructions and the like, needed in the context of cross-disciplinary, cross-jurisdictional communications related to emergency response.

The priorities and requirements are created by the DM EDXL Standards Working Group (SWG) which is a formalized group of emergency response practitioners, technical experts, and industry.

The draft DE specification was trialed by a number of EIC members starting in October, 2004. In November, 2004, EIC formally submitted the draft to the OASIS Emergency Management Technical Committee for standardization.

1.3 Structure of the EDXL Distribution Element

The EDXL Distribution Element (DE) comprises an <EDXLDistribution> element as described hereafter, optional <targetArea> elements describing geospatial or political target area for message delivery, and a set of <contentObject> elements each containing specific information regarding a particular item of content. The included content may be any XML or other content type or a URI to access the content.

The <EDXLDistribution> block may be used without content to form the body of a routing query to, or response from, a directory service.

1.3.1 <EDXLDistribution>

The <EDXLDistribution> element asserts the originator’s intent as to the dissemination of that particular message or set of messages.

Note that use of the <EDXLDistribution> element does not guarantee that all network links and nodes will implement the asserted dissemination policy or that unintended disclosure will not occur. Where sensitive information is transmitted over distrusted networks, it should be encrypted in accordance with the Web Services Security (WSS) standard http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf with any updates and errata published by the OASIS Web Services Security Technical Committee http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss, or some other suitable encryption scheme.

1.3.2 <targetArea>

The <targetArea> is a container element for the geospatial or political area targeting of the recipient of the message content. It contains data necessary to the originator's intent, based on location targeting, as to the dissemination of that particular message or set of messages.

1.3.3 <contentObject>

The <contentObject> is a container element for specific messages. The <contentObject> element MUST either contain an <xmlContent> content container or a <nonXMLContent> content container. Additional elements (metadata) used for specific distribution of the <contentObject> payload or hints for processing the payload are also present in the <contentObject> container element.

1.4 Applications of the EDXL Distribution Element

The primary use of the EDXL Distribution Element is to identify and provide information to enable the routing of encapsulated payloads, called Content Objects. It is used to provide a common mechanism to encapsulate content information.

1.5 Terminology

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” are to be interpreted as described in Key words for use in RFCs to Indicate Requirement Levels [RFC2119].

In addition, within this Specification, the keyword “CONDITIONAL” should be interpreted as potentially “REQUIRED” or “OPTIONAL” depending on the surrounding context. The term payload refers to some body of information contained in the distribution element.

1.6 Normative References

[RFC2046]

N. Freed, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types, http://www.ietf.org/rfc/rfc2046.txt, IETF RFC 2046, November 1996.

[RFC2119]

S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.

[RFC3066]

H. Alvestrand, Tags for the Identification of Languages, http://www.ietf.org/rfc/rfc3066.txt, IETF RFC 3066, January 2001.

[WGS 84]

National Geospatial Intelligence Agency, Department of Defense World Geodetic System 1984, http://earth-info.nga.mil/GandG/tr8350_2.html, NGA Technical Report TR8350.2, January 2000.

 [XML 1.0]

T. Bray, Extensible Markup Language (XML) 1.0 (Third Edition), http://www.w3.org/TR/REC-xml/, W3C REC-XML-20040204, February 2004.

[namespaces]

T. Bray, Namespaces in XML, http://www.w3.org/TR/REC-xml-names/, W3C REC-xml-names-19990114, January 1999.

[dateTime]

N. Freed, XML Schema Part 2: Datatypes Second Edition, http://www.w3.org/TR/xmlschema-2/#dateTime, W3C REC-xmlschema-2, October 2004.

1.7 Non-Normative References

EDXL General Functional Requirements

EDXL General Functional Requirements, http://www.oasis-open.org/committees/document.php?document_id=10031&wg_abbrev=emergency, November 2004.

EDXL Distribution Element Implementer's Guide

EDXL Distribution Element Implementer's Guide, http://www.oasis-open.org/committees/document.php?document_id=14120&wg_abbrev=emergency, August 2005.


2. Design Principles and Concepts (non-normative)

2.1 Design Philosophy

Below are some of the guiding principles of the Distribution Element:

2.2 Requirements for Design

The Distribution Element specification should:

  1. Define a single compound XML structure (or an equivalent single structure if transcoded into another format) including the required and optional elements defined below.
  2. Specify a desired geographic delivery area, expressed in geospatial coordinates or using political/administrative codes
  3. Allow the ability to encapsulate a payload or set of payloads
  4. Take a modular approach to the enumerations of element values which may evolve over time, e.g. by referring to a separate schema for those enumerations.
  5. Specify unique distribution and sender identifiers
  6. Specify the date and time the distribution was sent
  7. Specify the actionability of the distribution message (e.g., real-world, test, exercise)
  8. Specify the functional type of the distribution message (e.g., report, request, update, cancellation, etc.)
  9. Specify that the following elements may be present in a valid payload:
    1. A specification of the format of the distribution message (e.g., the URI of an XML Schema for the message)
    2. The functional role and/or type of the sender of the distribution message
    3. One or more functional role and/or type of desired recipients of the distribution message
    4. A reference to one or more previous distribution messages
    5. One or more types of response activity involved
    6. A reference to the type of incident
    7. One or more characterization of the etiology of the subject event or incident (e.g., terrorism, natural, under investigation, etc.)
    8. The incident name or other identifier of one or more event or incident
    9. A reference to one or more response types.
    10. One or more specific recipient addresses (as a URI)
    11. Specify an assertion of the confidentiality level of the combined payloads.
  1. In addition, the Content Object element contained within the Distribution Element SHOULD:
    1. Allow the encapsulation of one or more payloads in each of the Content Object elements.
    2. Specify the functional role and/or type of the sender of each payload
    3. Specify one or more functional roles and/or types of desired recipients of each payload
    4. Specify an assertion of the confidentiality level of each payload.
  1. Provide or refer to specific lists (enumerations) of values and their definitions for:
    1. Types of incidents
    2. Types of hazards and/or events
    3. Types of agencies
    4. Types of response activity
    5. The functional role and/or type of the sender
    6. The functional roles and/or types of desired recipients
    7. The incident name or other identifier of one or more event or incident.

2.3 Example Usage Scenarios

Note: The following examples of use scenarios were used as a basis for design and review of the EDXL Distribution Element Message format. These scenarios are non-normative and not intended to be exhaustive or to reflect actual practices.

2.3.1 Distribution of Emergency Message/s or Alerts Based on Geographic Delivery Area and Incident Type

The terror alert level has been raised to RED. Credible intelligence indicates that terrorist groups in the Mid-Atlantic region are seeking to conduct an attack in the next 48 hours. The Department of Homeland Security sends an emergency alert message, and using the Distribution Element, distributes it to all emergency agencies in the specified area.

2.3.2 Encapsulation and Distribution of One or More Emergency Messages or Alerts or Notifications

A Radiological sensor triggered at a prominent Tunnel toll booth. Radiation alarm levels indicates possible dirty bomb. Authorities decide to send multiple messages to a number of jurisdictions. They send an EDXL Distribution Element with two encapsulated CAP messages. The first one notifies the area where the sensor has been triggered. The second one is an alert to emergency response agencies that the state Emergency Operation Center (EOC) has been activated, and requests the agencies to be on alert.

2.3.3 Distribution of Resource Messages or Reports

The Local EOC has a need for additional resource/support, but is unsure what specifically to request. A free-form request for information and resource availability is prepared, and is sent to the state EOC and other organizations (person to person) using the Distribution Element. The Local EOC receives an acknowledgment message from the State EOC, as well as a request for Information on additional details of the requested resource. Both of these messages are contained within a single Distribution Element.

2.3.4 Distribution of Well-Formed XML Messages

A huge crash, involving a car and a HAZMAT truck, occurs at a busy junction on an inter-state freeway. Separate automatic notifications of both the car crash and the HAZMAT carrier are sent using the Vehicular Emergency Data Set (VEDS), contained in the Distribution Element. The Transportation Management Center (TMC) shares information (related to the above incident) with the adjacent TMC, using the IEEE 1512 Incident Management Message Set. These set of messages are exchanged using the EDXL Distribution Element.


3. EDXLDistribution Element Structure (normative)

3.1 Document Object Model

Bold indicates required element.
Italics indicates one or more optional unspecified elements

# indicates conditional requirement
* indicates multiple instances allowed

 


3.2 Data Dictionary

Note: Unless explicitly constrained within this Data Dictionary, EDXL-DE elements MAY have null values. Implementers MUST check for this condition wherever it might affect application performance.

3.2.1 EDXLDistribution Element and Sub-elements

The Distribution Message element, <EDXLDistribution> is the container element for all data necessary to the originator’s intent as to the dissemination of the contained message or set of messages.

Element

EDXLDistribution

Type

XML Structure

Usage

REQUIRED, MUST be used once and only once, top level container

Definition

The container of all of the elements related to the distribution of the content messages.

Comments

  1. The <EDXLDistribution> element may include one or more <targetArea> and <contentObject> blocks.
  2. Use of the <EDXLDistribution> element does not guarantee that all network links and nodes will implement the asserted dissemination policy or that unintended disclosure will not occur. Where sensitive information is transmitted over untrusted networks, it should be encrypted in accordance with the Web Services Security (WSS) standard (<http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf>) with any updates and errata published by the OASIS Web Services Security Technical Committee (<http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss>), or some other suitable encryption scheme.

Sub-elements

Used In

top level element


Element

distributionID

Type

xsd:string

Usage

REQUIRED, MUST be used once and only once

Definition

The unique identifier of this distribution message.

Comments

  1. Uniqueness is assigned by the sender to be unique for that sender.
  2. The identifier MUST be a properly formed -escaped if necessary- XML string.

Used In

EDXLDistribution

Element

senderID

Type

xsd:string

Usage

REQUIRED, MUST be used once and only once

Definition

The unique identifier of the sender.

Comments

  1. Uniquely identifies human parties, systems, services, or devices that are all potential senders of the distribution message.
  2. In the form actor@domain-name.
  3. Uniqueness of the domain-name is guaranteed through use of the Internet Domain Name System, and uniqueness of the actor name enforced by the domain owner.
  4. The identifier MUST be a properly formed -escaped if necessary- XML string.

Examples: dispatcher@example.gov, 0006.0e39.ad80@example.com

Used In

EDXLDistribution

Element

dateTimeSent

Type

xsd:dateTime

Usage

REQUIRED, MUST be used once and only once

Definition

The date and time the distribution message was sent.

Comments

  1. The Date Time combination must include the offset time for time zone.
  2. Must be in the W3C format for the XML [dateTime] data type.

Example: 2004-08-01T16:49:00-07:00

Used In

EDXLDistribution


Element

distributionStatus

Type

xsd:string with restrictions

Usage

REQUIRED, MUST be used once and only once

Definition

The actionability of the message.

Comments

  1. Value must be one of:
    1. Actual - "Real-world" information for action
    2. Exercise - Simulated information for exercise participants
    3. System - Messages regarding or supporting network functions
    4. Test - Discardable messages for technical testing only.
  2. The status MUST be a properly formed -escaped if necessary- XML string.

Used In

EDXLDistribution

Element

distributionType

Type

xsd:string with restrictions

Usage

REQUIRED, MUST be used once and only once

Definition

The function of the message.

Comments

  1. Value must be one of:
    1. Report - New information regarding an incident or activity
    2. Update - Updated information superseding a previous message
    3. Cancel - A cancellation or revocation of a previous message
    4. Request - A request for resources, information or action
    5. Response - A response to a previous request
    6. Dispatch - A commitment of resources or assistance
    7. Ack - Acknowledgment of receipt of an earlier message
    8. Error - Rejection of an earlier message (for technical reasons)
    9. SensorConfiguration - These messages are for reporting configuration during power up or after Installation or Maintenance.
    10. SensorControl - These are messages used to control sensors/sensor concentrator components behavior.
    11. SensorStatus - These are concise messages which report sensors/sensor concentrator component status or state of health.
    12. SensorDetection - These are high priority messages which report sensor detections.
  2. The distribution type applies to the function of the content objects as a set. Those cases where payloads have different distribution types should be clustered in different distribution elements.
  3. The type MUST be a properly formed -escaped if necessary- XML string.

Used In

EDXLDistribution

Element

combindedConfidentiality

Type

xsd:string

Usage

REQUIRED, MUST be used once and only once

Definition

Confidentiality of the combined distribution message’s content.

Comments

  1. The <combindedConfidentiality> indicates the confidentiality of the combined <contentObject> sub-elements. Generally the combined confidentiality is the most restrictive of the <confidentiality> elements in the container <contentObject> element, but it can be more restrictive than any of the individual <confidentiality> elements.
  2. The <combindedConfidentiality> element MUST be present if a <confidentiality> element is present in any of the <contentObject> elements.
  3. Application specific mechanisms will be required to determine the minimum confidentiality level in cases where different confidentiality schemes are used in the <contentObject>.
  4. Default value “UNCLASSIFIED AND NOT SENSITIVE”
  5. The confidentiality MUST be a properly formed -escaped if necessary- XML string.

Used In

EDXLDistribution

Element

language

Type

xsd:string

Usage

OPTIONAL, MAY use once and only once

Definition

The primary language (but not necessarily exclusive) used in the payloads.

Comments

  1. Valid language values are supplied in the ISO standard [RFC3066].
  2. The language MUST be a properly formed -escaped if necessary- XML string.

Examples:  FR, EN

Used In

EDXLDistribution


Element

senderRole

Type

List and Associated Value(s)

Usage

OPTIONAL, MAY use multiple

Definition

The functional role of the sender, as it may determine message routing decisions.

Comments

  1. The list and associated value(s) is in the form:
       <senderRole>
          <valueListUrn>valueListUrn</valueListUrn>
          <value>value</value>
       </senderRole>
    where the content of <valueListUrn> is the Uniform Resource Name of a published list of values and definitions, and the content of <value> is a string (which may represent a number) denoting the value itself.
  2. Multiple instances of the <value>, MAY occur with a single <valueListUrn> within the <senderRole> container.
  3. Multiple instances of <senderRole> MAY occur within a single <EDXLDistribution> container.

Sub-elements

Used In

EDXLDistribution


Element

recipientRole

Type

List and Associated Value(s)

Usage

OPTIONAL, MAY use multiple

Definition

The functional role of the recipient, as it may determine message routing decisions.

Comments

  1. The list and associated value(s) is in the form:
       <recipientRole>
          <valueListUrn>valueListUrn</valueListUrn>
          <value>value</value>
       </recipientRole>
    where the content of <valueListUrn> is the Uniform Resource Name of a published list of values and definitions, and the content of <value> is a string (which may represent a number) denoting the value itself.
  2. Multiple instances of the <value>, MAY occur with a single <valueListUrn> within the <recipientRole> container.
  3. Multiple instances of <recipientRole> MAY occur within a single <EDXLDistribution> container.

Sub-elements

Used In

EDXLDistribution


Element

keyword

Type

List and Associated Value(s)

Usage

OPTIONAL, MAY use multiple

Definition

The topic related to the distribution message, as it may determine message routing decisions.

Comments

  1. The list and associated value(s) is in the form:
       <keyword>
          <valueListUrn>valueListUrn</valueListUrn>
          <value>value</value>
       </keyword>
    where the content of <valueListUrn> is the Uniform Resource Name of a published list of values and definitions, and the content of <value> is a string (which may represent a number) denoting the value itself.
  2. Multiple instances of the <value>, MAY occur with a single <valueListUrn> within the <keyword> container.
  3. Multiple instances of <keyword> MAY occur within a single <EDXLDistribution> container.
  4. Examples of things <keyword> might be used to describe include event type, event etiology, incident ID and response type.

Sub-elements

Used In

EDXLDistribution

Element

distributionReference

Type

xsd:string

Usage

CONDITIONAL, MAY use multiple

Definition

A reference to a previous distribution message.

Comments

  1. The <distributionID> and <senderID> and <dateTimeSent> of the referenced previous message, concatenated with a comma delimiter.
  2. This element should appear at least once in any message which updates, cancels or otherwise refers to another message.
  3. MUST be a properly formed -escaped if necessary- XML string.

Example: msgID0074,actor@domain-name,2004-08-01T16:49:00-07:00

Used In

EDXLDistribution


Element

explicitAddress

Type

XML Structure

Usage

OPTIONAL, MAY use multiple

Definition

The identifier of an explicit recipient.

Comments

  1. Identifies human parties, systems, services, or devices that are all potential recipients of the distribution message.
  2. The explicit address of a recipient in the form:
       <explicitAddress>
          < explicitAddressScheme> explicitAddressScheme </ explicitAddressScheme>
          <explicitAddressValue> explicitAddressValue </ explicitAddressValue>
       </ explicitAddress >
    where the content of <explicitAddressScheme> is the distribution addressing scheme used, and the content of <explicitAddressValue> is a string denoting the addressees value.
  3. Multiple instances of the < explicitAddressValue >, MAY occur with a single < explicitAddressScheme > within the < explicitAddress > container.
  4. Multiple instances of < explicitAddress > MAY occur within a single <EDXLDistribution> container.

Sub-elements

Used In

EDXLDistribution

3.2.2 targetArea Element and Sub-elements

The <targetArea> is a container element for the geospatial or political area targeting of the message content. It indicates the originator’s intent based on location targeting as to the dissemination of that particular message or set of messages.

Geospatial Note:

Values for latitude and longitude shall be expressed as decimal fractions of degrees.  Whole degrees of latitude shall be represented by a decimal number ranging from 0 through 90.  Whole degrees of longitude shall be represented by a decimal number ranging from 0 through 180.  When a decimal fraction of a degree is specified, it shall be separated from the whole number of degrees by a decimal point (the period character, ".").  Decimal fractions of a degree should be expressed to the precision available, with trailing zeroes being used as placeholders if required.  A decimal point is optional where the precision is less than one degree.

Some effort should be made to preserve the apparent precision when converting from another datum or representation, for example 41 degrees 13 minutes should be represented as 41.22 and not 41.21666, while 41 13' 11" may be represented as 41.2197.

Latitudes north of the equator MAY be specified by a plus sign (+), or by the absence of a minus sign (-), preceding the designating degrees.  Latitudes south of the Equator MUST be designated by a  minus sign (-) preceding the digits designating degrees.  Latitudes on the Equator MUST be designated by a latitude value of 0.

Longitudes east of the prime meridian shall be specified by a plus sign (+), or by the absence of a minus sign (-), preceding the designating degrees.  Longitudes west of the prime meridian MUST be designated by a minus sign (-) preceding the digits designating degrees. Longitudes on the prime meridian  MUST be designated by a longitude value of 0.  A point on the 180th meridian shall be taken as 180 degrees West, and shall include a minus sign.

Element

targetArea

Type

XML Structure

Usage

OPTIONAL, MAY use multiple

Definition

The container element for location information.

Comments

  1. Multiple <targetArea> blocks may appear in a single <EDXLDistribution> element, in which case the target area for the current message is the union of all areas described in the various <targetArea> structures.

Sub-elements

Used In

EDXLDistribution

Element

circle

Type

xsd:string

Usage

OPTIONAL, MAY use multiple

Definition

An enclosed geographic area within a given radius around a geographic point.

Comments

  1. Represented in the form "latitude, longitude, radius". (See Geospatial Note above)
  2. The central point is represented by lat-long values conforming to the WGS84 coordinate reference system. [WGS 84]
  3. The radius value is expressed in kilometers.
  4. MUST be a properly formed -escaped if necessary- XML string.

Example: 38.26295, -122.07454 15

Used In

targetArea


Element

polygon

Type

xsd:string

Usage

OPTIONAL, MAY use multiple

Definition

An enclosed geographic area within a simple closed polygon defined by an ordered set of vertices.

Comments

  1. Represented by a space-delimited series of latitude, longitude pairs, with the last pair identical to the first. (See Geospatial Note above)
  2. The lat-long values conform to the WGS84 coordinate reference system. [WGS 84]
  3. MUST be a properly formed -escaped if necessary- XML string.

Example: 42,-124.2102 42,-120.1 39,-120 35.0,-114.6328 34.35,- 120.4418 38.9383,-123.817 42,-124.2102

Used In

targetArea

Element

country

Type

xsd:string

Usage

OPTIONAL, MAY use multiple

Definition

The code of the country.

Comments

  1. The two-character ISO 3166-1 Country Code for the country concerned.
  2. More specific target location information can be defined in the <subdivision> elements.
  3. MUST be a properly formed -escaped if necessary- XML string.

Used In

targetArea


Element

subdivision

Type

xsd:string

Usage

OPTIONAL, MAY use multiple

Definition

The ISO 3166-2 designator for the administrative subdivision concerned.

Comments

  1. The first two characters, before the hyphen, are the two character ISO 3166-1 Country Code for the country within which the designated subdivision is located.
  2. The following one-to-three characters following the hyphen designate the particular subdivision.
  3. MUST be a properly formed -escaped if necessary- XML string.

Examples: US-TX (U.S. State of Texas), DK-025 (Danish county Roskilde), MG-T (Antananarivo province, Madagascar)

Used In

targetArea

Element

locCodeUN

Type

xsd:string

Usage

OPTIONAL, MAY use multiple

Definition

The UN/LOCODE designator for the location concerned.

Comments

  1. The two first digits are the two character ISO3166-1 Country Code for the country in which the place is located.
  2. The following three characters are the UN/LOCODE designator for the particular location within that country.
  3. No spaces or punctuation are used within this designator.
  4. MUST be a properly formed -escaped if necessary- XML string.

Example: USFFB (Fairfield, Alabama, USA), USSUU (Fairfield, California, USA), GBFFD (Falfield, South Gloucestershire, UK)

Used In

targetArea

3.2.3 contentObject Element and Sub-elements

The <contentObject> element is the container element for specific messages. The <contentObject> element MUST either contain an <xmlContent> content container or a <nonXMLContent> content container. Additional elements (metadata) used for specific distribution of the <contentObject> payload or hints for processing the payload are also present in the <contentObject> container element.


Element

contentObject

Type

XML Structure

Usage

OPTIONAL, MAY use multiple

Definition

The container element for message data and content.

Comments

  1. The <contentObject> is the container element for specific messages.
  2. The <contentObject> may have an optional attribute that defines a namespace prefix which resolves ambiguous element names.
  3. The <contentObject> element MUST contain exactly one of the two content formats:

a.      <xmlContent>, for valid namespaced XML content or

b.      <nonXMLContent>, containing one or both of the elements <uri>, for reference to the content’s location, and <contentData>, for data encapsulated in the message.

Sub-elements

Used In

EDXLDistribution

Element

contentDescription

Type

xsd:string

Usage

OPTIONAL, MAY use once and only once

Definition

The human-readable text describing the content object.

Comments

  1. MUST be a properly formed -escaped if necessary- XML string.

Examples: "CAP message from FEMA", "Map of affected area" or "Photo of missing child".

Used In

contentObject


Element

contentKeyword

Type

List and Associated Value(s)

Usage

OPTIONAL, MAY use multiple

Definition

The topic related to the message data and content, as it may determine message distribution and presentation decisions.

Comments

  1. The list and associated value(s) is in the form:
       <contentKeyword>
          <valueListUrn>valueListUrn</valueListUrn>
          <value>value</value>
       </contentKeyword>
    where the content of <valueListUrn> is the Uniform Resource Name of a published list of values and definitions, and the content of <value> is a string (which may represent a number) denoting the value itself.
  2. Multiple instances of the <value>, MAY occur with a single <valueListUrn> within the <contentKeyword> container.
  3. Multiple instances of <contentKeyword> MAY occur within a single <contentObject> container.

Examples of things <contentKeyword> might be used to describe include message processor, event stage, resource code and response type.

Sub-elements

Used In

contentObject

Element

incidentID

Type

xsd:string

Usage

OPTIONAL, MAY use once and only once

Definition

The human-readable text uniquely identifying the incident/event/situation associated with the contentObject.

Comments

  1. MUST be a properly formed -escaped if necessary- XML string.

Used In

contentObject


Element

incidentDescription

Type

xsd:string

Usage

OPTIONAL, MAY use once and only once

Definition

The human-readable text describing the incident/event/situation associated with the contentObject.

Comments

  1. MUST be a properly formed -escaped if necessary- XML string.

Used In

contentObject

Element

originatorRole

Type

List and Associated Value(s)

Usage

OPTIONAL, MAY use multiple

Definition

The functional role of the message originator, as it may determine message distribution and presentation decisions.

Comments

  1. The list and associated value(s) is in the form:
       <originatorRole>
          <valueListUrn>valueListUrn</valueListUrn>
          <value>value</value>
       </originatorRole>
    where the content of <valueListUrn> is the Uniform Resource Name of a published list of values and definitions, and the content of <value> is a string (which may represent a number) denoting the value itself.
  2. Multiple instances of the <value>, MAY occur with a single <valueListUrn> within the <originatorRole> container.
  3. Multiple instances of <originatorRole> MAY occur within a single <contentObject> container.

Sub-elements

Used In

contentObject


Element

consumerRole

Type

List and Associated Value(s)

Usage

OPTIONAL, MAY use multiple

Definition

The functional role of the message consumer, as it may determine message distribution and presentation decisions.

Comments

  1. The list and associated value(s) is in the form:
       <consumerRole>
          <valueListUrn>valueListUrn</valueListUrn>
          <value>value</value>
       </consumerRole>
    where the content of <valueListUrn> is the Uniform Resource Name of a published list of values and definitions, and the content of <value> is a string (which may represent a number) denoting the value itself.
  2. Multiple instances of the <value>, MAY occur with a single <valueListUrn> within the <consumerRole> container.
  3. Multiple instances of <consumerRole> MAY occur within a single <contentObject> container.

Example: <valueListUrn>"http://www.dhs.gov/NiemRoleType"</valueListUrn>, <value>ICS Operations Branch</value>

Sub-elements

Used In

contentObject

Element

confidentiality

Type

xsd:string

Usage

OPTIONAL, MAY use once and only once

Definition

Special requirements regarding confidentiality of the content of this <contentObject>.

Comments

  1. MUST be a properly formed -escaped if necessary- XML string.

Used In

contentObject


Element

other

Type

xsd:other

Usage

OPTIONAL, MAY be use to add an unlimited number of XML elements for enveloped signing process.

Definition

Special requirements allowing for signature of the content of a <contentObject>.

Comments

  1. There is no mandatory validation of the elements if the namespace reference can not be located.
  2. MUST be a properly formed XML string – escaped, if necessary.
  3. Element names cannot duplicate other element names in the contentObject. Such duplication would prevent validation due to the ambiguity introduced. 
  4. This element may be used for signatures. If this element is used for experimental extensions, such extensions may not be supported by all users or in future versions of EDXL-DE.

Used In

contentObject

3.2.4 nonXMLContent Element and Sub-elements

Element

nonXMLContent

Type

XML Structure

Usage

CONDITIONAL, MUST use once if xmlContent is not used

Definition

Container for content provided in a non-XML MIME type.

Comments

  1. The <nonXMLContent> container MUST have one or both of the elements <contentData> and <uri>.
  2. If the <uri> element is used in conjunction with the <contentData> element, it must reference a data location that contains the same data as is contained in the <contentData> element.

Sub-elements

Used In

contentObject


Element

mimeType

Type

xsd:string

Usage

REQUIRED, MUST be used once and only once

Definition

The format of the payload.

Comments

  1. MIME content type and sub-type as described in [RFC 2046].
  2. MUST be a properly formed -escaped if necessary- XML string.

Examples: application/pdf, application/mp3

Used In

nonXMLContent

Element

size

Type

xsd:integer

Usage

OPTIONAL, MAY use once and only once

Definition

The file size of the payload .

Comments

  1. Value must be in bytes and represent the raw file size (not encoded or encrypted).

Used In

nonXMLContent

Element

digest

Type

xsd:string

Usage

OPTIONAL, MAY use once and only once

Definition

The digest value for the payload.

Comments

  1. Used to ensure the integrity of the payload.
  2. Calculated using the Secure Hash Algorithm (SHA-1)
  3. MUST be a properly formed -escaped if necessary- XML string.

Used In

nonXMLContent


Element

uri

Type

xsd:anyURI

Usage

OPTIONAL, MAY use once and only once

Definition

A Uniform Resource Identifier that can be used to retrieve the identified resource.

Comments

  1. May be a full absolute URI, typically a Uniform Resource Locator, that can be used to retrieve the resource over the Internet.
  2. May be a relative URI naming a file. This may be just a pointer to a file or specifically to the file represented in the <contentData>.

Used In

nonXMLContent

Element

contentData

Type

xsd:base64Binary

Usage

OPTIONAL, MAY use once and only once

Definition

The base-64 encoded data content.

Comments

  1. MAY be used either with or instead of the <uri> element in contexts where retrieval of a resource via a URI is not feasible.
  2. MUST be a properly formed -escaped if necessary- XML string.

Used In

nonXMLContent

3.2.5 xmlContent Element and Sub-elements

Element

xmlContent

Type

XML Structure

Usage

CONDITIONAL, MUST use once if nonXMLContent is not used

Definition

Container for valid-namespaced XML data.

Sub-elements

  1. keyXMLContent
  2. embeddedXMLContent
  3. An optional namespace attribute may be included.

Used In

contentObject


Element

keyXMLContent

Type

xsd:string

Usage

OPTIONAL, MAY use multiple

Definition

A container element for collected fragments of valid XML.

Comments

  1. Extracts must come from the XML document contained within the <embeddedXMLContent> element within the current <contentObject> block.
  2. All content within this element MUST be explicitly namespaced as defined in the enclosing <contentObject> tag.
  3. MUST be a properly formed -escaped if necessary- XML string.

Used In

xmlContent

Element

embeddedXMLContent

Type

xsd:string

Usage

OPTIONAL, MAY use multiple

Definition

The <embeddedXMLContent> element is an open container for valid XML from an explicit namespaced XML Schema.

Comments

  1. The content MUST be a separately-namespaced well-formed XML document.
  2. The enclosed XML content MUST be explicitly namespaced as defined in the enclosing <embeddedXMLContent> tag.
  3. Enclosed XML content may be encrypted and/or signed within this element.

Used In

xmlContent


3.2.6 List and Associated Value(s)

Element

valueListUrn

Type

xsd:string

Usage

CONDITIONAL, MAY use once and only once

Definition

The name of a certified list maintained by the Community of Interest (COI) for the value referenced.

Comments

  1. MUST be a properly formed -escaped if necessary- XML string.

Used In

Element

value

Type

xsd:string

Usage

CONDITIONAL, MAY use multiple

Definition

A value from a certified list maintained by the Community of Interest (COI) for the referenced element.

Comments

  1. MUST be a properly formed -escaped if necessary- XML string.

Used In


3.2.7 Explicit Addressing

Element

explicitAddressScheme

Type

xsd:string

Usage

REQUIRED, MUST use once and only once

Definition

Identifies the distribution addressing scheme used.

Comments

  1. MUST be a properly formed -escaped if necessary- XML string.

Examples for this type of distribution includes - email, military USMTF, etc. . .

Used In

explicitAddress

Element

explicitAddressValue

Type

xsd:string

Usage

REQUIRED, MAY use multiple

Definition

A properly formed -escaped if necessary- XML string denoting the addressees value.

Comments

  1. MUST be a properly formed -escaped if necessary- XML string.

Used In

explicitAddress


Appendix A. XML Schema for the EDXLDistribution Element

<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:oasis:names:tc:emergency:EDXL:DE:1.0" targetNamespace="urn:oasis:names:tc:emergency:EDXL:DE:1.0" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0CD">

   <xsd:element name="EDXLDistribution">

          <xsd:complexType>

          <xsd:sequence>

                 <xsd:element name="distributionID" type="xsd:string"/>

                 <xsd:element name="senderID" type="xsd:string"/>

                 <xsd:element name="dateTimeSent" type="xsd:dateTime"/>

                 <xsd:element name="distributionStatus" type="statusValues"/>

                 <xsd:element name="distributionType" type="typeValues"/>

                 <xsd:element name="combinedConfidentiality" type="xsd:string"/>

                 <xsd:element name="language" type="xsd:string" minOccurs="0"/>

                    <xsd:element name="senderRole" type="valueListType" minOccurs="0" maxOccurs="unbounded"/>

                    <xsd:element name="recipientRole" type="valueListType" minOccurs="0" maxOccurs="unbounded"/>

                 <xsd:element name="keyword" type="valueListType" minOccurs="0" maxOccurs="unbounded"/>

                    <xsd:element name="distributionReference" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>

                 <xsd:element name="explicitAddress" type="valueSchemeType" minOccurs="0" maxOccurs="unbounded"/>

                 <xsd:element name="targetArea" type="targetAreaType" minOccurs="0" maxOccurs="unbounded"/>

                 <xsd:element name="contentObject" type="contentObjectType" minOccurs="0" maxOccurs="unbounded"/>

          </xsd:sequence>

          </xsd:complexType>

  </xsd:element>

   <xsd:annotation/>

   <xsd:annotation/>

  <xsd:complexType name="contentObjectType">

          <xsd:sequence>

          <xsd:element name="contentDescription" type="xsd:string" minOccurs="0"/>

             <xsd:element name="contentKeyword" type="valueListType" minOccurs="0" maxOccurs="unbounded"/>

             <xsd:element name="incidentID" type="xsd:string" minOccurs="0"/>

             <xsd:element name="incidentDescription" type="xsd:string" minOccurs="0"/>

          <xsd:element name="originatorRole" type="valueListType" minOccurs="0" maxOccurs="unbounded"/>

          <xsd:element name="consumerRole" type="valueListType" minOccurs="0" maxOccurs="unbounded"/>

          <xsd:element name="confidentiality" type="xsd:string" minOccurs="0"/>

          <xsd:choice>

                 <xsd:element name="nonXMLContent" type="nonXMLContentType"/>

                 <xsd:element name="xmlContent" type="xmlContentType"/>

          </xsd:choice>

          <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />

          </xsd:sequence>

  </xsd:complexType>

   <xsd:complexType name="nonXMLContentType">

          <xsd:sequence>

          <xsd:element name="mimeType" type="xsd:string"/>

          <xsd:element name="size" type="xsd:integer" minOccurs="0"/>

          <xsd:element name="digest" type="xsd:string" minOccurs="0"/>

          <xsd:element name="uri" type="xsd:anyURI" minOccurs="0"/>

          <xsd:element name="contentData" type="xsd:base64Binary" minOccurs="0"/>

          </xsd:sequence>

  </xsd:complexType>

   <xsd:complexType name="xmlContentType">

          <xsd:sequence>

          <xsd:element name="keyXMLContent" type="anyXMLType" minOccurs="0" maxOccurs="unbounded"/>

          <xsd:element name="embeddedXMLContent" type="anyXMLType" minOccurs="0" maxOccurs="unbounded"/>

          </xsd:sequence>

  </xsd:complexType>

  <xsd:complexType name="anyXMLType">

          <xsd:sequence>

          <xsd:any namespace="##other" processContents="lax" maxOccurs="unbounded"/>

          </xsd:sequence>

          <xsd:anyAttribute namespace="##other" processContents="lax"/>

  </xsd:complexType>

  <xsd:complexType name="valueListType">

          <xsd:sequence>

          <xsd:element name="valueListUrn" type="xsd:string" />

          <xsd:element name="value" type="xsd:string" maxOccurs="unbounded"/>

          </xsd:sequence>

  </xsd:complexType>

  <xsd:complexType name="valueSchemeType">

          <xsd:sequence>

          <xsd:element name="explicitAddressScheme" type="xsd:string"/>

          <xsd:element name="explicitAddressValue" type="xsd:string" maxOccurs="unbounded"/>

          </xsd:sequence>

  </xsd:complexType>

  <xsd:complexType name="targetAreaType">

          <xsd:sequence>

          <xsd:element name="circle" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>

          <xsd:element name="polygon" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>

          <xsd:element name="country" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>

          <xsd:element name="subdivision" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>

          <xsd:element name="locCodeUN" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>

          </xsd:sequence>

  </xsd:complexType>

  <xsd:simpleType name="statusValues">

          <xsd:restriction base="xsd:NMTOKEN">

          <xsd:enumeration value="Actual"/>

          <xsd:enumeration value="Exercise"/>

          <xsd:enumeration value="System"/>

          <xsd:enumeration value="Test"/>

          </xsd:restriction>

  </xsd:simpleType>

  <xsd:simpleType name="typeValues">

          <xsd:restriction base="xsd:NMTOKEN">

          <xsd:enumeration value="Report"/>

          <xsd:enumeration value="Update"/>

          <xsd:enumeration value="Cancel"/>

          <xsd:enumeration value="Request"/>

          <xsd:enumeration value="Response"/>

          <xsd:enumeration value="Dispatch"/>

          <xsd:enumeration value="Ack"/>            

          <xsd:enumeration value="Error"/>

          <xsd:enumeration value="SensorConfiguration"/>

          <xsd:enumeration value="SensorControl"/>

          <xsd:enumeration value="SensorStatus"/>

          <xsd:enumeration value="SensorDetection"/>

          </xsd:restriction>

  </xsd:simpleType>

</xsd:schema>


Appendix B. EDXL-DE Examples

B.1 EDXL-DE With CAP Payload

The following is a speculative example in the form of an EDXL-DE XML message.

<EDXLDistribution xmlns="urn:oasis:names:tc:emergency:EDXL:DE:1.0">

   <distributionID>ieam_e3_2</distributionID>

   <senderID>XML2005</senderID>

   <dateTimeSent>2005-11-15T16:53:00-05:00</dateTimeSent>

   <distributionStatus>Exercise</distributionStatus>

   <distributionType>Update</distributionType>

   <keyword>

      <valueListUrn>http://www.niem.gov/EventTypeList</valueListUrn>

      <value>Explosion</value>

   </keyword>

   <targetArea>

      <polygon>33.4745,-112.1174 33.4745,-112.0238 33.4238,-112.0238 33.4238,-112.1174 33.4745,-112.1174 </polygon>

   </targetArea>

   <contentObject>

      <contentDescription>CAP message from DOT advising best alternate Routes </contentDescription>

      <xmlContent>

         <embeddedXMLContent>

            <alert xmlns = "urn:oasis:names:tc:emergency:cap:1.1">

               <identifier>Vendor generated</identifier>

               <sender>AZ DOT</sender>

               <sent>2005-11-15T16:58:00-05:00</sent>

               <status>Exercise</status>

               <msgType>Update</msgType>

               <scope>Public</scope>

               <info>

                  <category>Transport</category>

                  <event>Traffic Routes</event>

                  <urgency>Immediate</urgency>

                  <severity>Moderate</severity>

                  <certainty>Likely</certainty>

                  <description>Traffic adjustments ensure clear routes to St. Josephs Hospital and Phoenix Childrens Hospital on Thomas Rd. </description>

                  <area>

                     <areaDesc>Best Routes</areaDesc>

                     <polygon>38.91655012246089,-77.02016267943407 38.91655012246089,-77.0117098391165 38.907662564641285,-77.0117098391165 38.907662564641285,-77.02016267943407  38.91655012246089,-77.02016267943407 </polygon>

                  </area>

               </info>

            </alert>

         </embeddedXMLContent>

      </xmlContent>

   </contentObject>

</EDXLDistribution>


B.2 EDXL-DE With Multiple Encrypted Payloads

The following is a speculative example in the form of an EDXL-DE XML message.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<EDXLDistribution xmlns="urn:oasis:names:tc:emergency:EDXL:DE:1.0">

   <distributionID>Sandia001</distributionID>

   <senderID>dellis@sandia.gov</senderID>

   <dateTimeSent>2005-08-07T18:05:00-07:00</dateTimeSent>

   <distributionStatus>Actual</distributionStatus>

   <distributionType>Report</distributionType>

   <senderRole>

      <valueListUrn>urn:sandia:gov:sensors:senderRole</valueListUrn>

      <value>SENTRY sensor managment system</value>

   </senderRole>

   <!--

   This demonstrates the provison to allow multiple values under the same

   Value List.  <value> is repeated three times, since Warning and reporting

   systems want CAP content, Hazard Prediction systems want detailed sensor

   outputs, and situational awareness systems want the location and type of event.

   -->

   <recipientRole>

      <valueListUrn>urn:sandia:gov:sensors:reciepentRole</valueListUrn>

      <value>Warning and Reporting Devices</value>

      <value>Hazard Prediction applications</value>

      <value>Situational Awarness applications</value>

   </recipientRole>

   <!--

   This key word can be used by subscribing systems or applications

   to get distribution of one or more of the enclosed <contentObject>

   container elements.

   -->

   <keyword>

      <valueListUrn>urn:sandia:gov:sensors:keywords</valueListUrn>

      <value>SNM Detection</value>

   </keyword>

  <!--

   The elements explicitAddress used in this example are DMIS COGs and e-mail.

  Routing of EDXL Distribution is just being designed and there are no good

  way to show real scheme in this example.

   -->

  <explicitAddress>

    <scheme>DMIS COGs</scheme>

    <value>1734</value>

    <value>3520</value>

  </explicitAddress>

  <explicitAddress>

    <scheme>e-mail</scheme>

    <value>dellis@sandia.gov</value>

  </explicitAddress>

   <!-- In a real messaging system this would probably be FOUO or higher

   based on the sensitivity of a SNM detection.  The current confidentiality

   is all unclassified in this example for distribution purposes.

   -->  

   <combinedConfidentiality>Unclassified</combinedConfidentiality>

   <!-- In a real message more than one <targetArea> elements would be present.-->

   <targetArea>

      <!--

      These need to have the correct ISO 3166 codes added

      -->

      <country>US</country>

      <subdivision>California</subdivision>

      <locCodeUN>USA-SF</locCodeUN>

   </targetArea>

   <!--

   This is a XLST transformed CAP 1.0 message for legacy systems.  The message is used by

   publish/subscription software like NuParadigm Foundation engine in the DoD Alerting Framework.

   Legacy Warning and reporting systems would not be able to process a CAP 1.1

   message and therefore a transform was accomplished.

   Most recent information is added to the begining of the Distribution in this example to

   allow rapid determination of most recent key <contentObject> container elements.

   -->

      <contentObject>

         <!-- <contentKeyword> is added to allow referencing between <contentObject>s -->

         <contentKeyword>

            <valueListUrn>"urn:sandia:gov:sensor:detection.event.id"</valueListUrn>

            <value>10.2.2.1:2005-08-07T18:00:00Z</value>

         </contentKeyword>

         <!--

         This could be eliminated since it provides no distribution value but was retained

         to demonstrate the <keyXMLContent> would have to be transformed in CAP 1.1 to CAP 1.0

         Conversions

         -->

         <confidentiality>Unclassified</confidentiality>

         <xmlContent>

         <embeddedXMLContent xmlns:cap1.0="http://www.incident.com/cap/1.0">

            <EncryptedData xmlns="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element">

<EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>

<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">

<KeyName>deskey.bin</KeyName>

</KeyInfo>

<CipherData>

<CipherValue>GSCinwYBtwJxp6kcZPGqE6rybCfsnvI6Lz+IZVPqnRfnI1hWq7cI2WT4BsjBBQCu

TE68pCQ/keOGtvYJ5yNVZEuAnIhOf37OEiqk1rcBARXb03LCYvlXYKA1zmEC5yFT

CUcyCMV146G4eNU1H7F+wbMjbSgHjOYgYe+rpjOVYAK9Gs4Uj+CWhijjxpr5Y/vX

1NEtHFhLsXC9cSfhXWVmi3veXwbDycC+QtcvQL/Rfr45bDwsJnCCutTzfmoqF1CS

BgYUi6osW+XhoRkAttzKbRADVZ6bG5SMkZN0SKiwSaCyKyMKjdpiQwYQhjUXUoAn

veBylXREqfmtOIm/pT7Y45pabWNG9l3aljil8P7qZ5Y26Q0X+i0U+eEGuafHrMVb

S/QBpAkNbP5/f9UR3B4t5t7hLOsvDXdR6CWFBNsrczLjZ7YC2O+g1HBl8YsQdREA

And3PKgoy8QlKv6ZLA+aJzQpSvzbSu3btgN6vyF3GGPqKprVIYRFouaJHYgL81zn

zZovnH4lubwa+YPgD0H48a/FM2LaA8euPzMFDWIki0fm5DoZZzYCmPKmfLJS10RG

lUKzW0svDw8I1AwX6LBssPm+hoBa7HzTnuM40FD+vsmET+p0bqBtaUSnDHrHXLzp

P6TrcNr5R5cxQ4C+shwezFQDNKbioyC6m5PaTH/6qhlTmE32vP8ySnMKvL74QCfP

w8hTZxwq9UVLPq2WKJcI0Phc1e3HoYkBTpVk9OUf/CVaxMXGOiXReeLXGPC1IQnn

a6xw7ImkgeCFcY+rcttq2fE3UqWtc5R6J16/Jv666K9fgCbXRVhaBdMDYpz0GKFa

gMJulUK6zTtah+bidtUrF31UWAX+wqIqmDFJ1ivJaRbLEiEVCrt0jKwOjuR41dDD

VS5j2BuvmZ5TILnOnHFU6H4GudnwjpL01eLrwELSfKmbQmUx2A0L6NBj9SRkXXHW

onZV6uX+c3CR46OekvxYyMi1rxE2zQPykfh/mELRhGgyDVqtdFQwhDx2Klu+Gh2z

3nC51yn37laIO5KSvL5Gkb6jxFVrcUvrcp4pX5czw7/VWbxWoRPY7Bus3akhPu+I

/jchv7SiVRP5mX4Ewh+yeduYX+UZLo07m5zhAMtmFdiLJV9tgHVTJf7ZJ3bGWP+h

Et0Nl98hGV362cSRhkoLJwNmOgIpGXSMO6T5nA1MZhJ6CkCP8QV1zpKrLVJSRZRn

fffBjdl8CzipzjE05JVKbyfbq9I33fkWMbda+Vo9ZMiDinOee6KxnDnxll9ca9Lg

+dl9J0qjJz5VwnWLRCeprsOXt+LlmeHC60NJgRarhidlrfuxmONM+QZTk4ZQGIPD

fsk5ftJtzvHgW5G/wN7fxyLh1AqQucW13IAsmfwuJS0+HntYZVoXqGjRg1sK6snx

zteJJm6a2OyG/M5RvLAEVhOKWyU2+9hjzts8ySg6Qb2+KrUTRQ8JBmVBeSjR2svv

2AWyBYj29JAdAikX9gfGDDvTG9GqJr+jFE9mfOBtg7lsdLezQKvvNMsntm6RdSpu

dA3vL8uBIliGBNJZSOOKr06BXp6PjbL6Ov47EbOfvP8Vm9vKQD7PmjPaIbN1bUr9

V9cHUQ5h6LSecnAy/FZQMLdcamNAIhpiEgoQcwEmaa+1/wTv7LppqxZkFVQQbI2m

nC9Ujcd08g2Qyh+0YCHP50SbCwDe2W+CYBi7QBDdF3qt45zaZnHyRm/yXhVWCJX1

+0WY/+OukquhaWJ8Y0fygA1yk7Jyqqpu2XU9X0Vu8oETQlL/+37mEzy/beL9VNnr

eU7bfQBAnYw1CkeXs5rAcc1vllZEU22Uqg3H5saOQlEHgV1NxL+0C+A9/Q2ZsaFI

BDDIiH+f6+6aUno6fotGUA==</CipherValue>

</CipherData>

</EncryptedData>

         </embeddedXMLContent>

         </xmlContent>

      <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">

<SignedInfo>

<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>

<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>

<Reference>

<Transforms>

<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>

</Transforms>

<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>

<DigestValue>przigAg811cHIqSXpIrFg1BGx20=</DigestValue>

</Reference>

</SignedInfo>

<SignatureValue>BH8MGSS9QAlgq7a7I7PF5XjKsqaDumTt3cSWxBmwErByvQuaarOgH6MMflVLkG0Y

tv6zaOqR6Kis4giTqtZBo8QCkGukpre2gurdi3Ws0yO3Wt8nWrcH3QAUllhocXpV

gXahZ8MzHc9zuJq9+bl+S72czTjS0UdCvk/MMRV/xhwZ/1QSn+ffh0s3RU6Cn1Q0

aYSuDtX5mAGUWAzJghKgK/qSM5jF4c233g7M4m+Rul3C+QOFBOMGmp+NodnG9b0z

hycJGVdUpY0a+1r0quu2pmdLZnIQVY1stWNFS3wI9RzdslwzoGP9/nRARGS0kLf1

De+WB4Xdar48A9WJwng0iA==</SignatureValue>

<KeyInfo>

<KeyName>rsakey.pem</KeyName>

</KeyInfo>

</Signature></contentObject>

   <!--

   This is the original CAP 1.1 message produced by the SENTRY system.

   There was sufficent data to warrant the alert.

   In reality the CAP messages would not be Public, however, It is used in this

   for simplicity

   -->

   <contentObject>

      <contentKeyword>

         <valueListUrn>"urn:sandia:gov:sensor:detection.event.id"</valueListUrn>

         <value>10.2.2.1:2005-08-07T18:00:00Z</value>

      </contentKeyword>

      <confidentiality>Unclassified</confidentiality>

      <xmlContent>

          <embeddedXMLContent xmlns:cap1.1="urn:oasis:names:tc:emergency:cap:1.1">

         <EncryptedData xmlns="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element">

<EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>

<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">

<KeyName>deskey.bin</KeyName>

</KeyInfo>

<CipherData>

<CipherValue>MiKRUfL1Yb3Vw9JcewTAYVnYT3Zh2Tf9d0fhRyGreJW0FWoXr1/27AXFXBTmZC/2

hw9cMMFaGKeXNr1tK0Os1Lozx9uZZYoF5UiNH18KD/WnNbpwk+ttK3TwRcxBfowm

lzzClMn5suHeUM2PFiCll1Wup8cSfwAqptXVF3sZrLAMsQWJmGfyGYYCiaZ+P3NZ

hiVFamDB7D9id5HJ3qHLNcxucGNFA5TfOwe/euP7O1ah9Q7Rp2nxsXF9PaQYziSS

G4I/J+v+FwuJXhbLqU1PcbP4ofCLg+s6tph2kJxFArGSX9u3k7FHvp3tLZnskXCw

iYRGDqrSGrmLt7bTtMmF/IhFQc4x0aE4ldVEN999uQ6KnDyd22KdUJhupRH8UqZz

+sKVJF3+yatOsroCwOCjTe/GqnNRZNtG59dGC5D247LH2AVn/6WU+txFflZhUg0z

A0PElIMicguTRaEaIDGJF/QvqzTE1r3iYgHXIGfgEhQiix35ZURWUTcATrKyNFFE

/CD8+v6YHGbKrgeJDnvJ5AqjZSU1NajOpCtbhWQm1D878OhjCN+T689PZPB2X2nz

f1kupkZ/Fq6Z6aF77j0xp4wB7bpFW5ssWUHySwdg5vYw4hS3Geg5wn3AQViqTGI8

oRaDa3wT9byHq+cq83WqA3aroJOXzD/HQCmKNhmPFqYj503JH3aZcWNrDxHyBQRr

Libv4o9v4LCGviaKT/2y0S25t5KkL/MJA2c6LIngmhHKQFr1sruWgSrjHn9KtagU

KeYqYlgKK6s56X+PHQvusXoxpgDLjXpVVhNpF/mRh+86J4zY3JAIcfIZJQ05DjvX

io2iZY/hstzkTfY5+CPvKH7FmuYqeoU7Nano7+EGSB4w0TnSoDfm9D/RIsAtwdpu

7WonmeguEK37u0bNuXQHi9LZTELD0L2HIkPVdo4BYq26WMe5vZdwVkW6up92AIQE

7KvADQZZUGDVoKA3Njt9O5s6g+a14wcHqxD+FS8veacDsYFrmhs+0WYlyWtDJERL

+y0qtHLmSi/kTdYoKRGx+/lyUl8FIfqOnk2dk3BicbQ3kyEbngV3qHBrYqrVITTB

eMUKxL3wB5OkcCn3u6Nqun14QFmf8O9KEZGXZZqdQs7jz6MV3yjPvzelmLs9nbCm

3eXFGrSlHbbwCLQBconzDWgfoN6W/lTRv3z8RmTg+Z+3CjK2MRt6x5XZTcDqk4JW

wozh2btLz4Yc2xUbclbtVd3muOhBq3eSsGXC6xX4fxW0cuqi6UsOZRA2kiKJHY+V

2KFO9/y3x4arscIsBwfmNVZYt6bCoy/Or0yva49yV/A//8JFN7aGLh530Dt53J4H

bcsQ1n3q7kxir5VLuNj0aZYHjtGu7gzPa1UpPAJ0trqro4qinspnkdRueW7SQYcd

ufF5OG4GMTI+VjX4MnOMOgnYiAaZqrBoH3B5t7bAKeszVPs6S9NPfkzx1nkqminG

/Z/hBpmsFlcUlS+qylXU7umHvssE2juap1NQUaL6IyHQ0tZzsQd0e6mYkDuzNNbH

4l9czPXXXfvcKRJnJ0Yho9j30YfBWyllF67SMewYhcNg35tAbstXe+Ghg+D/TVcd

SZ4r1Cmk49IQE3SNwIO6vGUtMhmCJGq+yJx89lfMLijZRBr18exdQ1hoVeQ+YzyY

rZ/e6PTZHVkbcHGLsd+InyBdz3MTCmaYLGGG6gGtL42nJYmXDUIwWTAFXcWo0jDh

HO28OimZg8QGhiSAAc8uXzwbtjVHIJTC27e6iqldNxnYDoNWDZxVjI3fccbvUwmz

702I+4Kb/n5M1X5RXeMZ12OvlRRnQi7nhZuTeTMEbRizHptWP5yse3LcNjRJ2Jr2</CipherValue>

</CipherData>

</EncryptedData>

          </embeddedXMLContent>

      </xmlContent>

   <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">

<SignedInfo>

<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>

<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>

<Reference>

<Transforms>

<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>

</Transforms>

<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>

<DigestValue>N7NvgXfahdGZPjb9o0XvwejLI5o=</DigestValue>

</Reference>

</SignedInfo>

<SignatureValue>Tg8zP+/1Cg/3MR9iSareJb7snexQ3DjBxGSL3xH+Kf3Kh5NQq/Uwagw/fmI2wcxc

ac/2fz893HeTkXGn8mShg+wmdoRwNykp5uHPtAzcFBKlh3v7FemtM9M73XbX7KsY

fM0J+RTHUxp4tTMYUPogSEJWiSGSGVbp+MALtUH799fGqqqOREyuljfVIlLvvCog

wOd6n7J8S2sHjyRXEw5AVFnxL6k02TgjztbEuoLu+qvEZOIGXmj9yfy4nj41RNXe

HMOS1IAcOQgx5vNzju2slFIWzlmvjqq+7aVg5hy0yBiXJuljvigTOxrwHScaYW8o

HDpQHwM6EXbgW3uaWnf9Kg==</SignatureValue>

<KeyInfo>

<KeyName>rsakey.pem</KeyName>

</KeyInfo>

</Signature></contentObject>

   <contentObject>

      <contentDescription>Photo image from Sensor: RADDET-01, Site: Golden Gate Bridge, having a Detection class of SNM</contentDescription>

      <contentKeyword>

         <valueListUrn>"urn:sandia:gov:sensor:detection.event.id"</valueListUrn>

         <value>10.2.2.1:2005-08-07T18:00:00Z</value>

      </contentKeyword>

      <confidentiality>Unclassified</confidentiality>

      <nonXMLContent>

          <mimeType>image/jpeg</mimeType>

          <uri>http://sentry/photoCapture/10.2.2.1:2005-08-07T18:00:00Z</uri>

      </nonXMLContent>

   <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">

<SignedInfo>

<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>

<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>

<Reference>

<Transforms>

<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>

</Transforms>

<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>

<DigestValue>io7Katgoo77YNfQYdZMB8taoeKg=</DigestValue>

</Reference>

</SignedInfo>

<SignatureValue>AjQXGgp9h5TC2D+bh9w59sbmtUpgE/IeZVdDQM+zi58XT2RPb7OXAAABni78WduA

uP6nxL6k+BBo4G+TgaqWvCQIqdlDO+qyMnM0ExPui5eg00jstbwiSeYxSt2VQqS2

RD2vR811at0XwIkMpugSftKNJBZgB9mhRqQgP+E0nDJJPNYDz0bLJjp0J/EDxn4H

6qx6GpDKgDc//53jVhOb4zZPIERsTLjPxpOOnBK31cs5Rf6vU9MyOOBTHZgpvoza

muhejW1CIJfYjd/OoKQ9Hiv4MCX4v/dX7n6ePHZaDxNeCccDIjoVYrAHEWxQ9hE6

rqriugNLZ3Lh8sUzhZLTyg==</SignatureValue>

<KeyInfo>

<KeyName>rsakey.pem</KeyName>

</KeyInfo>

</Signature></contentObject>

   <!--  This is the based 64 encode image of the Suspect vehicle with SNM.

   This data is provide for Law Enforcement senstive systems to redistribute

   on private systems which do not have intenet access.

   -->

   <contentObject>

       <contentDescription>Photo image from Sensor: RADDET-01, Site: Golden Gate Bridge, having a Detection class of SNM</contentDescription>

       <contentKeyword>

      <valueListUrn>"urn:sandia:gov:sensor:detection.event.id"</valueListUrn>

      <value>10.2.2.1:2005-08-07T18:00:00Z</value>

       </contentKeyword>

       <confidentiality>Unclassified</confidentiality>

       <nonXMLContent>

         <mimeType>image/jpeg</mimeType>

         <contentData>

      /9j//gAoaAkAAAAAAECMWv/mOzNdGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD/2wBDAAgGBgcGBQgH

      BwcJCQgKDBQNDAsLDBkSEw8UHRofHh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/

      AYG3nGaeEI5BoACp6gmmgKwOBzQBFICRUZXIwOKAE8sjmms5Uc0AU5JwTioxLjpQBHIc5qpJQBGr

      YNSgjFACbuacQCtAEIXDVOOlACgUuAaAG4xVbUP+Qdc/9czQB//Z

      </contentData>

       </nonXMLContent>

   <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">

<SignedInfo>

<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>

<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>

<Reference>

<Transforms>

<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>

</Transforms>

<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>

<DigestValue>PkrjafcKUd027EETVu5JwqlubcA=</DigestValue>

</Reference>

</SignedInfo>

<SignatureValue>NvqlkBLs4GpM+t+uoWQ53rmjNT43qdwbMsEoiB0a2BRwqkmynKQDbA2eIHmxfBfo

xe+q+15v/2IGQQw+5XmWtMx8QIQkGBElSdlybOKibxBqNuWH+J6yR1mIA6bOmBE+

+F2zA9DuvKZVLa8El1pUGke6FeIzoMC7TdDcBtmSAkRMXxe8MjxjxApM3vnMSt9A

iCo2EUx4qYf82iJ9FX7vIFFfL2QW38RvZqY+rjXsHV5OK3fkTPFI+ZE5lIrHKjb3

gu409JrdNtSy/wLd/WLypiYFNDZXxT6i5wBbdAvBkQ0jHECOJjfN+h1bHkvT4wLX

Cpc26QQ6Ic3goSLojC3rjw==</SignatureValue>

<KeyInfo>

<KeyName>rsakey.pem</KeyName>

</KeyInfo>

</Signature></contentObject>

   <!--

   The following content object contains the readings from a UNWD radiation Portal

   The Detection ID is being used to correlate other contentObject container elements to

   the data found in this detection

   Because there is no provision for Location information in the current metadata situational

   awareness systems would have to extract location for the contents of related CAP messges.

   -->

</EDXLDistribution>


Appendix C. Acknowledgments

C.1 OASIS Emergency Management Technical Committee:


Appendix D. Revision History

Revision

Date

Editor

Changes Made