[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency] Groups - EDXL DE spec to date(XHTML_EDXL_DE_spec081505.html) uploaded
Gary, I've attached the schema I doctored to have the comments in it. I'll look at why the lines don't wrap in the html. -Michelle On 8/16/05, Ham, Gary A <hamg@battelle.org> wrote: > Unfortunately I cannot read the schema as layed out (no line breaks). > This is kind of funny because they are there in the examples. > > Gary A. Ham > Senior Research Scientist > Battelle Memorial Institute > 540-288-5611 (office) > 703-869-6241 (cell) > "You would be surprised what you can accomplish when you do not care who > gets the credit." - Harry S. Truman > > > -----Original Message----- > From: michellearaymond@gmail.com [mailto:michellearaymond@gmail.com] > Sent: Monday, August 15, 2005 10:32 PM > To: emergency@lists.oasis-open.org > Subject: [emergency] Groups - EDXL DE spec to > date(XHTML_EDXL_DE_spec081505.html) uploaded > > > The document revision named EDXL DE spec to date > (XHTML_EDXL_DE_spec081505.html) has been submitted by Michelle Raymond > to the OASIS Emergency Management TC document repository. This document > is revision #4 of XHTML_EDXL_DE_spec080805.html. > > Document Description: > This is likely the last pass before we talk, so get out the tweezers (or > crowbars) and write up your nits and suggestions. > > > There is still content addition, cleanup and review to do. > > View Document Details: > http://www.oasis-open.org/apps/org/workgroup/emergency/document.php?docu > ment_id=14057 > > Download Document: > http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/1405 > 7/XHTML_EDXL_DE_spec081505.html > > Revision: > This document is revision #4 of XHTML_EDXL_DE_spec080805.html. The > document details page referenced above will show the complete revision > history. > > > PLEASE NOTE: If the above links do not work for you, your email > application may be breaking the link into two pieces. You may be able > to copy and paste the entire link address into the address field of your > web browser. > > -OASIS Open Administration >
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:ed="urn:oasis:names:tc:emergency:EDXL:DE:1.0"
targetNamespace="urn:oasis:names:tc:emergency:EDXL:DE:1.0"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<!--
In a closed system where all content must be validated imports of allowed namespaces could be included:
<import namespace="urn:oasis:names:tc:emergency:cap:1.1" schemaLocation="file://c://schemas//CAP1_1.xsd" />
<import namespace="http://www.incident.com/cap/1.0"; schemaLocation="file://c://schemas//CAP1_0.xsd" />
<import namespace="http://www.dtra.mil/acrs/event"; schemaLocation="file://c://schemas//UNWDSensorEvent.xsd" />
-->
<element name="EDXLDistribution">
<annotation>
<documentation>
The container of all of the elements related to the distribution of the content messages.
</documentation>
<documentation>
1. The <EDXLDistribution> element may include <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.
</documentation>
</annotation>
<complexType>
<sequence>
<element name="distributionID" type="xsd:string">
<annotation>
<documentation>
The unique identifier of this distribution message.
</documentation>
<documentation>
Uniqueness is assigned by the sender to be unique for that sender.
</documentation>
</annotation>
</element>
<element name="senderID" type="xsd:string">
<annotation>
<documentation>
The unique identifier of the sender.
</documentation>
<documentation>
1. In the form actor@domain-name.
2. 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.
</documentation>
</annotation>
</element>
<element name="dateTimeSent" type="xsd:dateTime">
<annotation>
<documentation>
The date and time the distribution message was sent.
</documentation>
<documentation>
1. The Date Time combination must include the +/- offset time for time zone.
2. Must be in the ISO-8601 format for the XML DateTime data type.
Example: 2004-08-01T16:49:00-07:00
</documentation>
</annotation>
</element>
<element name="distributionStatus">
<annotation>
<documentation>
The actionability of the message.
</documentation>
<documentation>
Value must be one of:
Actual - "Real-world" information for action
Exercise - Simulated information for exercise participants
System - Messages regarding or supporting network functions
Test - Discardable messages for technical testing only
</documentation>
</annotation>
<simpleType>
<restriction base="xsd:string">
<enumeration value="Actual"/>
<enumeration value="Exercise"/>
<enumeration value="System"/>
<enumeration value="Test"/>
</restriction>
</simpleType>
</element>
<element name="distributionType">
<annotation>
<documentation>
The function of the message.
</documentation>
<documentation>
Value must be one of:
Report - New information regarding an incident or activity
Update - Updated information superseding a previous message
Cancel - A cancellation or revocation of a previous message
Request - A request for resources, information or action
Response - A response to a previous request
Dispatch - A commitment of resources or assistance
Ack - Acknowledgment of receipt of an earlier message
Error - Rejection of an earlier message (for technical reasons)
</documentation>
</annotation>
<simpleType>
<restriction base="xsd:string">
<enumeration value="Ack"/>
<enumeration value="Cancel"/>
<enumeration value="Dispatch"/>
<enumeration value="Error"/>
<enumeration value="Report"/>
<enumeration value="Request"/>
<enumeration value="Response"/>
<enumeration value="Update"/>
</restriction>
</simpleType>
</element>
<element name="senderRole">
<annotation>
<documentation>
The functional role of the sender, as it may determine message routing decisions.
</documentation>
<documentation>
1. The list, value pair 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 <valueListUrn>, <value> pairs MAY occur within a single <senderRole> structure.
3. Multiple instances of <senderRole> MAY occur within a single <EDXLDistribution> block.
</documentation>
</annotation>
<complexType>
<sequence>
<element ref="ed:valueListUrn">
<annotation>
<documentation>
The content of "valueListUrn" is the Uniform
Resource Name of a published list of values and definitions.
</documentation>
</annotation>
</element>
<element ref="ed:value">
<annotation>
<documentation>
The content of "value" is a string (which may represent a number)
denoting the value itself.
</documentation>
</annotation>
</element>
</sequence>
</complexType>
</element>
<element name="recipientRole" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
The functional role of the sender, as it may determine message routing decisions.
</documentation>
<documentation>
1. The list, value pair is in the form:
<recipientRole>
<valueListUrn>valueListUrn</valueListURN>
<value>value</value>
</reciepientRole>
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 <valueListUrn>, <value> pairs MAY occur within a single <recipientRole> structure.
3. Multiple instances of <recipientRole> MAY occur within a single <EDXLDistribution> block.
</documentation>
</annotation>
<complexType>
<sequence>
<element ref="ed:valueListUrn">
<annotation>
<documentation>
The content of "valueListUrn" is the Uniform
Resource Name of a published list of values and definitions.
</documentation>
</annotation>
</element>
<element ref="ed:value">
<annotation>
<documentation>
The content of "value" is a string (which may represent a number)
denoting the value itself.
</documentation>
</annotation>
</element>
</sequence>
</complexType>
</element>
<element name="keyword" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
The topic related to the distribution message, as it may determine message routing decisions.
</documentation>
<documentation>
1. The value list pair 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. Examples of things <keyword> might be used to describe include event type, event etiology, incident ID and response type.
3. Multiple instances of the <valueListUrn>, <value> pairs MAY occur within a single <keyword> structure.
4. Multiple instances of <keyword> MAY occur within a single <EDXLDistribution> block.
</documentation>
</annotation>
<complexType>
<sequence>
<element ref="ed:valueListUrn">
<annotation>
<documentation>
The content of "valueListUrn" is the Uniform
Resource Name of a published list of values and definitions.
</documentation>
</annotation>
</element>
<element ref="ed:value">
<annotation>
<documentation>
The content of "value" is a string (which may represent a number)
denoting the value itself.
</documentation>
</annotation>
</element>
</sequence>
</complexType>
</element>
<element name="explicitAddress" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
The identifier of an explicit recipient.
</documentation>
<documentation>
Identifies human parties, systems, services, or devices that are all potential recipients of the distribution message.
</documentation>
</annotation>
</element>
<element name="distributionReference" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
A reference to a previous distribution message.
</documentation>
<documentation>
1. The <distributionID> and <senderID> and <dateTimeSent> of the referenced previous message, concatenated with a ":" delimiter.
2. This element should appear at least once in any message which updates, cancels or otherwise refers to another message.
Example: msgID0074:actor@domain-name:2004-08-01T16:49:00-07:00
</documentation>
</annotation>
</element>
<element name="combinedConfidentiality" type="xsd:string" minOccurs="0">
<annotation>
<documentation>
Confidentiality of the combined distribution message's content.
</documentation>
<documentation>
1. The <combindedConfidentiality> indicates the confidentiality of the combined <messageObject> sub-elements. Generally the combined confidentiality is the most restrictive of the <confidentiality> elements in the container <messageObject> element, but it can be more restrictive than any of the individual <confidentiality> elements.
2. If this element is not present, all content messages are assumed to be unclassified and not sensitive.
3. The <combindedConfidentiality> element MUST be present if a confidentiality element is present in any of the contentObject elements.
4. Application specific mechanisms will be required to determine the minimum confidentiality level in cases where different confidentiality schemes are used in the contentObject.
</documentation>
</annotation>
</element>
<element name="targetArea" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
The container element for location information.
</documentation>
<documentation>
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.
</documentation>
</annotation>
<complexType>
<sequence>
<element name="circle" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
An enclosed geographic area within a given radius around a geographic point.
</documentation>
<documentation>
1.Represented in the form "latitude, longitude radius".
2. The central point is represented by lat-long values conforming to the WGS84 coordinate reference system.
3. The fixed mandatory attribute of "urn:ogc:def:crs:OGC:1.3:CRS84" must be included.
4. The radius value is expressed in kilometers.
Example: 38.26295, -122.07454 15
</documentation>
</annotation>
</element>
<element name="polygon" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
An enclosed geographic area within a simple closed polygon defined by an ordered set of vertices.
</documentation>
<documentation>
1. Represented by a space-delimited series of latitude, longitude pairs, with the last pair identical to the first.
2. The lat-long values conform to the WGS84 coordinate reference system.
3. The fixed mandatory attribute of "urn:ogc:def:crs:OGC:1.3:CRS84" must be included.
Example: 42,-124.2102 42,-120.1 39,-120 35.0,-114.6328 34.35,- 120.4418 38.9383,-123.817 42,-124.2102
</documentation>
</annotation>
</element>
<element name="country" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
The code of the country.
</documentation>
<documentation>
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.
</documentation>
</annotation>
</element>
<element name="subdivision" type="xsd:string" minOccurs="0">
<annotation>
<documentation>
The ISO 3166-2 designator for the administrative subdivision concerned.
</documentation>
<documentation>
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.
Examples: US-TX (U.S. State of Texas), DK-025 (Danish county Roskilde), MG-T (Antananarivo province, Madagascar)
</documentation>
</annotation>
</element>
<element name="location" type="xsd:string" minOccurs="0">
<annotation>
<documentation>
The UN/LOCODE designator for the location concerned.
</documentation>
<documentation>
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.
Example: USFFB (Fairfield, Alabama, USA), USSUU (Fairfield, California, USA), GBFFD (Falfield, South Gloucestershire, UK)
</documentation>
</annotation>
</element>
</sequence>
</complexType>
</element>
<element name="contentObject" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
The container element for message data and content.
</documentation>
<documentation>
1. The <contentObject> element is the container element for specific messages.
2. The <contentObject> element MUST either contain one <derefUri>, for base-64 encoded data content, one <uri>, for a reference to content location, or one <namespaceXmlContent>, for valid namespaced XML content.
</documentation>
</annotation>
<complexType>
<sequence>
<element name="contentKeyword" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
The topic related to the message data and content, as it may determine message distribution and presentation decisions.
</documentation>
<documentation>
1. The value list pair is in the form:
<cntentKeyword>
<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. Examples of things <contentKeyword> might be used to describe include message processor, event stage, resource code and response type.
3. Multiple instances of the <valueListUrn>, <value> pairs MAY occur within a single <contentKeyword> structure.
4. Multiple instances of <contentKeyword> MAY occur within a single <contentObject> block.
</documentation>
</annotation>
<complexType>
<sequence>
<element ref="ed:valueListUrn">
<annotation>
<documentation>
The content of "valueListUrn" is the Uniform Resource Name of a published list of values and definitions.
</documentation>
</annotation>
</element>
<element ref="ed:value">
<annotation>
<documentation>
The content of "value" is a string (which may represent a number) denoting the value itself.
</documentation>
</annotation>
</element>
</sequence>
</complexType>
</element>
<element name="keyXMLContent" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
A container element for collected fragments of a valid XML.
</documentation>
<documentation>
1. Extracts must come from the XML document contained within the <namespacedXmlContent> element within the current <contentObject> block.
2. All content within this element MUST be explicitly namespaced as defined in the enclosing <namespacedXmlContent> tag.
</documentation>
</annotation>
<complexType>
<sequence>
<any namespace="##any" processContents="lax" maxOccurs="unbounded"/>
</sequence>
<anyAttribute namespace="##other" processContents="lax"/>
</complexType>
</element>
<element name="originatorRole" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
The functional role of the message originator, as it may determine message distribution and presentation decisions.
</documentation>
<documentation>
1. The list, value pair 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 <valueListUrn>, <value> pairs MAY occur within a single <originatorRole> structure.
3. Multiple instances of <originatorRole> MAY occur within a single <EDXLDistribution> block.
</documentation>
</annotation>
<complexType>
<sequence>
<element ref="ed:valueListUrn">
<annotation>
<documentation>
The content of "valueListUrn" is the Uniform Resource Name of a published list of values and definitions.
</documentation>
</annotation>
</element>
<element ref="ed:value">
<annotation>
<documentation>
The content of "value" is a string (which may represent a number) denoting the value itself.
</documentation>
</annotation>
</element>
</sequence>
</complexType>
</element>
<element name="consumerRole" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>
The functional role of the message consumer, as it may determine message distribution and presentation decisions.
</documentation>
<documentation>
1. The list, value pair 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 <valueListUrn>, <value> pairs MAY occur within a single <consumerRole> structure.
3. Multiple instances of <consumerRole> MAY occur within a single <contentObject; block.
Example: <valueListUrn>"http://www.dhs.gov/NiemRoleType"</valueListUrn>, <value>ICS Operations Branch</value>
</documentation>
</annotation>
<complexType>
<sequence>
<element ref="ed:valueListUrn">
<annotation>
<documentation>
The content of "valueListUrn" is the Uniform Resource Name of a published list of values and definitions.
</documentation>
</annotation>
</element>
<element ref="ed:value">
<annotation>
<documentation>
The content of "value" is a string (which may represent a number) denoting the value itself.
</documentation>
</annotation>
</element>
</sequence>
</complexType>
</element>
<element name="confidentiality" type="xsd:string" minOccurs="0">
<annotation>
<documentation>
Special requirements regarding confidentiality of the content of this <messageElement>.
</documentation>
</annotation>
</element>
<element name="description" type="xsd:string" minOccurs="0">
<annotation>
<documentation>
The human-readable text describing the content object.
</documentation>
<documentation>
Examples: "CAP message from FEMA", "Map of affected area" or "Photo of missing child".
</documentation>
</annotation>
</element>
<element name="mimeType" type="xsd:string">
<annotation>
<documentation>
The format of the content.
</documentation>
<documentation>
MIME content type and sub-type as described in [RFC 2046].
Examples: application/pdf, text/xml
</documentation>
</annotation>
</element>
<element name="size" type="xsd:integer" minOccurs="0">
<annotation>
<documentation>
The file size of the content object item.
</documentation>
<documentation>
Value must be in bytes and represent the raw file size (not encoded or encrypted).
</documentation>
</annotation>
</element>
<element name="digest" type="xsd:string" minOccurs="0">
<annotation>
<documentation>
The digital digest ("hash") of the content item.
</documentation>
<documentation>
1. Used to ensure the integrity of the content object.
2. Calculated using the Secure Hash Algorithm (SHA-1) per [FIPS 180-2]
</documentation>
</annotation>
</element>
<choice id="contentContainer" maxOccurs="1">
<element name="uri" type="xsd:anyURI" minOccurs="0">
<annotation>
<documentation>
A Uniform Resource Identifier that can be used to retrieve the identified resource.
</documentation>
<documentation>
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 a reference to a file or specifically to the file represented in the <derefUri>.
</documentation>
</annotation>
</element>
<element name="derefUri" type="xsd:string" minOccurs="0">
<annotation>
<documentation>
The base-64 encoded data content.
</documentation>
<documentation>
MAY be used either with or instead of the <uri> element in contexts where retrieval of a resource via a URI is not feasible.
</documentation>
</annotation>
</element>
<element name="namespacedXMLContent" maxOccurs="1">
<annotation>
<documentation>
The Content XML element is an open container for valid XML from an explicit namespaced XML Schema.
</documentation>
<documentation>
1. The content MUST be a separately-namespaced XML document.
2. The enclosed XML content MUST be explicitly namepaced as defined in the enclosing <namespacedXMLContent> tag.
3. Enclosed XML content may be encrypted and/or signed within this element.
</documentation>
</annotation>
<complexType>
<sequence>
<any namespace="##other" processContents="lax" maxOccurs="unbounded"/>
</sequence>
<anyAttribute namespace="##other" processContents="lax"/>
</complexType>
</element>
</choice>
</sequence>
<anyAttribute namespace="##other" processContents="lax" />
</complexType>
</element>
</sequence>
</complexType>
</element>
<element name="value" type="xsd:string">
<annotation>
<documentation>
A value from a certified list maintained by the Community of Interest (COI)
for the referenced element.
</documentation>
</annotation>
</element>
<element name="valueListUrn" type="xsd:string">
<annotation>
<documentation>
The name of the certified list maintained by the Community of Interest (COI)
for the value referenced.
</documentation>
</annotation>
</element>
</schema>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]