EDXL DE "issue" location metadata for <contentObject>

["Ellis, David" <dellis@sandia.gov>]

EM TC

 

There needs to be a way to provide <contentObject> origination location metadata for sources of <namespacedXMLContent>.

 

Rationale:  Many fixed sensors do not report their location while reporting a potential detection.  This can be for many reasons form design limitations to security of wireless transmission of detection.

 

I suggest using labels the following schema (similar to CAP 1.1 and/or CAP 1.0) but names of elements could be changed for clarity.

 

<element name = "XMLContentLocation" minOccurs = "0" maxOccurs = "1">

   <complexType>

       <sequence>

           <element name = "locationLabel" type = "string"/>

           <element name = "location" type= “string”/>

       </sequence>

   </complexType>

</element>

 

This would allow for easy transform and inclusion in CAP messages generated after assessing the detection is a valid threat. I am a little concerned with the difference in schema structure between CAP 1.0 Standard and CAP 1.1 Standard (e.g. List versus string) but believe the transform of “locationLabel” to “areaDesc” a mandatory element and “location” to “circle” will provide the functionality needed and also allow GIS systems the minimal data needed to directly display a reported detection.

 

This is the CAP 1.0 structure.

 

<element name = "area" minOccurs = "0" maxOccurs = "unbounded">

   <complexType>

       <sequence>

           <element name = "areaDesc" type = "string"/>

           <element name = "polygon" minOccurs = "0" maxOccurs = "unbounded">

           <element name = "circle" minOccurs = "0" maxOccurs = "unbounded">

           <element name = "geocode" type = "string" minOccurs = "0" maxOccurs = "unbounded"/>

                <complexType>

                      <sequence>

                            <element ref “cap:valueName” />

                            <element ref “cap:valueName” />

                     </sequence>

                </complexType>

           </element>

           <element name = "altitude" type = "string" minOccurs = "0"/>

           <element name = "ceiling" type = "string" minOccurs = "0"/>

       </sequence>

   </complexType>

</element>

 

This is the CAP 1.0 structure.

 

<element name = "area" minOccurs = "0" maxOccurs = "unbounded">

   <complexType>

       <sequence>

           <element name = "areaDesc" type = "string"/>

           <element name = "polygon" minOccurs = "0" maxOccurs = "unbounded">

                <simpleType>

                    <list itemType = "string"/>

                </simpleType>

           </element>

           <element name = "circle" minOccurs = "0" maxOccurs = "unbounded">

                <simpleType>

                    <list itemType = "string"/>

                </simpleType>

           </element>

           <element name = "geocode" type = "string" minOccurs = "0" maxOccurs = "unbounded"/>

           <element name = "altitude" type = "string" minOccurs = "0"/>

           <element name = "ceiling" type = "string" minOccurs = "0"/>

       </sequence>

   </complexType>

</element>

 

David E. Ellis

Information Management Architect

(505) 844-6697