OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [emergency] update for EDXL DE xsd and Sample xml


EMTC

I have added to my Radiation Example and also done some addition work on
the schema.  I would appreciate everyone with an XML validation tool to
examine them both in detail.  I created them with my Microsoft Visual
Studio 2005 Beta 2 software.  I used it because the production Visual
Studio 2003 will not allow a <choice> in a <sequence> of elements.  When
I used the <group> element it validated but was obviously an artifact of
the older Microsoft software.  I am also no expert of XML schema and
would still like to provide flexibility in the EDXLDistribution schema
for include namespaces for validating <ContentObject> XML and wrapping
the contents of <namespacedXMLcontent> with encryption and signature
capability.

Please review this and let me know what your tools determine.

David E. Ellis
Information Management Architect
(505) 844-6697

-----Original Message-----
From: Michelle Raymond [mailto:michellearaymond@gmail.com] 
Sent: Thursday, August 11, 2005 11:34 PM
To: Emergency_Mgt_TC TC
Subject: [emergency] EDXL DE xsd and Sample xml and latest draft

EMTC,

I'm a bit delayed on sending the full draft due to schema validation
issues.  I think they are resolved in the files sent.

Dave did a great job putting the schema together.  I still had issues
with the <group> element followed by a <choice> in three validation
tools.  By removing the <group> as a wrapper, it 'seems' to have
resolved the issue.  I am no expert on xml schema 'model groups',
'partitions' or the like. We're likely to get (hopefully constructive)
comments on the schema format during review.

In the Specification Draft, Section 3.2: Data Dictionary, Appendix A:
Examples and Appendix B: Schema still need replacing.  I'll do that
after a sleep break.

Best Regards,

Michelle

EDXLDistribution1.xsd

<?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>
	<!--
	Currently there is not provison to allow multiple values under the
	same Value List.  Therefore the <receipentRole must be repeated three
	times, since Warning and reporting systems want CAP cintent, 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>
	</recipientRole>
	<recipientRole>
		<valueListUrn>urn:sandia:gov:sensors:reciepentRole</valueListUrn>
		<value>Hazard Prediction applications</value>
	</recipientRole>
	<recipientRole>
		<valueListUrn>urn:sandia:gov:sensors:reciepentRole</valueListUrn>
		<value>Situational Awarness applications</value>
	</recipientRole>
	
	<!--
	The elements explicitAddress and DistributionReference are not used
	in this example.  Routing of EDXL Distribution is just being designed
	and there are no good ways to show them in this example.
	-->
	
	<!--
	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>
	
	<!-- 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>
		<location>San Francisco</location>
	</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
			-->
			<keyXMLContent xmlns:cap1.0="http://www.incident.com/cap/1.0";>
				<cap1.0:category >Other</cap1.0:category>
			</keyXMLContent>
			
			<confidentiality>Unclassified</confidentiality>
			<mimeType>text/xml</mimeType>
			<namespacedXMLcontent xmlns:cap1.0="http://www.incident.com/cap/1.0";>
				<cap1.0:alert xmlns="http://www.incident.com/cap/1.0";>
					<cap1.0:identifier>Jul29_000002</cap1.0:identifier>
					<cap1.0:sender>Rad1@sandia.gov</cap1.0:sender>
					<cap1.0:sent>2005-07-29T19:11:01-04:00</cap1.0:sent>
					<cap1.0:status>Test</cap1.0:status>
					<cap1.0:msgType>Alert</cap1.0:msgType>
					<cap1.0:source>Radiation Sensor at golden gate bridge</cap1.0:source>
					<cap1.0:scope>Public</cap1.0:scope>
					<cap1.0:info>
						<cap1.0:language>En-US</cap1.0:language>
						<cap1.0:category>Other</cap1.0:category>
						<cap1.0:event>Possible Terrorism</cap1.0:event>
						<cap1.0:urgency>Immediate</cap1.0:urgency>
						<cap1.0:severity>Extreme</cap1.0:severity>
						<cap1.0:certainty>Observed</cap1.0:certainty>
						<cap1.0:audience>sensor Management</cap1.0:audience>
						<cap1.0:senderName>Rad1</cap1.0:senderName>
						<cap1.0:headline>Radiation Detection</cap1.0:headline>
						<cap1.0:description>Unknown vehicle will potential SNM has been detected
						crossing the golden gate bridge</cap1.0:description>
						<cap1.0:instruction>Please locate vehicle</cap1.0:instruction>
						<cap1.0:contact>David E. Ellis, 505-844-6697</cap1.0:contact>
						<cap1.0:area>
							<cap1.0:areaDesc>Estimated source coordinates</cap1.0:areaDesc>
							<cap1.0:circle>37.82945,-122.47997 0</cap1.0:circle>
						</cap1.0:area>
					</cap1.0:info>
				</cap1.0:alert>
			</namespacedXMLcontent>
		</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>
		<keyXMLContent xmlns:cap1.1="urn:oasis:names:tc:emergency:cap:1.1">
			<cap1.1:category >CBRNE</cap1.1:category>
		</keyXMLContent>
		<confidentiality>Unclassified</confidentiality>
		<mimeType>text/xml</mimeType>
		<namespacedXMLcontent xmlns:cap1.1="urn:oasis:names:tc:emergency:cap:1.1">
			<cap1.1:alert xmlns="urn:oasis:names:tc:emergency:cap:1.1">
				<cap1.1:identifier>Aug08_000001</cap1.1:identifier>
				<cap1.1:sender>dellis@sandia.gov</cap1.1:sender>
				<cap1.1:sent>2005-08-07T18:11:01-07:00</cap1.1:sent>
				<cap1.1:status>Test</cap1.1:status>
				<cap1.1:msgType>Alert</cap1.1:msgType>
				<cap1.1:source>Radiation Sensor at golden gate bridge</cap1.1:source>
				<cap1.1:scope>Public</cap1.1:scope>
				<cap1.1:info>
					<cap1.1:language>En-US</cap1.1:language>
					<cap1.1:category>CBRNE</cap1.1:category>
					<cap1.1:event>Possible Terrorism</cap1.1:event>
					<cap1.1:urgency>Immediate</cap1.1:urgency>
					<cap1.1:severity>Extreme</cap1.1:severity>
					<cap1.1:certainty>Observed</cap1.1:certainty>
					<cap1.1:audience>sensor Management</cap1.1:audience>
					<cap1.1:senderName>Rad1</cap1.1:senderName>
					<cap1.1:headline>Radiation Detection</cap1.1:headline>
					<cap1.1:description>Unknown vehicle will potential SNM has been detected crossing the golden gate bridge</cap1.1:description>
					<cap1.1:instruction>Please locate vehicle</cap1.1:instruction>
					<cap1.1:contact>David E. Ellis, 505-844-6697</cap1.1:contact>
					<cap1.1:area>
						<cap1.1:areaDesc>Estimated source coordinates</cap1.1:areaDesc>
						<cap1.1:circle>37.82945,-122.47997 0</cap1.1:circle>
									</cap1.1:area>
						</cap1.1:info>
				</cap1.1:alert>
		</namespacedXMLcontent>
	</contentObject>
	<!--
		Examples of Sensor Management video and image content for internet access if allowed. 
		
	<resource>
        <resourceDesc>Video clip from Sensor: CWDET-01, Site: Tiedown, having a Detection class of CWDET.
		Video specs:  Length: 23   Type:  mpeg   Channel Band: Channel A</resourceDesc>
        <uri>http://sentry/videoClip1</uri>
	</resource>
	<resource>
		<resourceDesc>Photo image from Sensor: CWDET-01, Site: Tiedown, having a Detection class of CWDET.
		Photo specs:  Type:  jpeg   Channel Band: Channel B</resourceDesc>
		<uri>http://sentry/photoCapture</uri>
		
	This is the Internet Viewable image of the Suspect vehicle with SNM. 
	-->
	<contentObject>
		<contentKeyword>
			<valueListUrn>"urn:sandia:gov:sensor:detection.event.id"</valueListUrn>
			<value>10.2.2.1:2005-08-07T18:00:00Z</value>
		</contentKeyword>
		<keyXMLContent xmlns:cap1.1="urn:oasis:names:tc:emergency:cap:1.1">
			<cap1.1:category >CBRNE</cap1.1:category>
		</keyXMLContent>
		<confidentiality>Unclassified</confidentiality>
		<description>Photo image from Sensor: RADDET-01, Site: Golden Gate Bridge, having a Detection class of SNM</description>
		<mimeType>image/jpeg</mimeType>
		<uri>http://sentry/photoCapture/10.2.2.1:2005-08-07T18:00:00Z</uri> 
	</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>
		<contentKeyword>
			<valueListUrn>"urn:sandia:gov:sensor:detection.event.id"</valueListUrn>
			<value>10.2.2.1:2005-08-07T18:00:00Z</value>
		</contentKeyword>
		<keyXMLContent xmlns:cap1.1="urn:oasis:names:tc:emergency:cap:1.1">
			<cap1.1:category >CBRNE</cap1.1:category>
		</keyXMLContent>
		<confidentiality>Unclassified</confidentiality>
		<description>Photo image from Sensor: RADDET-01, Site: Golden Gate Bridge, having a Detection class of SNM</description>
		<mimeType>image/jpeg</mimeType>
		<derefUri>Base 64 encodeing of vehicle image</derefUri>
	</contentObject>
		
	<!--
	The following content object contains the readings from a UNWD radiation Portal
	The Detection ID is beeing 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.
	-->
	<contentObject>
		<contentKeyword>
			<valueListUrn>"urn:sandia:gov:sensor:detection.event.id"</valueListUrn>
			<value>10.2.2.1:2005-08-07T18:00:00Z</value>
		</contentKeyword>
		<originatorRole>
			<valueListUrn>urn:sandia:gov:originator.role</valueListUrn>
			<value>Portal Radiation Detector</value>
		</originatorRole>
		<consumerRole>
			<valueListUrn>"urn:sandia:gov:sensor:consumer:role"</valueListUrn>
			<value>Sensor Managment Systems</value>
		</consumerRole>
		<confidentiality>Unclassified</confidentiality>
		<mimeType>text/xml</mimeType>
		<namespacedXMLcontent xmlns:UNWD="urn:sandia:gov:sensors:unwd:1.0">
			<UNWD:SensorEvent rev="1.00" xmlns="urn:sandia:gov:sensors:unwd:1.0">
				<UNWD:SensorData id="10.2.2.1" timestamp="2005-08-07T18:00:00Z" oemid="Thermo Electron" model="RAD_RISIV" type="detect" sensorclass="radiation">
					<UNWD:Result valuetype="PeakGamma" value="520" units="cps"></UNWD:Result>
					<UNWD:Result valuetype="PeakNeutrons" value="150" units="cps"></UNWD:Result>
					<UNWD:Result valuetype="SNMProbability" value="0.4"></UNWD:Result>
					<UNWD:Result valuetype="TLF" value="1.62" units="seconds"></UNWD:Result>
					<UNWD:Result valuetype="TLB" value="298" units="seconds"></UNWD:Result>
					<UNWD:Result valuetype="ChiSquare" value="0.9"></UNWD:Result>
					<UNWD:Result texttype="IsotopeName" text="Tc99m" valuetype="IDProbability" value="0.9"></UNWD:Result>
					<UNWD:Result texttype="IsotopeName" text="Pu239" valuetype="IDProbability" value="0.5"></UNWD:Result>
					<UNWD:Media id="Golden Gate Lane 1 Camera" mimetype="image/jpeg">
						<!-- The location of servername has a private IP address 10.2.2.1
						It is not available for direct access form the internet -->
						<UNWD:MediaItem uri="http://servername/imagepath/image1.jpg";></UNWD:MediaItem>
					</UNWD:Media>
				</UNWD:SensorData>
			</UNWD:SensorEvent>
		</namespacedXMLcontent>
	</contentObject>
</EDXLDistribution>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]