pdfnano7
nano7 时间:2021-01-17 阅读:()
EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page1of42EmergencyDataExchangeLanguage(EDXL)DistributionElement,v.
1.
0OASISStandardEDXL-DEv1.
0,1May2006DocumentIdentifier:EDXL-DE-V1.
0OASISIdentifier:{EMTC}-{EDXL-DE}-{1.
0}(HTML)(Word)(PDF)Location:ThisVersion:http://docs.
oasis-open.
org/emergency/EDXL-DE/V1.
0TechnicalCommittee:OASISEmergencyManagementTCChair(s):ElysaJones,WarningSystems,Inc.
-Editor(s):MichelleRaymond,IndividualSylviaWebb,IndividualPattiIlesAymond,IEM,Inc.
-Subject/Keywords:distributionelement,dissemination,routing,payload,alert,resourcemessage,emergency,informationsharing,dataexchange,emergencyresponse,emergencymanagement,geospatial,political,targetarea,messagedelivery,messagesender,messagerecipient,distributionstatus,distributiontype,senderrole,recipientrole,responsetype,eventcause,confidentiality,circle,polygon,location,contentobject,consumerrole,notification,XMLmessage,distributiontype,geography,incident,senderidentification,senderid,recipientidentification,recipientid,inter-agency,emergencyinformation,functionalrole,recipientaddress,hazard,distributionstatus,distributiontype,eventtype,eventetiology,messageprocessor,eventstage,resourcecodeandresponsetypeRelatedWork:Thisspecificationisrelatedto:CAP1.
1-http://www.
oasis-open.
org/committees/emergencyTheCommonAlertingProtocol(CAP)providesanopen,non-proprietarydigitalmessageformatforalltypesofalertsandnotifications.
CAPmessagesarerecommendedasoneofthestandardizedformsforXMLbasedmessagecontent,tobedistributedbythisDistributionElement.
EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page2of42Abstract:ThisDistributionElementspecificationdescribesastandardmessagedistributionframeworkfordatasharingamongemergencyinformationsystemsusingtheXML-basedEmergencyDataExchangeLanguage(EDXL).
Thisformatmaybeusedoveranydatatransmissionsystem,includingbutnotlimitedtotheSOAPHTTPbinding.
Status:ThisdocumentwaslastrevisedorapprovedbytheEmergencyManagementTechnicalCommitteeontheabovedate.
Thelevelofapprovalisalsolistedabove.
Checkthecurrentlocationnotedaboveforpossiblelaterrevisionsofthisdocument.
Thisdocumentisupdatedperiodicallyonnoparticularschedule.
TechnicalCommitteemembersshouldsendcommentsonthisspecificationtotheTechnicalCommittee'semaillist.
OthersshouldsendcommentstotheTechnicalCommitteebyusingthe"SendAComment"buttonontheTechnicalCommittee'swebpageatwww.
oasis-open.
org/committees/emergency.
Forinformationonwhetheranypatentshavebeendisclosedthatmaybeessentialtoimplementingthisspecification,andanyoffersofpatentlicensingterms,pleaserefertotheIntellectualPropertyRightssectionoftheTechnicalCommitteewebpageatwww.
oasis-open.
org/committees/emergency/ipr.
php.
NoticesOASIStakesnopositionregardingthevalidityorscopeofanyintellectualpropertyorotherrightsthatmightbeclaimedtopertaintotheimplementationoruseofthetechnologydescribedinthisdocumentortheextenttowhichanylicenseundersuchrightsmightormightnotbeavailable;neitherdoesitrepresentthatithasmadeanyefforttoidentifyanysuchrights.
InformationonOASISprocedureswithrespecttorightsinOASISspecificationscanbefoundattheOASISwebsite.
Copiesofclaimsofrightsmadeavailableforpublicationandanyassurancesoflicensestobemadeavailable,ortheresultofanattemptmadetoobtainagenerallicenseorpermissionfortheuseofsuchproprietaryrightsbyimplementersorusersofthisspecification,canbeobtainedfromtheOASISPresident.
OASISinvitesanyinterestedpartytobringtoitsattentionanycopyrights,patentsorpatentapplications,orotherproprietaryrightswhichmaycovertechnologythatmayberequiredtoimplementthisspecification.
PleaseaddresstheinformationtotheOASISPresident.
CopyrightOASISOpen2006.
AllRightsReserved.
Thisdocumentandtranslationsofitmaybecopiedandfurnishedtoothers,andderivativeworksthatcommentonorotherwiseexplainitorassistinitsimplementationmaybeprepared,copied,publishedanddistributed,inwholeorinpart,withoutrestrictionofanykind,providedthattheabovecopyrightnoticeandthisparagraphareincludedonallsuchcopiesandderivativeworks.
However,thisdocumentitselfdoesnotbemodifiedinanyway,suchasbyremovingthecopyrightnoticeorreferencestoOASIS,exceptasneededforthepurposeofdevelopingOASISspecifications,inwhichcasetheproceduresforcopyrightsdefinedintheOASISIntellectualPropertyRightsdocumentmustbefollowed,orasrequiredtotranslateitintolanguagesotherthanEnglish.
ThelimitedpermissionsgrantedaboveareperpetualandwillnotberevokedbyOASISoritssuccessorsorassigns.
EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page3of42Thisdocumentandtheinformationcontainedhereinisprovidedonan"ASIS"basisandOASISDISCLAIMSALLWARRANTIES,EXPRESSORIMPLIED,INCLUDINGBUTNOTLIMITEDTOANYWARRANTYTHATTHEUSEOFTHEINFORMATIONHEREINWILLNOTINFRINGEANYRIGHTSORANYIMPLIEDWARRANTIESOFMERCHANTABILITYORFITNESSFORAPARTICULARPURPOSE.
EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page4of42TableofContents1.
INTRODUCTION51.
1PURPOSE51.
2HISTORY51.
3STRUCTUREOFTHEEDXLDISTRIBUTIONELEMENT.
61.
3.
161.
3.
261.
3.
361.
4APPLICATIONSOFTHEEDXLDISTRIBUTIONELEMENT61.
5TERMINOLOGY.
61.
6NORMATIVEREFERENCES.
71.
7NON-NORMATIVEREFERENCES.
72.
DESIGNPRINCIPLESANDCONCEPTS(NON-NORMATIVE)82.
1DESIGNPHILOSOPHY82.
2REQUIREMENTSFORDESIGN82.
3EXAMPLEUSAGESCENARIOS92.
3.
1DistributionofEmergencyMessage/sorAlertsBasedonGeographicDeliveryAreaandIncidentType.
92.
3.
2EncapsulationandDistributionofOneorMoreEmergencyMessagesorAlertsorNotifications92.
3.
3DistributionofResourceMessagesorReports.
92.
3.
4DistributionofWell-FormedXMLMessages.
93.
EDXLDISTRIBUTIONELEMENTSTRUCTURE(NORMATIVE)103.
1DOCUMENTOBJECTMODEL103.
2DATADICTIONARY.
113.
2.
1EDXLDistributionElementandSub-elements.
113.
2.
2targetAreaElementandSub-elements183.
2.
3contentObjectElementandSub-elements213.
2.
4nonXMLContentElementandSub-elements.
263.
2.
5xmlContentElementandSub-elements.
283.
2.
6ListandAssociatedValue(s)303.
2.
7ExplicitAddressing31APPENDIXA.
XMLSCHEMAFORTHEEDXLDISTRIBUTIONELEMENT.
32APPENDIXB.
EDXL-DEEXAMPLES.
35B.
1EDXL-DEWITHCAPPAYLOAD.
35B.
2EDXL-DEWITHMULTIPLEENCRYPTEDPAYLOADS36APPENDIXC.
ACKNOWLEDGMENTS.
41C.
1OASISEMERGENCYMANAGEMENTTECHNICALCOMMITTEE:41APPENDIXD.
REVISIONHISTORY.
42EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page5of421.
Introduction11.
1Purpose2TheprimarypurposeoftheDistributionElementistofacilitatetheroutingofanyproperlyformattedXML3emergencymessagetorecipients.
TheDistributionElementmaybethoughtofasa"container".
It4providestheinformationtoroute"payload"messagesets(suchasAlertsorResourceMessages),by5includingkeyroutinginformationsuchasdistributiontype,geography,incident,andsender/recipientIDs.
61.
2History7TheDisasterManagementeGovInitiativeoftheDepartmentofHomelandSecurity(DHS)determinedin82004tolaunchaprojecttodevelopinteragencyemergencydatacommunicationsstandards.
Itcalled9togetheragroupofnationalemergencyresponsepractitionerleadersandsoughttheirguidanceon10requirementsforsuchstandards.
InJune,2004thefirstsuchmeetingidentifiedtheneedforacommon11distributionelementforallemergencymessages.
SubsequentmeetingsofaStandardsWorkingGroup12developeddetailedrequirementsandadraftspecificationforsuchadistributionelement(DE).
13DuringthesameperiodtheDMInitiativewasformingapartnershipwithindustrymembersofthe14EmergencyInteroperabilityConsortium(EIC)tocooperateinthedevelopmentofemergencystandards.
15EIChadbeenaleadingsponsoroftheCommonAlertingProtocol(CAP).
Bothorganizationsdesiredto16developanexpandedfamilyofdataformatsforexchangingoperationalinformationbeyondwarning.
17EICmembersparticipatedinthedevelopmentoftheDE,andinthebroaderdesignofthedesignofa18processforthedevelopmentofadditionalstandards.
ThiswasnamedEmergencyDataExchange19Language(EDXL).
20ThegoaloftheEDXLprojectistofacilitateemergencyinformationsharinganddataexchangeacrossthe21local,state,tribal,nationalandnon-governmentalorganizationsofdifferentprofessionsthatprovide22emergencyresponseandmanagementservices.
EDXLwillaccomplishthisgoalbyfocusingonthe23standardizationofspecificmessages(messaginginterfaces)tofacilitateemergencycommunicationand24coordinationparticularlywhenmorethanoneprofessionisinvolved.
Itisnotjustan"emergency25management"domainexercise.
26Itisanationaleffortincludingadiverseandrepresentativegroupoflocal,stateandfederalemergency27responseorganizationsandprofessionals,followingamulti-stepprocess.
Justasadata-focusedeffort28targetsshareddataelements,theEDXLprocesslooksforsharedmessageneeds,whicharecommon29acrossabroadnumberoforganizations.
Theobjectiveistorapidlydeliverimplementablestandard30messages,inanincrementalfashion,directlytoemergencyresponseagenciesinthetrenches,providing31seamlesscommunicationandcoordinationsupportingeachparticularprocess.
Theeffortfirstaddresses32themosturgentneedsandproceedstosubsequentmessagesetsinaprioritizedfashion.
Thegoalisto33incrementallydevelopanddeliverstandards.
34EDXLisintendedasasuiteofemergencydatamessagetypesincludingresourcequeriesandrequests,35situationstatus,messageroutinginstructionsandthelike,neededinthecontextofcross-disciplinary,36cross-jurisdictionalcommunicationsrelatedtoemergencyresponse.
37TheprioritiesandrequirementsarecreatedbytheDMEDXLStandardsWorkingGroup(SWG)whichisa38formalizedgroupofemergencyresponsepractitioners,technicalexperts,andindustry.
39EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page6of42ThedraftDEspecificationwastrialedbyanumberofEICmembersstartinginOctober,2004.
In1November,2004,EICformallysubmittedthedrafttotheOASISEmergencyManagementTechnical2Committeeforstandardization.
31.
3StructureoftheEDXLDistributionElement4TheEDXLDistributionElement(DE)comprisesanelementasdescribedhereafter,5optionalelementsdescribinggeospatialorpoliticaltargetareaformessagedelivery,anda6setofelementseachcontainingspecificinformationregardingaparticularitemof7content.
TheincludedcontentmaybeanyXMLorothercontenttypeoraURItoaccessthecontent.
8Theblockmaybeusedwithoutcontenttoformthebodyofaroutingqueryto,or9responsefrom,adirectoryservice.
101.
3.
111Theelementassertstheoriginator'sintentastothedisseminationofthatparticular12messageorsetofmessages.
13Notethatuseoftheelementdoesnotguaranteethatallnetworklinksandnodeswill14implementtheasserteddisseminationpolicyorthatunintendeddisclosurewillnotoccur.
Wheresensitive15informationistransmittedoverdistrustednetworks,itshouldbeencryptedinaccordancewiththeWeb16ServicesSecurity(WSS)standardhttp://docs.
oasis-open.
org/wss/2004/01/oasis-200401-wss-soap-17message-security-1.
0.
pdfwithanyupdatesanderratapublishedbytheOASISWebServicesSecurity18TechnicalCommitteehttp://www.
oasis-open.
org/committees/tc_home.
phpwg_abbrev=wss,orsome19othersuitableencryptionscheme.
201.
3.
221Theisacontainerelementforthegeospatialorpoliticalareatargetingoftherecipientofthe22messagecontent.
Itcontainsdatanecessarytotheoriginator'sintent,basedonlocationtargeting,asto23thedisseminationofthatparticularmessageorsetofmessages.
241.
3.
325Theisacontainerelementforspecificmessages.
TheelementMUST26eithercontainancontentcontaineroracontentcontainer.
Additional27elements(metadata)usedforspecificdistributionofthepayloadorhintsforprocessing28thepayloadarealsopresentinthecontainerelement.
291.
4ApplicationsoftheEDXLDistributionElement30TheprimaryuseoftheEDXLDistributionElementistoidentifyandprovideinformationtoenablethe31routingofencapsulatedpayloads,calledContentObjects.
Itisusedtoprovideacommonmechanismto32encapsulatecontentinformation.
331.
5Terminology34Thekeywords"MUST","MUSTNOT","REQUIRED","SHALL","SHALLNOT","SHOULD","SHOULD35NOT","RECOMMENDED","MAY",and"OPTIONAL"aretobeinterpretedasdescribedinKeywordsfor36useinRFCstoIndicateRequirementLevels[RFC2119].
37EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page7of42Inaddition,withinthisSpecification,thekeyword"CONDITIONAL"shouldbeinterpretedaspotentially1"REQUIRED"or"OPTIONAL"dependingonthesurroundingcontext.
Thetermpayloadreferstosome2bodyofinformationcontainedinthedistributionelement.
31.
6NormativeReferences4[RFC2046]5N.
Freed,MultipurposeInternetMailExtensions(MIME)PartTwo:MediaTypes,6http://www.
ietf.
org/rfc/rfc2046.
txt,IETFRFC2046,November1996.
7[RFC2119]8S.
Bradner,KeywordsforuseinRFCstoIndicateRequirementLevels,9http://www.
ietf.
org/rfc/rfc2119.
txt,IETFRFC2119,March1997.
10[RFC3066]11H.
Alvestrand,TagsfortheIdentificationofLanguages,12http://www.
ietf.
org/rfc/rfc3066.
txt,IETFRFC3066,January2001.
13[WGS84]14NationalGeospatialIntelligenceAgency,DepartmentofDefenseWorldGeodetic15System1984,http://earth-info.
nga.
mil/GandG/tr8350_2.
html,NGATechnicalReport16TR8350.
2,January2000.
17[XML1.
0]18T.
Bray,ExtensibleMarkupLanguage(XML)1.
0(ThirdEdition),19http://www.
w3.
org/TR/REC-xml/,W3CREC-XML-20040204,February2004.
20[namespaces]21T.
Bray,NamespacesinXML,http://www.
w3.
org/TR/REC-xml-names/,W3CREC-22xml-names-19990114,January1999.
23[dateTime]24N.
Freed,XMLSchemaPart2:DatatypesSecondEdition,25http://www.
w3.
org/TR/xmlschema-2/#dateTime,W3CREC-xmlschema-2,October262004.
271.
7Non-NormativeReferences28EDXLGeneralFunctionalRequirements29EDXLGeneralFunctionalRequirements,http://www.
oasis-30open.
org/committees/document.
phpdocument_id=10031&wg_abbrev=emergency,31November2004.
32EDXLDistributionElementImplementer'sGuide33EDXLDistributionElementImplementer'sGuide,http://www.
oasis-34open.
org/committees/document.
phpdocument_id=14120&wg_abbrev=emergency,35August2005.
36EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page8of422.
DesignPrinciplesandConcepts(non-normative)12.
1DesignPhilosophy2BelowaresomeoftheguidingprinciplesoftheDistributionElement:3ProvideanOpenContainerModeltoenabledisseminationofoneormoreemergencymessages4Provideflexiblemechanismstoinformmessageroutingand/orprocessingdecisions5Enabledisseminationofmessagesbasedongeographicdeliveryarea6Useandre-useofdatacontentandmodelsdevelopedbyotherinitiatives7Businessprocess-drivenspecificmessagingneedsacrossemergencyprofessions8Supportingeverydayeventsandincidentpreparedness,aswellasdisasters9Facilitateemergencyinformationsharinganddataexchangeacrossthelocal,state,tribal,10nationalandnon-governmentalorganizationsofdifferentprofessionsthatprovideemergency11responseandmanagementservices12Multi-useformat-Onemessageschemasupportsmultiplemessagetypes(e.
g.
,alert/update/13cancellations/acknowledgments/errormessages)invariousapplications(actual/exercise/test14/systemmessage.
)152.
2RequirementsforDesign16TheDistributionElementspecificationshould:171.
DefineasinglecompoundXMLstructure(oranequivalentsinglestructureiftranscodedinto18anotherformat)includingtherequiredandoptionalelementsdefinedbelow.
192.
Specifyadesiredgeographicdeliveryarea,expressedingeospatialcoordinatesorusing20political/administrativecodes213.
Allowtheabilitytoencapsulateapayloadorsetofpayloads224.
Takeamodularapproachtotheenumerationsofelementvalueswhichmayevolveovertime,23e.
g.
byreferringtoaseparateschemaforthoseenumerations.
245.
Specifyuniquedistributionandsenderidentifiers256.
Specifythedateandtimethedistributionwassent267.
Specifytheactionabilityofthedistributionmessage(e.
g.
,real-world,test,exercise)278.
Specifythefunctionaltypeofthedistributionmessage(e.
g.
,report,request,update,cancellation,28etc.
)299.
Specifythatthefollowingelementsmaybepresentinavalidpayload:30a.
Aspecificationoftheformatofthedistributionmessage(e.
g.
,theURIofanXMLSchema31forthemessage)32b.
Thefunctionalroleand/ortypeofthesenderofthedistributionmessage33c.
Oneormorefunctionalroleand/ortypeofdesiredrecipientsofthedistributionmessage34d.
Areferencetooneormorepreviousdistributionmessages35e.
Oneormoretypesofresponseactivityinvolved36f.
Areferencetothetypeofincident37g.
Oneormorecharacterizationoftheetiologyofthesubjecteventorincident(e.
g.
,38terrorism,natural,underinvestigation,etc.
)39h.
Theincidentnameorotheridentifierofoneormoreeventorincident40i.
Areferencetooneormoreresponsetypes.
41j.
Oneormorespecificrecipientaddresses(asaURI)42k.
Specifyanassertionoftheconfidentialitylevelofthecombinedpayloads.
4310.
Inaddition,theContentObjectelementcontainedwithintheDistributionElementSHOULD:44a.
AllowtheencapsulationofoneormorepayloadsineachoftheContentObjectelements.
45b.
Specifythefunctionalroleand/ortypeofthesenderofeachpayload46c.
Specifyoneormorefunctionalrolesand/ortypesofdesiredrecipientsofeachpayload47EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page9of42d.
Specifyanassertionoftheconfidentialitylevelofeachpayload.
111.
Provideorrefertospecificlists(enumerations)ofvaluesandtheirdefinitionsfor:2a.
Typesofincidents3b.
Typesofhazardsand/orevents4c.
Typesofagencies5d.
Typesofresponseactivity6e.
Thefunctionalroleand/ortypeofthesender7f.
Thefunctionalrolesand/ortypesofdesiredrecipients8g.
Theincidentnameorotheridentifierofoneormoreeventorincident.
92.
3ExampleUsageScenarios10Note:ThefollowingexamplesofusescenarioswereusedasabasisfordesignandreviewoftheEDXL11DistributionElementMessageformat.
Thesescenariosarenon-normativeandnotintendedtobe12exhaustiveortoreflectactualpractices.
132.
3.
1DistributionofEmergencyMessage/sorAlertsBasedonGeographic14DeliveryAreaandIncidentType15TheterroralertlevelhasbeenraisedtoRED.
Credibleintelligenceindicatesthatterroristgroupsinthe16Mid-Atlanticregionareseekingtoconductanattackinthenext48hours.
TheDepartmentofHomeland17Securitysendsanemergencyalertmessage,andusingtheDistributionElement,distributesittoall18emergencyagenciesinthespecifiedarea.
192.
3.
2EncapsulationandDistributionofOneorMoreEmergencyMessagesor20AlertsorNotifications21ARadiologicalsensortriggeredataprominentTunneltollbooth.
Radiationalarmlevelsindicates22possibledirtybomb.
Authoritiesdecidetosendmultiplemessagestoanumberofjurisdictions.
Theysend23anEDXLDistributionElementwithtwoencapsulatedCAPmessages.
Thefirstonenotifiesthearea24wherethesensorhasbeentriggered.
Thesecondoneisanalerttoemergencyresponseagenciesthat25thestateEmergencyOperationCenter(EOC)hasbeenactivated,andrequeststheagenciestobeon26alert.
272.
3.
3DistributionofResourceMessagesorReports28TheLocalEOChasaneedforadditionalresource/support,butisunsurewhatspecificallytorequest.
A29free-formrequestforinformationandresourceavailabilityisprepared,andissenttothestateEOCand30otherorganizations(persontoperson)usingtheDistributionElement.
TheLocalEOCreceivesan31acknowledgmentmessagefromtheStateEOC,aswellasarequestforInformationonadditionaldetails32oftherequestedresource.
BothofthesemessagesarecontainedwithinasingleDistributionElement.
332.
3.
4DistributionofWell-FormedXMLMessages34Ahugecrash,involvingacarandaHAZMATtruck,occursatabusyjunctiononaninter-statefreeway.
35SeparateautomaticnotificationsofboththecarcrashandtheHAZMATcarrieraresentusingthe36VehicularEmergencyDataSet(VEDS),containedintheDistributionElement.
TheTransportation37ManagementCenter(TMC)sharesinformation(relatedtotheaboveincident)withtheadjacentTMC,38usingtheIEEE1512IncidentManagementMessageSet.
Thesesetofmessagesareexchangedusing39theEDXLDistributionElement.
40EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page10of423.
EDXLDistributionElementStructure(normative)13.
1DocumentObjectModel2Boldindicatesrequiredelement.
3Italicsindicatesoneormoreoptionalunspecifiedelements4#indicatesconditionalrequirement5*indicatesmultipleinstancesallowed6EDXLDistributiondistributionIDsenderIDdateTimeSentdistributionStatusdistributionTypecombinedConfidentialitylanguagesenderRole*recipientRole*keyword*distributionReference*#explicitAddress*targetAreacircle*polygon*country*subdivision*locCodeUN*contentObjectcontentDescriptioncontentKeyword*incidentIDincidentDescriptionoriginatorRole*consumerRole*confidentialityother*nonXMLContentmimeTypesizedigesturicontentDataxmlContentkeyXMLContentembeddedXMLContent0.
.
*OR10.
.
*7EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page11of423.
2DataDictionary1Note:UnlessexplicitlyconstrainedwithinthisDataDictionary,EDXL-DEelementsMAYhavenullvalues.
2ImplementersMUSTcheckforthisconditionwhereveritmightaffectapplicationperformance.
33.
2.
1EDXLDistributionElementandSub-elements4TheDistributionMessageelement,isthecontainerelementforalldatanecessaryto5theoriginator'sintentastothedisseminationofthecontainedmessageorsetofmessages.
6ElementEDXLDistributionTypeXMLStructureUsageREQUIRED,MUSTbeusedonceandonlyonce,toplevelcontainerDefinitionThecontainerofalloftheelementsrelatedtothedistributionofthecontentmessages.
Comments1.
Theelementmayincludeoneormoreandblocks.
2.
Useoftheelementdoesnotguaranteethatallnetworklinksandnodeswillimplementtheasserteddisseminationpolicyorthatunintendeddisclosurewillnotoccur.
Wheresensitiveinformationistransmittedoveruntrustednetworks,itshouldbeencryptedinaccordancewiththeWebServicesSecurity(WSS)standard()withanyupdatesanderratapublishedbytheOASISWebServicesSecurityTechnicalCommittee(),orsomeothersuitableencryptionscheme.
Sub-elementsdistributionIDsenderIDdateTimeSentdistributionStatusdistributionTypecombindedConfidentialitylanguagesenderRolerecipientRolekeyworddistributionReferenceexplicitAddresstargetAreacontentObjectUsedIntoplevelelement7EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page12of421ElementdistributionIDTypexsd:stringUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionTheuniqueidentifierofthisdistributionmessage.
Comments1.
Uniquenessisassignedbythesendertobeuniqueforthatsender.
2.
TheidentifierMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution2ElementsenderIDTypexsd:stringUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionTheuniqueidentifierofthesender.
Comments1.
Uniquelyidentifieshumanparties,systems,services,ordevicesthatareallpotentialsendersofthedistributionmessage.
2.
Intheformactor@domain-name.
3.
Uniquenessofthedomain-nameisguaranteedthroughuseoftheInternetDomainNameSystem,anduniquenessoftheactornameenforcedbythedomainowner.
4.
TheidentifierMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:dispatcher@example.
gov,0006.
0e39.
ad80@example.
comUsedInEDXLDistribution3ElementdateTimeSentTypexsd:dateTimeUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionThedateandtimethedistributionmessagewassent.
Comments1.
TheDateTimecombinationmustincludetheoffsettimefortimezone.
2.
MustbeintheW3CformatfortheXML[dateTime]datatype.
Example:2004-08-01T16:49:00-07:00UsedInEDXLDistribution4EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page13of421ElementdistributionStatusTypexsd:stringwithrestrictionsUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionTheactionabilityofthemessage.
Comments1.
Valuemustbeoneof:a.
Actual-"Real-world"informationforactionb.
Exercise-Simulatedinformationforexerciseparticipantsc.
System-Messagesregardingorsupportingnetworkfunctionsd.
Test-Discardablemessagesfortechnicaltestingonly.
2.
ThestatusMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution2ElementdistributionTypeTypexsd:stringwithrestrictionsUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionThefunctionofthemessage.
Comments1.
Valuemustbeoneof:a.
Report-Newinformationregardinganincidentoractivityb.
Update-Updatedinformationsupersedingapreviousmessagec.
Cancel-Acancellationorrevocationofapreviousmessaged.
Request-Arequestforresources,informationoractione.
Response-Aresponsetoapreviousrequestf.
Dispatch-Acommitmentofresourcesorassistanceg.
Ack-Acknowledgmentofreceiptofanearliermessageh.
Error-Rejectionofanearliermessage(fortechnicalreasons)i.
SensorConfiguration-ThesemessagesareforreportingconfigurationduringpoweruporafterInstallationorMaintenance.
j.
SensorControl-Thesearemessagesusedtocontrolsensors/sensorconcentratorcomponentsbehavior.
k.
SensorStatus-Theseareconcisemessageswhichreportsensors/sensorconcentratorcomponentstatusorstateofhealth.
l.
SensorDetection-Thesearehighprioritymessageswhichreportsensordetections.
2.
Thedistributiontypeappliestothefunctionofthecontentobjectsasaset.
Thosecaseswherepayloadshavedifferentdistributiontypesshouldbeclusteredindifferentdistributionelements.
3.
ThetypeMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page14of42ElementcombindedConfidentialityTypexsd:stringUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionConfidentialityofthecombineddistributionmessage'scontent.
Comments1.
Theindicatestheconfidentialityofthecombinedsub-elements.
Generallythecombinedconfidentialityisthemostrestrictiveoftheelementsinthecontainerelement,butitcanbemorerestrictivethananyoftheindividualelements.
2.
TheelementMUSTbepresentifaelementispresentinanyoftheelements.
3.
Applicationspecificmechanismswillberequiredtodeterminetheminimumconfidentialitylevelincaseswheredifferentconfidentialityschemesareusedinthe.
4.
Defaultvalue"UNCLASSIFIEDANDNOTSENSITIVE"5.
TheconfidentialityMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution1ElementlanguageTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionTheprimarylanguage(butnotnecessarilyexclusive)usedinthepayloads.
Comments1.
ValidlanguagevaluesaresuppliedintheISOstandard[RFC3066].
2.
ThelanguageMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:FR,ENUsedInEDXLDistribution2EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page15of421ElementsenderRoleTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThefunctionalroleofthesender,asitmaydeterminemessageroutingdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Sub-elementsvalueListUrnvalueUsedInEDXLDistribution2EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page16of421ElementrecipientRoleTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThefunctionalroleoftherecipient,asitmaydeterminemessageroutingdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Sub-elementsvalueListUrnvalueUsedInEDXLDistribution2EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page17of421ElementkeywordTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThetopicrelatedtothedistributionmessage,asitmaydeterminemessageroutingdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
4.
Examplesofthingsmightbeusedtodescribeincludeeventtype,eventetiology,incidentIDandresponsetype.
Sub-elementsvalueListUrnvalueUsedInEDXLDistribution2ElementdistributionReferenceTypexsd:stringUsageCONDITIONAL,MAYusemultipleDefinitionAreferencetoapreviousdistributionmessage.
Comments1.
Theandandofthereferencedpreviousmessage,concatenatedwithacommadelimiter.
2.
Thiselementshouldappearatleastonceinanymessagewhichupdates,cancelsorotherwisereferstoanothermessage.
3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Example:msgID0074,actor@domain-name,2004-08-01T16:49:00-07:00UsedInEDXLDistribution3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page18of421ElementexplicitAddressTypeXMLStructureUsageOPTIONAL,MAYusemultipleDefinitionTheidentifierofanexplicitrecipient.
Comments1.
Identifieshumanparties,systems,services,ordevicesthatareallpotentialrecipientsofthedistributionmessage.
2.
Theexplicitaddressofarecipientintheform:explicitAddressSchemeexplicitAddressValuewherethecontentofisthedistributionaddressingschemeused,andthecontentofisastringdenotingtheaddresseesvalue.
3.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
4.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Sub-elementsexplicitAddressSchemeexplicitAddressValueUsedInEDXLDistribution3.
2.
2targetAreaElementandSub-elements2Theisacontainerelementforthegeospatialorpoliticalareatargetingofthemessage3content.
Itindicatestheoriginator'sintentbasedonlocationtargetingastothedisseminationofthat4particularmessageorsetofmessages.
5GeospatialNote:6Valuesforlatitudeandlongitudeshallbeexpressedasdecimalfractionsofdegrees.
Whole7degreesoflatitudeshallberepresentedbyadecimalnumberrangingfrom0through90.
Whole8degreesoflongitudeshallberepresentedbyadecimalnumberrangingfrom0through180.
9Whenadecimalfractionofadegreeisspecified,itshallbeseparatedfromthewholenumberof10degreesbyadecimalpoint(theperiodcharacter,".
").
Decimalfractionsofadegreeshouldbe11expressedtotheprecisionavailable,withtrailingzeroesbeingusedasplaceholdersifrequired.
12Adecimalpointisoptionalwheretheprecisionislessthanonedegree.
13Someeffortshouldbemadetopreservetheapparentprecisionwhenconvertingfrom14anotherdatumorrepresentation,forexample41degrees13minutesshouldberepresentedas1541.
22andnot41.
21666,while4113'11"mayberepresentedas41.
2197.
16LatitudesnorthoftheequatorMAYbespecifiedbyaplussign(+),orbytheabsenceofaminus17sign(-),precedingthedesignatingdegrees.
LatitudessouthoftheEquatorMUSTbedesignated18byaminussign(-)precedingthedigitsdesignatingdegrees.
LatitudesontheEquatorMUSTbe19designatedbyalatitudevalueof0.
20EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page19of42Longitudeseastoftheprimemeridianshallbespecifiedbyaplussign(+),orbytheabsenceofa1minussign(-),precedingthedesignatingdegrees.
LongitudeswestoftheprimemeridianMUST2bedesignatedbyaminussign(-)precedingthedigitsdesignatingdegrees.
Longitudesonthe3primemeridianMUSTbedesignatedbyalongitudevalueof0.
Apointonthe180thmeridian4shallbetakenas180degreesWest,andshallincludeaminussign.
5ElementtargetAreaTypeXMLStructureUsageOPTIONAL,MAYusemultipleDefinitionThecontainerelementforlocationinformation.
Comments1.
Multipleblocksmayappearinasingleelement,inwhichcasethetargetareaforthecurrentmessageistheunionofallareasdescribedinthevariousstructures.
Sub-elementscirclepolygoncountrysubdivisionlocCodeUNUsedInEDXLDistribution6ElementcircleTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionAnenclosedgeographicareawithinagivenradiusaroundageographicpoint.
Comments1.
Representedintheform"latitude,longitude,radius".
(SeeGeospatialNoteabove)2.
Thecentralpointisrepresentedbylat-longvaluesconformingtotheWGS84coordinatereferencesystem.
[WGS84]3.
Theradiusvalueisexpressedinkilometers.
4.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Example:38.
26295,-122.
0745415UsedIntargetArea7EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page20of421ElementpolygonTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionAnenclosedgeographicareawithinasimpleclosedpolygondefinedbyanorderedsetofvertices.
Comments1.
Representedbyaspace-delimitedseriesoflatitude,longitudepairs,withthelastpairidenticaltothefirst.
(SeeGeospatialNoteabove)2.
Thelat-longvaluesconformtotheWGS84coordinatereferencesystem.
[WGS84]3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Example:42,-124.
210242,-120.
139,-12035.
0,-114.
632834.
35,-120.
441838.
9383,-123.
81742,-124.
2102UsedIntargetArea2ElementcountryTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionThecodeofthecountry.
Comments1.
Thetwo-characterISO3166-1CountryCodeforthecountryconcerned.
2.
Morespecifictargetlocationinformationcanbedefinedintheelements.
3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedIntargetArea3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page21of421ElementsubdivisionTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionTheISO3166-2designatorfortheadministrativesubdivisionconcerned.
Comments1.
Thefirsttwocharacters,beforethehyphen,arethetwocharacterISO3166-1CountryCodeforthecountrywithinwhichthedesignatedsubdivisionislocated.
2.
Thefollowingone-to-threecharactersfollowingthehyphendesignatetheparticularsubdivision.
3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:US-TX(U.
S.
StateofTexas),DK-025(DanishcountyRoskilde),MG-T(Antananarivoprovince,Madagascar)UsedIntargetArea2ElementlocCodeUNTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionTheUN/LOCODEdesignatorforthelocationconcerned.
Comments1.
ThetwofirstdigitsarethetwocharacterISO3166-1CountryCodeforthecountryinwhichtheplaceislocated.
2.
ThefollowingthreecharactersaretheUN/LOCODEdesignatorfortheparticularlocationwithinthatcountry.
3.
Nospacesorpunctuationareusedwithinthisdesignator.
4.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Example:USFFB(Fairfield,Alabama,USA),USSUU(Fairfield,California,USA),GBFFD(Falfield,SouthGloucestershire,UK)UsedIntargetArea33.
2.
3contentObjectElementandSub-elements4Theelementisthecontainerelementforspecificmessages.
The5elementMUSTeithercontainancontentcontaineroracontent6container.
Additionalelements(metadata)usedforspecificdistributionofthepayloador7hintsforprocessingthepayloadarealsopresentinthecontainerelement.
8EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page22of421ElementcontentObjectTypeXMLStructureUsageOPTIONAL,MAYusemultipleDefinitionThecontainerelementformessagedataandcontent.
Comments1.
Theisthecontainerelementforspecificmessages.
2.
Themayhaveanoptionalattributethatdefinesanamespaceprefixwhichresolvesambiguouselementnames.
3.
TheelementMUSTcontainexactlyoneofthetwocontentformats:a.
,forvalidnamespacedXMLcontentorb.
,containingoneorbothoftheelements,forreferencetothecontent'slocation,and,fordataencapsulatedinthemessage.
Sub-elementscontentDescriptioncontentKeywordincidentIDincidentDescriptionoriginatorRoleconsumerRoleconfidentialitynonXMLContentxmlContentUsedInEDXLDistribution2ElementcontentDescriptionTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThehuman-readabletextdescribingthecontentobject.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:"CAPmessagefromFEMA","Mapofaffectedarea"or"Photoofmissingchild".
UsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page23of421ElementcontentKeywordTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThetopicrelatedtothemessagedataandcontent,asitmaydeterminemessagedistributionandpresentationdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Examplesofthingsmightbeusedtodescribeincludemessageprocessor,eventstage,resourcecodeandresponsetype.
Sub-elementsvalueListUrnvalueUsedIncontentObject2ElementincidentIDTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThehuman-readabletextuniquelyidentifyingtheincident/event/situationassociatedwiththecontentObject.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page24of421ElementincidentDescriptionTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThehuman-readabletextdescribingtheincident/event/situationassociatedwiththecontentObject.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedIncontentObject2ElementoriginatorRoleTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThefunctionalroleofthemessageoriginator,asitmaydeterminemessagedistributionandpresentationdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Sub-elementsvalueListUrnvalueUsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page25of421ElementconsumerRoleTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThefunctionalroleofthemessageconsumer,asitmaydeterminemessagedistributionandpresentationdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Example:"http://www.
dhs.
gov/NiemRoleType",ICSOperationsBranchSub-elementsvalueListUrnvalueUsedIncontentObject2ElementconfidentialityTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionSpecialrequirementsregardingconfidentialityofthecontentofthis.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page26of421ElementotherTypexsd:otherUsageOPTIONAL,MAYbeusetoaddanunlimitednumberofXMLelementsforenvelopedsigningprocess.
DefinitionSpecialrequirementsallowingforsignatureofthecontentofa.
Comments1.
Thereisnomandatoryvalidationoftheelementsifthenamespacereferencecannotbelocated.
2.
MUSTbeaproperlyformedXMLstring–escaped,ifnecessary.
3.
ElementnamescannotduplicateotherelementnamesinthecontentObject.
Suchduplicationwouldpreventvalidationduetotheambiguityintroduced.
4.
Thiselementmaybeusedforsignatures.
Ifthiselementisusedforexperimentalextensions,suchextensionsmaynotbesupportedbyallusersorinfutureversionsofEDXL-DE.
UsedIncontentObject3.
2.
4nonXMLContentElementandSub-elements2ElementnonXMLContentTypeXMLStructureUsageCONDITIONAL,MUSTuseonceifxmlContentisnotusedDefinitionContainerforcontentprovidedinanon-XMLMIMEtype.
Comments1.
ThecontainerMUSThaveoneorbothoftheelementsand.
2.
Iftheelementisusedinconjunctionwiththeelement,itmustreferenceadatalocationthatcontainsthesamedataasiscontainedintheelement.
Sub-elementsmimeTypesizedigesturicontentDataUsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page27of421ElementmimeTypeTypexsd:stringUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionTheformatofthepayload.
Comments1.
MIMEcontenttypeandsub-typeasdescribedin[RFC2046].
2.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:application/pdf,application/mp3UsedInnonXMLContent2ElementsizeTypexsd:integerUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThefilesizeofthepayload.
Comments1.
Valuemustbeinbytesandrepresenttherawfilesize(notencodedorencrypted).
UsedInnonXMLContent3ElementdigestTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThedigestvalueforthepayload.
Comments1.
Usedtoensuretheintegrityofthepayload.
2.
CalculatedusingtheSecureHashAlgorithm(SHA-1)3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInnonXMLContent4EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page28of421ElementuriTypexsd:anyURIUsageOPTIONAL,MAYuseonceandonlyonceDefinitionAUniformResourceIdentifierthatcanbeusedtoretrievetheidentifiedresource.
Comments1.
MaybeafullabsoluteURI,typicallyaUniformResourceLocator,thatcanbeusedtoretrievetheresourceovertheInternet.
2.
MaybearelativeURInamingafile.
Thismaybejustapointertoafileorspecificallytothefilerepresentedinthe.
UsedInnonXMLContent2ElementcontentDataTypexsd:base64BinaryUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThebase-64encodeddatacontent.
Comments1.
MAYbeusedeitherwithorinsteadoftheelementincontextswhereretrievalofaresourceviaaURIisnotfeasible.
2.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInnonXMLContent3.
2.
5xmlContentElementandSub-elements3ElementxmlContentTypeXMLStructureUsageCONDITIONAL,MUSTuseonceifnonXMLContentisnotusedDefinitionContainerforvalid-namespacedXMLdata.
Sub-elements1.
keyXMLContent2.
embeddedXMLContent3.
Anoptionalnamespaceattributemaybeincluded.
UsedIncontentObject4EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page29of421ElementkeyXMLContentTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionAcontainerelementforcollectedfragmentsofvalidXML.
Comments1.
ExtractsmustcomefromtheXMLdocumentcontainedwithintheelementwithinthecurrentblock.
2.
AllcontentwithinthiselementMUSTbeexplicitlynamespacedasdefinedintheenclosingtag.
3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInxmlContent2ElementembeddedXMLContentTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionTheelementisanopencontainerforvalidXMLfromanexplicitnamespacedXMLSchema.
Comments1.
ThecontentMUSTbeaseparately-namespacedwell-formedXMLdocument.
2.
TheenclosedXMLcontentMUSTbeexplicitlynamespacedasdefinedintheenclosingtag.
3.
EnclosedXMLcontentmaybeencryptedand/orsignedwithinthiselement.
UsedInxmlContent3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page30of423.
2.
6ListandAssociatedValue(s)1ElementvalueListUrnTypexsd:stringUsageCONDITIONAL,MAYuseonceandonlyonceDefinitionThenameofacertifiedlistmaintainedbytheCommunityofInterest(COI)forthevaluereferenced.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution/senderRoleEDXLDistribution/recipientRoleEDXLDistribution/keywordcontentObject/contentKeywordcontentObject/originatorRolecontentObject/consumerRole2ElementvalueTypexsd:stringUsageCONDITIONAL,MAYusemultipleDefinitionAvaluefromacertifiedlistmaintainedbytheCommunityofInterest(COI)forthereferencedelement.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution/senderRoleEDXLDistribution/recipientRoleEDXLDistribution/keywordcontentObject/contentKeywordcontentObject/originatorRolecontentObject/consumerRole3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page31of423.
2.
7ExplicitAddressing1ElementexplicitAddressSchemeTypexsd:stringUsageREQUIRED,MUSTuseonceandonlyonceDefinitionIdentifiesthedistributionaddressingschemeused.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examplesforthistypeofdistributionincludes-email,militaryUSMTF,etc.
.
.
UsedInexplicitAddress2ElementexplicitAddressValueTypexsd:stringUsageREQUIRED,MAYusemultipleDefinitionAproperlyformed-escapedifnecessary-XMLstringdenotingtheaddresseesvalue.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInexplicitAddressEDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page32of42AppendixA.
XMLSchemafortheEDXLDistribution1Element23489101112131415161718192123252729313334353637383940414244454648EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page33of42234567891112131415161718192021222324252627293132333435363738394041424344454647484950EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page34of421245678911131517192021222324252627282930313233343536373839404142434445464748EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page35of42AppendixB.
EDXL-DEExamples1B.
1EDXL-DEWithCAPPayload2ThefollowingisaspeculativeexampleintheformofanEDXL-DEXMLmessage.
34ieam_e3_25XML200562005-11-15T16:53:00-05:007Exercise8Update910http://www.
niem.
gov/EventTypeList11Explosion12131433.
4745,-112.
117433.
4745,-112.
023833.
4238,-112.
023833.
4238,-112.
117433.
4745,-15112.
1174161718CAPmessagefromDOTadvisingbestalternateRoutes1920212223Vendorgenerated24AZDOT252005-11-15T16:58:00-05:0026Exercise27Update28Public2930Transport31TrafficRoutes32Immediate33Moderate34Likely35TrafficadjustmentsensureclearroutestoSt.
JosephsHospital36andPhoenixChildrensHospitalonThomasRd.
3738BestRoutes3938.
91655012246089,-77.
0201626794340738.
91655012246089,-4077.
011709839116538.
907662564641285,-77.
011709839116538.
907662564641285,-77.
020162679434074138.
91655012246089,-77.
0201626794340742434445464748495051EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page36of42B.
2EDXL-DEWithMultipleEncryptedPayloads1ThefollowingisaspeculativeexampleintheformofanEDXL-DEXMLmessage.
234Sandia0015dellis@sandia.
gov62005-08-07T18:05:00-07:007Actual8Report910urn:sandia:gov:sensors:senderRole11SENTRYsensormanagmentsystem1213isrepeatedthreetimes,sinceWarningandreporting16systemswantCAPcontent,HazardPredictionsystemswantdetailedsensor17outputs,andsituationalawarenesssystemswantthelocationandtypeofevent.
18-->1920urn:sandia:gov:sensors:reciepentRole21WarningandReportingDevices22HazardPredictionapplications23SituationalAwarnessapplications24252629containerelements.
30-->313233urn:sandia:gov:sensors:keywords34SNMDetection3536374243DMISCOGs44173445352046474849e-mail50dellis@sandia.
gov51525357Unclassified5859elementswouldbepresent.
-->606164US65California66EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page37of42USA-SF123containerelements.
11-->1213isaddedtoallowreferencingbetweens-->1415"urn:sandia:gov:sensor:detection.
event.
id"1610.
2.
2.
1:2005-08-07T18:00:00Z1718wouldhavetobetransformedinCAP1.
1toCAP1.
021Conversions22-->23Unclassified242526282930deskey.
bin313233GSCinwYBtwJxp6kcZPGqE6rybCfsnvI6Lz+IZVPqnRfnI1hWq7cI2WT4BsjBBQCu34TE68pCQ/keOGtvYJ5yNVZEuAnIhOf37OEiqk1rcBARXb03LCYvlXYKA1zmEC5yFT35CUcyCMV146G4eNU1H7F+wbMjbSgHjOYgYe+rpjOVYAK9Gs4Uj+CWhijjxpr5Y/vX361NEtHFhLsXC9cSfhXWVmi3veXwbDycC+QtcvQL/Rfr45bDwsJnCCutTzfmoqF1CS37BgYUi6osW+XhoRkAttzKbRADVZ6bG5SMkZN0SKiwSaCyKyMKjdpiQwYQhjUXUoAn38veBylXREqfmtOIm/pT7Y45pabWNG9l3aljil8P7qZ5Y26Q0X+i0U+eEGuafHrMVb39S/QBpAkNbP5/f9UR3B4t5t7hLOsvDXdR6CWFBNsrczLjZ7YC2O+g1HBl8YsQdREA40And3PKgoy8QlKv6ZLA+aJzQpSvzbSu3btgN6vyF3GGPqKprVIYRFouaJHYgL81zn41zZovnH4lubwa+YPgD0H48a/FM2LaA8euPzMFDWIki0fm5DoZZzYCmPKmfLJS10RG42lUKzW0svDw8I1AwX6LBssPm+hoBa7HzTnuM40FD+vsmET+p0bqBtaUSnDHrHXLzp43P6TrcNr5R5cxQ4C+shwezFQDNKbioyC6m5PaTH/6qhlTmE32vP8ySnMKvL74QCfP44w8hTZxwq9UVLPq2WKJcI0Phc1e3HoYkBTpVk9OUf/CVaxMXGOiXReeLXGPC1IQnn45a6xw7ImkgeCFcY+rcttq2fE3UqWtc5R6J16/Jv666K9fgCbXRVhaBdMDYpz0GKFa46gMJulUK6zTtah+bidtUrF31UWAX+wqIqmDFJ1ivJaRbLEiEVCrt0jKwOjuR41dDD47VS5j2BuvmZ5TILnOnHFU6H4GudnwjpL01eLrwELSfKmbQmUx2A0L6NBj9SRkXXHW48onZV6uX+c3CR46OekvxYyMi1rxE2zQPykfh/mELRhGgyDVqtdFQwhDx2Klu+Gh2z493nC51yn37laIO5KSvL5Gkb6jxFVrcUvrcp4pX5czw7/VWbxWoRPY7Bus3akhPu+I50/jchv7SiVRP5mX4Ewh+yeduYX+UZLo07m5zhAMtmFdiLJV9tgHVTJf7ZJ3bGWP+h51Et0Nl98hGV362cSRhkoLJwNmOgIpGXSMO6T5nA1MZhJ6CkCP8QV1zpKrLVJSRZRn52fffBjdl8CzipzjE05JVKbyfbq9I33fkWMbda+Vo9ZMiDinOee6KxnDnxll9ca9Lg53+dl9J0qjJz5VwnWLRCeprsOXt+LlmeHC60NJgRarhidlrfuxmONM+QZTk4ZQGIPD54fsk5ftJtzvHgW5G/wN7fxyLh1AqQucW13IAsmfwuJS0+HntYZVoXqGjRg1sK6snx55zteJJm6a2OyG/M5RvLAEVhOKWyU2+9hjzts8ySg6Qb2+KrUTRQ8JBmVBeSjR2svv562AWyBYj29JAdAikX9gfGDDvTG9GqJr+jFE9mfOBtg7lsdLezQKvvNMsntm6RdSpu57dA3vL8uBIliGBNJZSOOKr06BXp6PjbL6Ov47EbOfvP8Vm9vKQD7PmjPaIbN1bUr958V9cHUQ5h6LSecnAy/FZQMLdcamNAIhpiEgoQcwEmaa+1/wTv7LppqxZkFVQQbI2m59nC9Ujcd08g2Qyh+0YCHP50SbCwDe2W+CYBi7QBDdF3qt45zaZnHyRm/yXhVWCJX160+0WY/+OukquhaWJ8Y0fygA1yk7Jyqqpu2XU9X0Vu8oETQlL/+37mEzy/beL9VNnr61eU7bfQBAnYw1CkeXs5rAcc1vllZEU22Uqg3H5saOQlEHgV1NxL+0C+A9/Q2ZsaFI62BDDIiH+f6+6aUno6fotGUA==636465666768697071EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page38of4212345przigAg811cHIqSXpIrFg1BGx20=678BH8MGSS9QAlgq7a7I7PF5XjKsqaDumTt3cSWxBmwErByvQuaarOgH6MMflVLkG0Y9tv6zaOqR6Kis4giTqtZBo8QCkGukpre2gurdi3Ws0yO3Wt8nWrcH3QAUllhocXpV10gXahZ8MzHc9zuJq9+bl+S72czTjS0UdCvk/MMRV/xhwZ/1QSn+ffh0s3RU6Cn1Q011aYSuDtX5mAGUWAzJghKgK/qSM5jF4c233g7M4m+Rul3C+QOFBOMGmp+NodnG9b0z12hycJGVdUpY0a+1r0quu2pmdLZnIQVY1stWNFS3wI9RzdslwzoGP9/nRARGS0kLf113De+WB4Xdar48A9WJwng0iA==1415rsakey.
pem161718242526"urn:sandia:gov:sensor:detection.
event.
id"2710.
2.
2.
1:2005-08-07T18:00:00Z2829Unclassified303132343536deskey.
bin373839MiKRUfL1Yb3Vw9JcewTAYVnYT3Zh2Tf9d0fhRyGreJW0FWoXr1/27AXFXBTmZC/240hw9cMMFaGKeXNr1tK0Os1Lozx9uZZYoF5UiNH18KD/WnNbpwk+ttK3TwRcxBfowm41lzzClMn5suHeUM2PFiCll1Wup8cSfwAqptXVF3sZrLAMsQWJmGfyGYYCiaZ+P3NZ42hiVFamDB7D9id5HJ3qHLNcxucGNFA5TfOwe/euP7O1ah9Q7Rp2nxsXF9PaQYziSS43G4I/J+v+FwuJXhbLqU1PcbP4ofCLg+s6tph2kJxFArGSX9u3k7FHvp3tLZnskXCw44iYRGDqrSGrmLt7bTtMmF/IhFQc4x0aE4ldVEN999uQ6KnDyd22KdUJhupRH8UqZz45+sKVJF3+yatOsroCwOCjTe/GqnNRZNtG59dGC5D247LH2AVn/6WU+txFflZhUg0z46A0PElIMicguTRaEaIDGJF/QvqzTE1r3iYgHXIGfgEhQiix35ZURWUTcATrKyNFFE47/CD8+v6YHGbKrgeJDnvJ5AqjZSU1NajOpCtbhWQm1D878OhjCN+T689PZPB2X2nz48f1kupkZ/Fq6Z6aF77j0xp4wB7bpFW5ssWUHySwdg5vYw4hS3Geg5wn3AQViqTGI849oRaDa3wT9byHq+cq83WqA3aroJOXzD/HQCmKNhmPFqYj503JH3aZcWNrDxHyBQRr50Libv4o9v4LCGviaKT/2y0S25t5KkL/MJA2c6LIngmhHKQFr1sruWgSrjHn9KtagU51KeYqYlgKK6s56X+PHQvusXoxpgDLjXpVVhNpF/mRh+86J4zY3JAIcfIZJQ05DjvX52io2iZY/hstzkTfY5+CPvKH7FmuYqeoU7Nano7+EGSB4w0TnSoDfm9D/RIsAtwdpu537WonmeguEK37u0bNuXQHi9LZTELD0L2HIkPVdo4BYq26WMe5vZdwVkW6up92AIQE547KvADQZZUGDVoKA3Njt9O5s6g+a14wcHqxD+FS8veacDsYFrmhs+0WYlyWtDJERL55+y0qtHLmSi/kTdYoKRGx+/lyUl8FIfqOnk2dk3BicbQ3kyEbngV3qHBrYqrVITTB56eMUKxL3wB5OkcCn3u6Nqun14QFmf8O9KEZGXZZqdQs7jz6MV3yjPvzelmLs9nbCm573eXFGrSlHbbwCLQBconzDWgfoN6W/lTRv3z8RmTg+Z+3CjK2MRt6x5XZTcDqk4JW58wozh2btLz4Yc2xUbclbtVd3muOhBq3eSsGXC6xX4fxW0cuqi6UsOZRA2kiKJHY+V592KFO9/y3x4arscIsBwfmNVZYt6bCoy/Or0yva49yV/A//8JFN7aGLh530Dt53J4H60bcsQ1n3q7kxir5VLuNj0aZYHjtGu7gzPa1UpPAJ0trqro4qinspnkdRueW7SQYcd61ufF5OG4GMTI+VjX4MnOMOgnYiAaZqrBoH3B5t7bAKeszVPs6S9NPfkzx1nkqminG62/Z/hBpmsFlcUlS+qylXU7umHvssE2juap1NQUaL6IyHQ0tZzsQd0e6mYkDuzNNbH634l9czPXXXfvcKRJnJ0Yho9j30YfBWyllF67SMewYhcNg35tAbstXe+Ghg+D/TVcd64SZ4r1Cmk49IQE3SNwIO6vGUtMhmCJGq+yJx89lfMLijZRBr18exdQ1hoVeQ+YzyY65rZ/e6PTZHVkbcHGLsd+InyBdz3MTCmaYLGGG6gGtL42nJYmXDUIwWTAFXcWo0jDh66HO28OimZg8QGhiSAAc8uXzwbtjVHIJTC27e6iqldNxnYDoNWDZxVjI3fccbvUwmz67702I+4Kb/n5M1X5RXeMZ12OvlRRnQi7nhZuTeTMEbRizHptWP5yse3LcNjRJ2Jr268697071EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page39of4212345678910N7NvgXfahdGZPjb9o0XvwejLI5o=111213Tg8zP+/1Cg/3MR9iSareJb7snexQ3DjBxGSL3xH+Kf3Kh5NQq/Uwagw/fmI2wcxc14ac/2fz893HeTkXGn8mShg+wmdoRwNykp5uHPtAzcFBKlh3v7FemtM9M73XbX7KsY15fM0J+RTHUxp4tTMYUPogSEJWiSGSGVbp+MALtUH799fGqqqOREyuljfVIlLvvCog16wOd6n7J8S2sHjyRXEw5AVFnxL6k02TgjztbEuoLu+qvEZOIGXmj9yfy4nj41RNXe17HMOS1IAcOQgx5vNzju2slFIWzlmvjqq+7aVg5hy0yBiXJuljvigTOxrwHScaYW8o18HDpQHwM6EXbgW3uaWnf9Kg==1920rsakey.
pem21222324PhotoimagefromSensor:RADDET-01,Site:GoldenGateBridge,havinga25DetectionclassofSNM2627"urn:sandia:gov:sensor:detection.
event.
id"2810.
2.
2.
1:2005-08-07T18:00:00Z2930Unclassified3132image/jpeg33http://sentry/photoCapture/10.
2.
2.
1:2005-08-07T18:00:00Z3435363738394041424344io7Katgoo77YNfQYdZMB8taoeKg=454647AjQXGgp9h5TC2D+bh9w59sbmtUpgE/IeZVdDQM+zi58XT2RPb7OXAAABni78WduA48uP6nxL6k+BBo4G+TgaqWvCQIqdlDO+qyMnM0ExPui5eg00jstbwiSeYxSt2VQqS249RD2vR811at0XwIkMpugSftKNJBZgB9mhRqQgP+E0nDJJPNYDz0bLJjp0J/EDxn4H506qx6GpDKgDc//53jVhOb4zZPIERsTLjPxpOOnBK31cs5Rf6vU9MyOOBTHZgpvoza51muhejW1CIJfYjd/OoKQ9Hiv4MCX4v/dX7n6ePHZaDxNeCccDIjoVYrAHEWxQ9hE652rqriugNLZ3Lh8sUzhZLTyg==5354rsakey.
pem5556576162PhotoimagefromSensor:RADDET-01,Site:GoldenGateBridge,havinga63DetectionclassofSNM6465"urn:sandia:gov:sensor:detection.
event.
id"6610.
2.
2.
1:2005-08-07T18:00:00Z6768Unclassified6970image/jpeg71EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page40of421/9j//gAoaAkAAAAAAECMWv/mOzNdGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD/2wBDAAgGBgcGBQgH2BwcJCQgKDBQNDAsLDBkSEw8UHRofHh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/3AYG3nGaeEI5BoACp6gmmgKwOBzQBFICRUZXIwOKAE8sjmms5Uc0AU5JwTioxLjpQBHIc5qpJQBGr4YNSgjFACbuacQCtAEIXDVOOlACgUuAaAG4xVbUP+Qdc/9czQB//Z5678910111213141516PkrjafcKUd027EETVu5JwqlubcA=171819NvqlkBLs4GpM+t+uoWQ53rmjNT43qdwbMsEoiB0a2BRwqkmynKQDbA2eIHmxfBfo20xe+q+15v/2IGQQw+5XmWtMx8QIQkGBElSdlybOKibxBqNuWH+J6yR1mIA6bOmBE+21+F2zA9DuvKZVLa8El1pUGke6FeIzoMC7TdDcBtmSAkRMXxe8MjxjxApM3vnMSt9A22iCo2EUx4qYf82iJ9FX7vIFFfL2QW38RvZqY+rjXsHV5OK3fkTPFI+ZE5lIrHKjb323gu409JrdNtSy/wLd/WLypiYFNDZXxT6i5wBbdAvBkQ0jHECOJjfN+h1bHkvT4wLX24Cpc26QQ6Ic3goSLojC3rjw==2526rsakey.
pem272829373839EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page41of42AppendixC.
Acknowledgments1C.
1OASISEmergencyManagementTechnicalCommittee:2PattiAymond,IEM3ArtBotterell,Individual4RexBrooks,HumanMarkup.
org,Inc.
5LenBullard,Individual6MarkCarlson,Conneva,Inc.
7EliotChristian,USDepartmentoftheInterior8JamesBryceClark,OASIS9RobinCover,OASIS10DavidDanko,ESRI11SukumarDwarkanath,Individual12David,Ellis,Individual13JackFox,USDepartmentofHomelandSecurity14TimGrapes,ScienceApplicationsInternationalCorporation15GaryHam,DisasterManagementInteroperabilityServices16AdamHocek,Individual17TravisHubbard,DisasterManagementInteroperabilityServices18RenatoIannella,NICTA19ElysaJones,WarningSystems,Inc.
20JeffKyser,WarningSystems,Inc.
21MaryMcRae,OASIS22TomMerkle,LockheedMartin23GaryPoindexter,Individual24MichelleRaymond,Individual25CarlReed,OpenGISConsortium(OGC)26JuliaRidgely,Individual27EleanorRobinson,AnteonCorporation28KwasiSpeede,AnteonCorporation29AaronTemin,Individual30LeeTincher,ScienceApplicationsInternationalCorporation31BrettTrusko,OASIS32RichardVandame,USDepartmentofHomelandSecurity33SylviaWebb,Individual34KonstantinWilms,Individual35EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page42of42AppendixD.
RevisionHistory12RevisionDateEditorChangesMade3
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page1of42EmergencyDataExchangeLanguage(EDXL)DistributionElement,v.
1.
0OASISStandardEDXL-DEv1.
0,1May2006DocumentIdentifier:EDXL-DE-V1.
0OASISIdentifier:{EMTC}-{EDXL-DE}-{1.
0}(HTML)(Word)(PDF)Location:ThisVersion:http://docs.
oasis-open.
org/emergency/EDXL-DE/V1.
0TechnicalCommittee:OASISEmergencyManagementTCChair(s):ElysaJones,WarningSystems,Inc.
-Editor(s):MichelleRaymond,IndividualSylviaWebb,IndividualPattiIlesAymond,IEM,Inc.
-Subject/Keywords:distributionelement,dissemination,routing,payload,alert,resourcemessage,emergency,informationsharing,dataexchange,emergencyresponse,emergencymanagement,geospatial,political,targetarea,messagedelivery,messagesender,messagerecipient,distributionstatus,distributiontype,senderrole,recipientrole,responsetype,eventcause,confidentiality,circle,polygon,location,contentobject,consumerrole,notification,XMLmessage,distributiontype,geography,incident,senderidentification,senderid,recipientidentification,recipientid,inter-agency,emergencyinformation,functionalrole,recipientaddress,hazard,distributionstatus,distributiontype,eventtype,eventetiology,messageprocessor,eventstage,resourcecodeandresponsetypeRelatedWork:Thisspecificationisrelatedto:CAP1.
1-http://www.
oasis-open.
org/committees/emergencyTheCommonAlertingProtocol(CAP)providesanopen,non-proprietarydigitalmessageformatforalltypesofalertsandnotifications.
CAPmessagesarerecommendedasoneofthestandardizedformsforXMLbasedmessagecontent,tobedistributedbythisDistributionElement.
EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page2of42Abstract:ThisDistributionElementspecificationdescribesastandardmessagedistributionframeworkfordatasharingamongemergencyinformationsystemsusingtheXML-basedEmergencyDataExchangeLanguage(EDXL).
Thisformatmaybeusedoveranydatatransmissionsystem,includingbutnotlimitedtotheSOAPHTTPbinding.
Status:ThisdocumentwaslastrevisedorapprovedbytheEmergencyManagementTechnicalCommitteeontheabovedate.
Thelevelofapprovalisalsolistedabove.
Checkthecurrentlocationnotedaboveforpossiblelaterrevisionsofthisdocument.
Thisdocumentisupdatedperiodicallyonnoparticularschedule.
TechnicalCommitteemembersshouldsendcommentsonthisspecificationtotheTechnicalCommittee'semaillist.
OthersshouldsendcommentstotheTechnicalCommitteebyusingthe"SendAComment"buttonontheTechnicalCommittee'swebpageatwww.
oasis-open.
org/committees/emergency.
Forinformationonwhetheranypatentshavebeendisclosedthatmaybeessentialtoimplementingthisspecification,andanyoffersofpatentlicensingterms,pleaserefertotheIntellectualPropertyRightssectionoftheTechnicalCommitteewebpageatwww.
oasis-open.
org/committees/emergency/ipr.
php.
NoticesOASIStakesnopositionregardingthevalidityorscopeofanyintellectualpropertyorotherrightsthatmightbeclaimedtopertaintotheimplementationoruseofthetechnologydescribedinthisdocumentortheextenttowhichanylicenseundersuchrightsmightormightnotbeavailable;neitherdoesitrepresentthatithasmadeanyefforttoidentifyanysuchrights.
InformationonOASISprocedureswithrespecttorightsinOASISspecificationscanbefoundattheOASISwebsite.
Copiesofclaimsofrightsmadeavailableforpublicationandanyassurancesoflicensestobemadeavailable,ortheresultofanattemptmadetoobtainagenerallicenseorpermissionfortheuseofsuchproprietaryrightsbyimplementersorusersofthisspecification,canbeobtainedfromtheOASISPresident.
OASISinvitesanyinterestedpartytobringtoitsattentionanycopyrights,patentsorpatentapplications,orotherproprietaryrightswhichmaycovertechnologythatmayberequiredtoimplementthisspecification.
PleaseaddresstheinformationtotheOASISPresident.
CopyrightOASISOpen2006.
AllRightsReserved.
Thisdocumentandtranslationsofitmaybecopiedandfurnishedtoothers,andderivativeworksthatcommentonorotherwiseexplainitorassistinitsimplementationmaybeprepared,copied,publishedanddistributed,inwholeorinpart,withoutrestrictionofanykind,providedthattheabovecopyrightnoticeandthisparagraphareincludedonallsuchcopiesandderivativeworks.
However,thisdocumentitselfdoesnotbemodifiedinanyway,suchasbyremovingthecopyrightnoticeorreferencestoOASIS,exceptasneededforthepurposeofdevelopingOASISspecifications,inwhichcasetheproceduresforcopyrightsdefinedintheOASISIntellectualPropertyRightsdocumentmustbefollowed,orasrequiredtotranslateitintolanguagesotherthanEnglish.
ThelimitedpermissionsgrantedaboveareperpetualandwillnotberevokedbyOASISoritssuccessorsorassigns.
EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page3of42Thisdocumentandtheinformationcontainedhereinisprovidedonan"ASIS"basisandOASISDISCLAIMSALLWARRANTIES,EXPRESSORIMPLIED,INCLUDINGBUTNOTLIMITEDTOANYWARRANTYTHATTHEUSEOFTHEINFORMATIONHEREINWILLNOTINFRINGEANYRIGHTSORANYIMPLIEDWARRANTIESOFMERCHANTABILITYORFITNESSFORAPARTICULARPURPOSE.
EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page4of42TableofContents1.
INTRODUCTION51.
1PURPOSE51.
2HISTORY51.
3STRUCTUREOFTHEEDXLDISTRIBUTIONELEMENT.
61.
3.
161.
3.
261.
3.
361.
4APPLICATIONSOFTHEEDXLDISTRIBUTIONELEMENT61.
5TERMINOLOGY.
61.
6NORMATIVEREFERENCES.
71.
7NON-NORMATIVEREFERENCES.
72.
DESIGNPRINCIPLESANDCONCEPTS(NON-NORMATIVE)82.
1DESIGNPHILOSOPHY82.
2REQUIREMENTSFORDESIGN82.
3EXAMPLEUSAGESCENARIOS92.
3.
1DistributionofEmergencyMessage/sorAlertsBasedonGeographicDeliveryAreaandIncidentType.
92.
3.
2EncapsulationandDistributionofOneorMoreEmergencyMessagesorAlertsorNotifications92.
3.
3DistributionofResourceMessagesorReports.
92.
3.
4DistributionofWell-FormedXMLMessages.
93.
EDXLDISTRIBUTIONELEMENTSTRUCTURE(NORMATIVE)103.
1DOCUMENTOBJECTMODEL103.
2DATADICTIONARY.
113.
2.
1EDXLDistributionElementandSub-elements.
113.
2.
2targetAreaElementandSub-elements183.
2.
3contentObjectElementandSub-elements213.
2.
4nonXMLContentElementandSub-elements.
263.
2.
5xmlContentElementandSub-elements.
283.
2.
6ListandAssociatedValue(s)303.
2.
7ExplicitAddressing31APPENDIXA.
XMLSCHEMAFORTHEEDXLDISTRIBUTIONELEMENT.
32APPENDIXB.
EDXL-DEEXAMPLES.
35B.
1EDXL-DEWITHCAPPAYLOAD.
35B.
2EDXL-DEWITHMULTIPLEENCRYPTEDPAYLOADS36APPENDIXC.
ACKNOWLEDGMENTS.
41C.
1OASISEMERGENCYMANAGEMENTTECHNICALCOMMITTEE:41APPENDIXD.
REVISIONHISTORY.
42EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page5of421.
Introduction11.
1Purpose2TheprimarypurposeoftheDistributionElementistofacilitatetheroutingofanyproperlyformattedXML3emergencymessagetorecipients.
TheDistributionElementmaybethoughtofasa"container".
It4providestheinformationtoroute"payload"messagesets(suchasAlertsorResourceMessages),by5includingkeyroutinginformationsuchasdistributiontype,geography,incident,andsender/recipientIDs.
61.
2History7TheDisasterManagementeGovInitiativeoftheDepartmentofHomelandSecurity(DHS)determinedin82004tolaunchaprojecttodevelopinteragencyemergencydatacommunicationsstandards.
Itcalled9togetheragroupofnationalemergencyresponsepractitionerleadersandsoughttheirguidanceon10requirementsforsuchstandards.
InJune,2004thefirstsuchmeetingidentifiedtheneedforacommon11distributionelementforallemergencymessages.
SubsequentmeetingsofaStandardsWorkingGroup12developeddetailedrequirementsandadraftspecificationforsuchadistributionelement(DE).
13DuringthesameperiodtheDMInitiativewasformingapartnershipwithindustrymembersofthe14EmergencyInteroperabilityConsortium(EIC)tocooperateinthedevelopmentofemergencystandards.
15EIChadbeenaleadingsponsoroftheCommonAlertingProtocol(CAP).
Bothorganizationsdesiredto16developanexpandedfamilyofdataformatsforexchangingoperationalinformationbeyondwarning.
17EICmembersparticipatedinthedevelopmentoftheDE,andinthebroaderdesignofthedesignofa18processforthedevelopmentofadditionalstandards.
ThiswasnamedEmergencyDataExchange19Language(EDXL).
20ThegoaloftheEDXLprojectistofacilitateemergencyinformationsharinganddataexchangeacrossthe21local,state,tribal,nationalandnon-governmentalorganizationsofdifferentprofessionsthatprovide22emergencyresponseandmanagementservices.
EDXLwillaccomplishthisgoalbyfocusingonthe23standardizationofspecificmessages(messaginginterfaces)tofacilitateemergencycommunicationand24coordinationparticularlywhenmorethanoneprofessionisinvolved.
Itisnotjustan"emergency25management"domainexercise.
26Itisanationaleffortincludingadiverseandrepresentativegroupoflocal,stateandfederalemergency27responseorganizationsandprofessionals,followingamulti-stepprocess.
Justasadata-focusedeffort28targetsshareddataelements,theEDXLprocesslooksforsharedmessageneeds,whicharecommon29acrossabroadnumberoforganizations.
Theobjectiveistorapidlydeliverimplementablestandard30messages,inanincrementalfashion,directlytoemergencyresponseagenciesinthetrenches,providing31seamlesscommunicationandcoordinationsupportingeachparticularprocess.
Theeffortfirstaddresses32themosturgentneedsandproceedstosubsequentmessagesetsinaprioritizedfashion.
Thegoalisto33incrementallydevelopanddeliverstandards.
34EDXLisintendedasasuiteofemergencydatamessagetypesincludingresourcequeriesandrequests,35situationstatus,messageroutinginstructionsandthelike,neededinthecontextofcross-disciplinary,36cross-jurisdictionalcommunicationsrelatedtoemergencyresponse.
37TheprioritiesandrequirementsarecreatedbytheDMEDXLStandardsWorkingGroup(SWG)whichisa38formalizedgroupofemergencyresponsepractitioners,technicalexperts,andindustry.
39EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page6of42ThedraftDEspecificationwastrialedbyanumberofEICmembersstartinginOctober,2004.
In1November,2004,EICformallysubmittedthedrafttotheOASISEmergencyManagementTechnical2Committeeforstandardization.
31.
3StructureoftheEDXLDistributionElement4TheEDXLDistributionElement(DE)comprisesanelementasdescribedhereafter,5optionalelementsdescribinggeospatialorpoliticaltargetareaformessagedelivery,anda6setofelementseachcontainingspecificinformationregardingaparticularitemof7content.
TheincludedcontentmaybeanyXMLorothercontenttypeoraURItoaccessthecontent.
8Theblockmaybeusedwithoutcontenttoformthebodyofaroutingqueryto,or9responsefrom,adirectoryservice.
101.
3.
111Theelementassertstheoriginator'sintentastothedisseminationofthatparticular12messageorsetofmessages.
13Notethatuseoftheelementdoesnotguaranteethatallnetworklinksandnodeswill14implementtheasserteddisseminationpolicyorthatunintendeddisclosurewillnotoccur.
Wheresensitive15informationistransmittedoverdistrustednetworks,itshouldbeencryptedinaccordancewiththeWeb16ServicesSecurity(WSS)standardhttp://docs.
oasis-open.
org/wss/2004/01/oasis-200401-wss-soap-17message-security-1.
0.
pdfwithanyupdatesanderratapublishedbytheOASISWebServicesSecurity18TechnicalCommitteehttp://www.
oasis-open.
org/committees/tc_home.
phpwg_abbrev=wss,orsome19othersuitableencryptionscheme.
201.
3.
221Theisacontainerelementforthegeospatialorpoliticalareatargetingoftherecipientofthe22messagecontent.
Itcontainsdatanecessarytotheoriginator'sintent,basedonlocationtargeting,asto23thedisseminationofthatparticularmessageorsetofmessages.
241.
3.
325Theisacontainerelementforspecificmessages.
TheelementMUST26eithercontainancontentcontaineroracontentcontainer.
Additional27elements(metadata)usedforspecificdistributionofthepayloadorhintsforprocessing28thepayloadarealsopresentinthecontainerelement.
291.
4ApplicationsoftheEDXLDistributionElement30TheprimaryuseoftheEDXLDistributionElementistoidentifyandprovideinformationtoenablethe31routingofencapsulatedpayloads,calledContentObjects.
Itisusedtoprovideacommonmechanismto32encapsulatecontentinformation.
331.
5Terminology34Thekeywords"MUST","MUSTNOT","REQUIRED","SHALL","SHALLNOT","SHOULD","SHOULD35NOT","RECOMMENDED","MAY",and"OPTIONAL"aretobeinterpretedasdescribedinKeywordsfor36useinRFCstoIndicateRequirementLevels[RFC2119].
37EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page7of42Inaddition,withinthisSpecification,thekeyword"CONDITIONAL"shouldbeinterpretedaspotentially1"REQUIRED"or"OPTIONAL"dependingonthesurroundingcontext.
Thetermpayloadreferstosome2bodyofinformationcontainedinthedistributionelement.
31.
6NormativeReferences4[RFC2046]5N.
Freed,MultipurposeInternetMailExtensions(MIME)PartTwo:MediaTypes,6http://www.
ietf.
org/rfc/rfc2046.
txt,IETFRFC2046,November1996.
7[RFC2119]8S.
Bradner,KeywordsforuseinRFCstoIndicateRequirementLevels,9http://www.
ietf.
org/rfc/rfc2119.
txt,IETFRFC2119,March1997.
10[RFC3066]11H.
Alvestrand,TagsfortheIdentificationofLanguages,12http://www.
ietf.
org/rfc/rfc3066.
txt,IETFRFC3066,January2001.
13[WGS84]14NationalGeospatialIntelligenceAgency,DepartmentofDefenseWorldGeodetic15System1984,http://earth-info.
nga.
mil/GandG/tr8350_2.
html,NGATechnicalReport16TR8350.
2,January2000.
17[XML1.
0]18T.
Bray,ExtensibleMarkupLanguage(XML)1.
0(ThirdEdition),19http://www.
w3.
org/TR/REC-xml/,W3CREC-XML-20040204,February2004.
20[namespaces]21T.
Bray,NamespacesinXML,http://www.
w3.
org/TR/REC-xml-names/,W3CREC-22xml-names-19990114,January1999.
23[dateTime]24N.
Freed,XMLSchemaPart2:DatatypesSecondEdition,25http://www.
w3.
org/TR/xmlschema-2/#dateTime,W3CREC-xmlschema-2,October262004.
271.
7Non-NormativeReferences28EDXLGeneralFunctionalRequirements29EDXLGeneralFunctionalRequirements,http://www.
oasis-30open.
org/committees/document.
phpdocument_id=10031&wg_abbrev=emergency,31November2004.
32EDXLDistributionElementImplementer'sGuide33EDXLDistributionElementImplementer'sGuide,http://www.
oasis-34open.
org/committees/document.
phpdocument_id=14120&wg_abbrev=emergency,35August2005.
36EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page8of422.
DesignPrinciplesandConcepts(non-normative)12.
1DesignPhilosophy2BelowaresomeoftheguidingprinciplesoftheDistributionElement:3ProvideanOpenContainerModeltoenabledisseminationofoneormoreemergencymessages4Provideflexiblemechanismstoinformmessageroutingand/orprocessingdecisions5Enabledisseminationofmessagesbasedongeographicdeliveryarea6Useandre-useofdatacontentandmodelsdevelopedbyotherinitiatives7Businessprocess-drivenspecificmessagingneedsacrossemergencyprofessions8Supportingeverydayeventsandincidentpreparedness,aswellasdisasters9Facilitateemergencyinformationsharinganddataexchangeacrossthelocal,state,tribal,10nationalandnon-governmentalorganizationsofdifferentprofessionsthatprovideemergency11responseandmanagementservices12Multi-useformat-Onemessageschemasupportsmultiplemessagetypes(e.
g.
,alert/update/13cancellations/acknowledgments/errormessages)invariousapplications(actual/exercise/test14/systemmessage.
)152.
2RequirementsforDesign16TheDistributionElementspecificationshould:171.
DefineasinglecompoundXMLstructure(oranequivalentsinglestructureiftranscodedinto18anotherformat)includingtherequiredandoptionalelementsdefinedbelow.
192.
Specifyadesiredgeographicdeliveryarea,expressedingeospatialcoordinatesorusing20political/administrativecodes213.
Allowtheabilitytoencapsulateapayloadorsetofpayloads224.
Takeamodularapproachtotheenumerationsofelementvalueswhichmayevolveovertime,23e.
g.
byreferringtoaseparateschemaforthoseenumerations.
245.
Specifyuniquedistributionandsenderidentifiers256.
Specifythedateandtimethedistributionwassent267.
Specifytheactionabilityofthedistributionmessage(e.
g.
,real-world,test,exercise)278.
Specifythefunctionaltypeofthedistributionmessage(e.
g.
,report,request,update,cancellation,28etc.
)299.
Specifythatthefollowingelementsmaybepresentinavalidpayload:30a.
Aspecificationoftheformatofthedistributionmessage(e.
g.
,theURIofanXMLSchema31forthemessage)32b.
Thefunctionalroleand/ortypeofthesenderofthedistributionmessage33c.
Oneormorefunctionalroleand/ortypeofdesiredrecipientsofthedistributionmessage34d.
Areferencetooneormorepreviousdistributionmessages35e.
Oneormoretypesofresponseactivityinvolved36f.
Areferencetothetypeofincident37g.
Oneormorecharacterizationoftheetiologyofthesubjecteventorincident(e.
g.
,38terrorism,natural,underinvestigation,etc.
)39h.
Theincidentnameorotheridentifierofoneormoreeventorincident40i.
Areferencetooneormoreresponsetypes.
41j.
Oneormorespecificrecipientaddresses(asaURI)42k.
Specifyanassertionoftheconfidentialitylevelofthecombinedpayloads.
4310.
Inaddition,theContentObjectelementcontainedwithintheDistributionElementSHOULD:44a.
AllowtheencapsulationofoneormorepayloadsineachoftheContentObjectelements.
45b.
Specifythefunctionalroleand/ortypeofthesenderofeachpayload46c.
Specifyoneormorefunctionalrolesand/ortypesofdesiredrecipientsofeachpayload47EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page9of42d.
Specifyanassertionoftheconfidentialitylevelofeachpayload.
111.
Provideorrefertospecificlists(enumerations)ofvaluesandtheirdefinitionsfor:2a.
Typesofincidents3b.
Typesofhazardsand/orevents4c.
Typesofagencies5d.
Typesofresponseactivity6e.
Thefunctionalroleand/ortypeofthesender7f.
Thefunctionalrolesand/ortypesofdesiredrecipients8g.
Theincidentnameorotheridentifierofoneormoreeventorincident.
92.
3ExampleUsageScenarios10Note:ThefollowingexamplesofusescenarioswereusedasabasisfordesignandreviewoftheEDXL11DistributionElementMessageformat.
Thesescenariosarenon-normativeandnotintendedtobe12exhaustiveortoreflectactualpractices.
132.
3.
1DistributionofEmergencyMessage/sorAlertsBasedonGeographic14DeliveryAreaandIncidentType15TheterroralertlevelhasbeenraisedtoRED.
Credibleintelligenceindicatesthatterroristgroupsinthe16Mid-Atlanticregionareseekingtoconductanattackinthenext48hours.
TheDepartmentofHomeland17Securitysendsanemergencyalertmessage,andusingtheDistributionElement,distributesittoall18emergencyagenciesinthespecifiedarea.
192.
3.
2EncapsulationandDistributionofOneorMoreEmergencyMessagesor20AlertsorNotifications21ARadiologicalsensortriggeredataprominentTunneltollbooth.
Radiationalarmlevelsindicates22possibledirtybomb.
Authoritiesdecidetosendmultiplemessagestoanumberofjurisdictions.
Theysend23anEDXLDistributionElementwithtwoencapsulatedCAPmessages.
Thefirstonenotifiesthearea24wherethesensorhasbeentriggered.
Thesecondoneisanalerttoemergencyresponseagenciesthat25thestateEmergencyOperationCenter(EOC)hasbeenactivated,andrequeststheagenciestobeon26alert.
272.
3.
3DistributionofResourceMessagesorReports28TheLocalEOChasaneedforadditionalresource/support,butisunsurewhatspecificallytorequest.
A29free-formrequestforinformationandresourceavailabilityisprepared,andissenttothestateEOCand30otherorganizations(persontoperson)usingtheDistributionElement.
TheLocalEOCreceivesan31acknowledgmentmessagefromtheStateEOC,aswellasarequestforInformationonadditionaldetails32oftherequestedresource.
BothofthesemessagesarecontainedwithinasingleDistributionElement.
332.
3.
4DistributionofWell-FormedXMLMessages34Ahugecrash,involvingacarandaHAZMATtruck,occursatabusyjunctiononaninter-statefreeway.
35SeparateautomaticnotificationsofboththecarcrashandtheHAZMATcarrieraresentusingthe36VehicularEmergencyDataSet(VEDS),containedintheDistributionElement.
TheTransportation37ManagementCenter(TMC)sharesinformation(relatedtotheaboveincident)withtheadjacentTMC,38usingtheIEEE1512IncidentManagementMessageSet.
Thesesetofmessagesareexchangedusing39theEDXLDistributionElement.
40EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page10of423.
EDXLDistributionElementStructure(normative)13.
1DocumentObjectModel2Boldindicatesrequiredelement.
3Italicsindicatesoneormoreoptionalunspecifiedelements4#indicatesconditionalrequirement5*indicatesmultipleinstancesallowed6EDXLDistributiondistributionIDsenderIDdateTimeSentdistributionStatusdistributionTypecombinedConfidentialitylanguagesenderRole*recipientRole*keyword*distributionReference*#explicitAddress*targetAreacircle*polygon*country*subdivision*locCodeUN*contentObjectcontentDescriptioncontentKeyword*incidentIDincidentDescriptionoriginatorRole*consumerRole*confidentialityother*nonXMLContentmimeTypesizedigesturicontentDataxmlContentkeyXMLContentembeddedXMLContent0.
.
*OR10.
.
*7EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page11of423.
2DataDictionary1Note:UnlessexplicitlyconstrainedwithinthisDataDictionary,EDXL-DEelementsMAYhavenullvalues.
2ImplementersMUSTcheckforthisconditionwhereveritmightaffectapplicationperformance.
33.
2.
1EDXLDistributionElementandSub-elements4TheDistributionMessageelement,isthecontainerelementforalldatanecessaryto5theoriginator'sintentastothedisseminationofthecontainedmessageorsetofmessages.
6ElementEDXLDistributionTypeXMLStructureUsageREQUIRED,MUSTbeusedonceandonlyonce,toplevelcontainerDefinitionThecontainerofalloftheelementsrelatedtothedistributionofthecontentmessages.
Comments1.
Theelementmayincludeoneormoreandblocks.
2.
Useoftheelementdoesnotguaranteethatallnetworklinksandnodeswillimplementtheasserteddisseminationpolicyorthatunintendeddisclosurewillnotoccur.
Wheresensitiveinformationistransmittedoveruntrustednetworks,itshouldbeencryptedinaccordancewiththeWebServicesSecurity(WSS)standard()withanyupdatesanderratapublishedbytheOASISWebServicesSecurityTechnicalCommittee(),orsomeothersuitableencryptionscheme.
Sub-elementsdistributionIDsenderIDdateTimeSentdistributionStatusdistributionTypecombindedConfidentialitylanguagesenderRolerecipientRolekeyworddistributionReferenceexplicitAddresstargetAreacontentObjectUsedIntoplevelelement7EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page12of421ElementdistributionIDTypexsd:stringUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionTheuniqueidentifierofthisdistributionmessage.
Comments1.
Uniquenessisassignedbythesendertobeuniqueforthatsender.
2.
TheidentifierMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution2ElementsenderIDTypexsd:stringUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionTheuniqueidentifierofthesender.
Comments1.
Uniquelyidentifieshumanparties,systems,services,ordevicesthatareallpotentialsendersofthedistributionmessage.
2.
Intheformactor@domain-name.
3.
Uniquenessofthedomain-nameisguaranteedthroughuseoftheInternetDomainNameSystem,anduniquenessoftheactornameenforcedbythedomainowner.
4.
TheidentifierMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:dispatcher@example.
gov,0006.
0e39.
ad80@example.
comUsedInEDXLDistribution3ElementdateTimeSentTypexsd:dateTimeUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionThedateandtimethedistributionmessagewassent.
Comments1.
TheDateTimecombinationmustincludetheoffsettimefortimezone.
2.
MustbeintheW3CformatfortheXML[dateTime]datatype.
Example:2004-08-01T16:49:00-07:00UsedInEDXLDistribution4EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page13of421ElementdistributionStatusTypexsd:stringwithrestrictionsUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionTheactionabilityofthemessage.
Comments1.
Valuemustbeoneof:a.
Actual-"Real-world"informationforactionb.
Exercise-Simulatedinformationforexerciseparticipantsc.
System-Messagesregardingorsupportingnetworkfunctionsd.
Test-Discardablemessagesfortechnicaltestingonly.
2.
ThestatusMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution2ElementdistributionTypeTypexsd:stringwithrestrictionsUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionThefunctionofthemessage.
Comments1.
Valuemustbeoneof:a.
Report-Newinformationregardinganincidentoractivityb.
Update-Updatedinformationsupersedingapreviousmessagec.
Cancel-Acancellationorrevocationofapreviousmessaged.
Request-Arequestforresources,informationoractione.
Response-Aresponsetoapreviousrequestf.
Dispatch-Acommitmentofresourcesorassistanceg.
Ack-Acknowledgmentofreceiptofanearliermessageh.
Error-Rejectionofanearliermessage(fortechnicalreasons)i.
SensorConfiguration-ThesemessagesareforreportingconfigurationduringpoweruporafterInstallationorMaintenance.
j.
SensorControl-Thesearemessagesusedtocontrolsensors/sensorconcentratorcomponentsbehavior.
k.
SensorStatus-Theseareconcisemessageswhichreportsensors/sensorconcentratorcomponentstatusorstateofhealth.
l.
SensorDetection-Thesearehighprioritymessageswhichreportsensordetections.
2.
Thedistributiontypeappliestothefunctionofthecontentobjectsasaset.
Thosecaseswherepayloadshavedifferentdistributiontypesshouldbeclusteredindifferentdistributionelements.
3.
ThetypeMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page14of42ElementcombindedConfidentialityTypexsd:stringUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionConfidentialityofthecombineddistributionmessage'scontent.
Comments1.
Theindicatestheconfidentialityofthecombinedsub-elements.
Generallythecombinedconfidentialityisthemostrestrictiveoftheelementsinthecontainerelement,butitcanbemorerestrictivethananyoftheindividualelements.
2.
TheelementMUSTbepresentifaelementispresentinanyoftheelements.
3.
Applicationspecificmechanismswillberequiredtodeterminetheminimumconfidentialitylevelincaseswheredifferentconfidentialityschemesareusedinthe.
4.
Defaultvalue"UNCLASSIFIEDANDNOTSENSITIVE"5.
TheconfidentialityMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution1ElementlanguageTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionTheprimarylanguage(butnotnecessarilyexclusive)usedinthepayloads.
Comments1.
ValidlanguagevaluesaresuppliedintheISOstandard[RFC3066].
2.
ThelanguageMUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:FR,ENUsedInEDXLDistribution2EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page15of421ElementsenderRoleTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThefunctionalroleofthesender,asitmaydeterminemessageroutingdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Sub-elementsvalueListUrnvalueUsedInEDXLDistribution2EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page16of421ElementrecipientRoleTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThefunctionalroleoftherecipient,asitmaydeterminemessageroutingdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Sub-elementsvalueListUrnvalueUsedInEDXLDistribution2EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page17of421ElementkeywordTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThetopicrelatedtothedistributionmessage,asitmaydeterminemessageroutingdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
4.
Examplesofthingsmightbeusedtodescribeincludeeventtype,eventetiology,incidentIDandresponsetype.
Sub-elementsvalueListUrnvalueUsedInEDXLDistribution2ElementdistributionReferenceTypexsd:stringUsageCONDITIONAL,MAYusemultipleDefinitionAreferencetoapreviousdistributionmessage.
Comments1.
Theandandofthereferencedpreviousmessage,concatenatedwithacommadelimiter.
2.
Thiselementshouldappearatleastonceinanymessagewhichupdates,cancelsorotherwisereferstoanothermessage.
3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Example:msgID0074,actor@domain-name,2004-08-01T16:49:00-07:00UsedInEDXLDistribution3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page18of421ElementexplicitAddressTypeXMLStructureUsageOPTIONAL,MAYusemultipleDefinitionTheidentifierofanexplicitrecipient.
Comments1.
Identifieshumanparties,systems,services,ordevicesthatareallpotentialrecipientsofthedistributionmessage.
2.
Theexplicitaddressofarecipientintheform:explicitAddressSchemeexplicitAddressValuewherethecontentofisthedistributionaddressingschemeused,andthecontentofisastringdenotingtheaddresseesvalue.
3.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
4.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Sub-elementsexplicitAddressSchemeexplicitAddressValueUsedInEDXLDistribution3.
2.
2targetAreaElementandSub-elements2Theisacontainerelementforthegeospatialorpoliticalareatargetingofthemessage3content.
Itindicatestheoriginator'sintentbasedonlocationtargetingastothedisseminationofthat4particularmessageorsetofmessages.
5GeospatialNote:6Valuesforlatitudeandlongitudeshallbeexpressedasdecimalfractionsofdegrees.
Whole7degreesoflatitudeshallberepresentedbyadecimalnumberrangingfrom0through90.
Whole8degreesoflongitudeshallberepresentedbyadecimalnumberrangingfrom0through180.
9Whenadecimalfractionofadegreeisspecified,itshallbeseparatedfromthewholenumberof10degreesbyadecimalpoint(theperiodcharacter,".
").
Decimalfractionsofadegreeshouldbe11expressedtotheprecisionavailable,withtrailingzeroesbeingusedasplaceholdersifrequired.
12Adecimalpointisoptionalwheretheprecisionislessthanonedegree.
13Someeffortshouldbemadetopreservetheapparentprecisionwhenconvertingfrom14anotherdatumorrepresentation,forexample41degrees13minutesshouldberepresentedas1541.
22andnot41.
21666,while4113'11"mayberepresentedas41.
2197.
16LatitudesnorthoftheequatorMAYbespecifiedbyaplussign(+),orbytheabsenceofaminus17sign(-),precedingthedesignatingdegrees.
LatitudessouthoftheEquatorMUSTbedesignated18byaminussign(-)precedingthedigitsdesignatingdegrees.
LatitudesontheEquatorMUSTbe19designatedbyalatitudevalueof0.
20EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page19of42Longitudeseastoftheprimemeridianshallbespecifiedbyaplussign(+),orbytheabsenceofa1minussign(-),precedingthedesignatingdegrees.
LongitudeswestoftheprimemeridianMUST2bedesignatedbyaminussign(-)precedingthedigitsdesignatingdegrees.
Longitudesonthe3primemeridianMUSTbedesignatedbyalongitudevalueof0.
Apointonthe180thmeridian4shallbetakenas180degreesWest,andshallincludeaminussign.
5ElementtargetAreaTypeXMLStructureUsageOPTIONAL,MAYusemultipleDefinitionThecontainerelementforlocationinformation.
Comments1.
Multipleblocksmayappearinasingleelement,inwhichcasethetargetareaforthecurrentmessageistheunionofallareasdescribedinthevariousstructures.
Sub-elementscirclepolygoncountrysubdivisionlocCodeUNUsedInEDXLDistribution6ElementcircleTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionAnenclosedgeographicareawithinagivenradiusaroundageographicpoint.
Comments1.
Representedintheform"latitude,longitude,radius".
(SeeGeospatialNoteabove)2.
Thecentralpointisrepresentedbylat-longvaluesconformingtotheWGS84coordinatereferencesystem.
[WGS84]3.
Theradiusvalueisexpressedinkilometers.
4.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Example:38.
26295,-122.
0745415UsedIntargetArea7EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page20of421ElementpolygonTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionAnenclosedgeographicareawithinasimpleclosedpolygondefinedbyanorderedsetofvertices.
Comments1.
Representedbyaspace-delimitedseriesoflatitude,longitudepairs,withthelastpairidenticaltothefirst.
(SeeGeospatialNoteabove)2.
Thelat-longvaluesconformtotheWGS84coordinatereferencesystem.
[WGS84]3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Example:42,-124.
210242,-120.
139,-12035.
0,-114.
632834.
35,-120.
441838.
9383,-123.
81742,-124.
2102UsedIntargetArea2ElementcountryTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionThecodeofthecountry.
Comments1.
Thetwo-characterISO3166-1CountryCodeforthecountryconcerned.
2.
Morespecifictargetlocationinformationcanbedefinedintheelements.
3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedIntargetArea3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page21of421ElementsubdivisionTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionTheISO3166-2designatorfortheadministrativesubdivisionconcerned.
Comments1.
Thefirsttwocharacters,beforethehyphen,arethetwocharacterISO3166-1CountryCodeforthecountrywithinwhichthedesignatedsubdivisionislocated.
2.
Thefollowingone-to-threecharactersfollowingthehyphendesignatetheparticularsubdivision.
3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:US-TX(U.
S.
StateofTexas),DK-025(DanishcountyRoskilde),MG-T(Antananarivoprovince,Madagascar)UsedIntargetArea2ElementlocCodeUNTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionTheUN/LOCODEdesignatorforthelocationconcerned.
Comments1.
ThetwofirstdigitsarethetwocharacterISO3166-1CountryCodeforthecountryinwhichtheplaceislocated.
2.
ThefollowingthreecharactersaretheUN/LOCODEdesignatorfortheparticularlocationwithinthatcountry.
3.
Nospacesorpunctuationareusedwithinthisdesignator.
4.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Example:USFFB(Fairfield,Alabama,USA),USSUU(Fairfield,California,USA),GBFFD(Falfield,SouthGloucestershire,UK)UsedIntargetArea33.
2.
3contentObjectElementandSub-elements4Theelementisthecontainerelementforspecificmessages.
The5elementMUSTeithercontainancontentcontaineroracontent6container.
Additionalelements(metadata)usedforspecificdistributionofthepayloador7hintsforprocessingthepayloadarealsopresentinthecontainerelement.
8EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page22of421ElementcontentObjectTypeXMLStructureUsageOPTIONAL,MAYusemultipleDefinitionThecontainerelementformessagedataandcontent.
Comments1.
Theisthecontainerelementforspecificmessages.
2.
Themayhaveanoptionalattributethatdefinesanamespaceprefixwhichresolvesambiguouselementnames.
3.
TheelementMUSTcontainexactlyoneofthetwocontentformats:a.
,forvalidnamespacedXMLcontentorb.
,containingoneorbothoftheelements,forreferencetothecontent'slocation,and,fordataencapsulatedinthemessage.
Sub-elementscontentDescriptioncontentKeywordincidentIDincidentDescriptionoriginatorRoleconsumerRoleconfidentialitynonXMLContentxmlContentUsedInEDXLDistribution2ElementcontentDescriptionTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThehuman-readabletextdescribingthecontentobject.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:"CAPmessagefromFEMA","Mapofaffectedarea"or"Photoofmissingchild".
UsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page23of421ElementcontentKeywordTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThetopicrelatedtothemessagedataandcontent,asitmaydeterminemessagedistributionandpresentationdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Examplesofthingsmightbeusedtodescribeincludemessageprocessor,eventstage,resourcecodeandresponsetype.
Sub-elementsvalueListUrnvalueUsedIncontentObject2ElementincidentIDTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThehuman-readabletextuniquelyidentifyingtheincident/event/situationassociatedwiththecontentObject.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page24of421ElementincidentDescriptionTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThehuman-readabletextdescribingtheincident/event/situationassociatedwiththecontentObject.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedIncontentObject2ElementoriginatorRoleTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThefunctionalroleofthemessageoriginator,asitmaydeterminemessagedistributionandpresentationdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Sub-elementsvalueListUrnvalueUsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page25of421ElementconsumerRoleTypeListandAssociatedValue(s)UsageOPTIONAL,MAYusemultipleDefinitionThefunctionalroleofthemessageconsumer,asitmaydeterminemessagedistributionandpresentationdecisions.
Comments1.
Thelistandassociatedvalue(s)isintheform:valueListUrnvaluewherethecontentofistheUniformResourceNameofapublishedlistofvaluesanddefinitions,andthecontentofisastring(whichmayrepresentanumber)denotingthevalueitself.
2.
Multipleinstancesofthe,MAYoccurwithasinglewithinthecontainer.
3.
MultipleinstancesofMAYoccurwithinasinglecontainer.
Example:"http://www.
dhs.
gov/NiemRoleType",ICSOperationsBranchSub-elementsvalueListUrnvalueUsedIncontentObject2ElementconfidentialityTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionSpecialrequirementsregardingconfidentialityofthecontentofthis.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page26of421ElementotherTypexsd:otherUsageOPTIONAL,MAYbeusetoaddanunlimitednumberofXMLelementsforenvelopedsigningprocess.
DefinitionSpecialrequirementsallowingforsignatureofthecontentofa.
Comments1.
Thereisnomandatoryvalidationoftheelementsifthenamespacereferencecannotbelocated.
2.
MUSTbeaproperlyformedXMLstring–escaped,ifnecessary.
3.
ElementnamescannotduplicateotherelementnamesinthecontentObject.
Suchduplicationwouldpreventvalidationduetotheambiguityintroduced.
4.
Thiselementmaybeusedforsignatures.
Ifthiselementisusedforexperimentalextensions,suchextensionsmaynotbesupportedbyallusersorinfutureversionsofEDXL-DE.
UsedIncontentObject3.
2.
4nonXMLContentElementandSub-elements2ElementnonXMLContentTypeXMLStructureUsageCONDITIONAL,MUSTuseonceifxmlContentisnotusedDefinitionContainerforcontentprovidedinanon-XMLMIMEtype.
Comments1.
ThecontainerMUSThaveoneorbothoftheelementsand.
2.
Iftheelementisusedinconjunctionwiththeelement,itmustreferenceadatalocationthatcontainsthesamedataasiscontainedintheelement.
Sub-elementsmimeTypesizedigesturicontentDataUsedIncontentObject3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page27of421ElementmimeTypeTypexsd:stringUsageREQUIRED,MUSTbeusedonceandonlyonceDefinitionTheformatofthepayload.
Comments1.
MIMEcontenttypeandsub-typeasdescribedin[RFC2046].
2.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examples:application/pdf,application/mp3UsedInnonXMLContent2ElementsizeTypexsd:integerUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThefilesizeofthepayload.
Comments1.
Valuemustbeinbytesandrepresenttherawfilesize(notencodedorencrypted).
UsedInnonXMLContent3ElementdigestTypexsd:stringUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThedigestvalueforthepayload.
Comments1.
Usedtoensuretheintegrityofthepayload.
2.
CalculatedusingtheSecureHashAlgorithm(SHA-1)3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInnonXMLContent4EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page28of421ElementuriTypexsd:anyURIUsageOPTIONAL,MAYuseonceandonlyonceDefinitionAUniformResourceIdentifierthatcanbeusedtoretrievetheidentifiedresource.
Comments1.
MaybeafullabsoluteURI,typicallyaUniformResourceLocator,thatcanbeusedtoretrievetheresourceovertheInternet.
2.
MaybearelativeURInamingafile.
Thismaybejustapointertoafileorspecificallytothefilerepresentedinthe.
UsedInnonXMLContent2ElementcontentDataTypexsd:base64BinaryUsageOPTIONAL,MAYuseonceandonlyonceDefinitionThebase-64encodeddatacontent.
Comments1.
MAYbeusedeitherwithorinsteadoftheelementincontextswhereretrievalofaresourceviaaURIisnotfeasible.
2.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInnonXMLContent3.
2.
5xmlContentElementandSub-elements3ElementxmlContentTypeXMLStructureUsageCONDITIONAL,MUSTuseonceifnonXMLContentisnotusedDefinitionContainerforvalid-namespacedXMLdata.
Sub-elements1.
keyXMLContent2.
embeddedXMLContent3.
Anoptionalnamespaceattributemaybeincluded.
UsedIncontentObject4EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page29of421ElementkeyXMLContentTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionAcontainerelementforcollectedfragmentsofvalidXML.
Comments1.
ExtractsmustcomefromtheXMLdocumentcontainedwithintheelementwithinthecurrentblock.
2.
AllcontentwithinthiselementMUSTbeexplicitlynamespacedasdefinedintheenclosingtag.
3.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInxmlContent2ElementembeddedXMLContentTypexsd:stringUsageOPTIONAL,MAYusemultipleDefinitionTheelementisanopencontainerforvalidXMLfromanexplicitnamespacedXMLSchema.
Comments1.
ThecontentMUSTbeaseparately-namespacedwell-formedXMLdocument.
2.
TheenclosedXMLcontentMUSTbeexplicitlynamespacedasdefinedintheenclosingtag.
3.
EnclosedXMLcontentmaybeencryptedand/orsignedwithinthiselement.
UsedInxmlContent3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page30of423.
2.
6ListandAssociatedValue(s)1ElementvalueListUrnTypexsd:stringUsageCONDITIONAL,MAYuseonceandonlyonceDefinitionThenameofacertifiedlistmaintainedbytheCommunityofInterest(COI)forthevaluereferenced.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution/senderRoleEDXLDistribution/recipientRoleEDXLDistribution/keywordcontentObject/contentKeywordcontentObject/originatorRolecontentObject/consumerRole2ElementvalueTypexsd:stringUsageCONDITIONAL,MAYusemultipleDefinitionAvaluefromacertifiedlistmaintainedbytheCommunityofInterest(COI)forthereferencedelement.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInEDXLDistribution/senderRoleEDXLDistribution/recipientRoleEDXLDistribution/keywordcontentObject/contentKeywordcontentObject/originatorRolecontentObject/consumerRole3EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page31of423.
2.
7ExplicitAddressing1ElementexplicitAddressSchemeTypexsd:stringUsageREQUIRED,MUSTuseonceandonlyonceDefinitionIdentifiesthedistributionaddressingschemeused.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
Examplesforthistypeofdistributionincludes-email,militaryUSMTF,etc.
.
.
UsedInexplicitAddress2ElementexplicitAddressValueTypexsd:stringUsageREQUIRED,MAYusemultipleDefinitionAproperlyformed-escapedifnecessary-XMLstringdenotingtheaddresseesvalue.
Comments1.
MUSTbeaproperlyformed-escapedifnecessary-XMLstring.
UsedInexplicitAddressEDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page32of42AppendixA.
XMLSchemafortheEDXLDistribution1Element23489101112131415161718192123252729313334353637383940414244454648EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page33of42234567891112131415161718192021222324252627293132333435363738394041424344454647484950EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page34of421245678911131517192021222324252627282930313233343536373839404142434445464748EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page35of42AppendixB.
EDXL-DEExamples1B.
1EDXL-DEWithCAPPayload2ThefollowingisaspeculativeexampleintheformofanEDXL-DEXMLmessage.
34ieam_e3_25XML200562005-11-15T16:53:00-05:007Exercise8Update910http://www.
niem.
gov/EventTypeList11Explosion12131433.
4745,-112.
117433.
4745,-112.
023833.
4238,-112.
023833.
4238,-112.
117433.
4745,-15112.
1174161718CAPmessagefromDOTadvisingbestalternateRoutes1920212223Vendorgenerated24AZDOT252005-11-15T16:58:00-05:0026Exercise27Update28Public2930Transport31TrafficRoutes32Immediate33Moderate34Likely35TrafficadjustmentsensureclearroutestoSt.
JosephsHospital36andPhoenixChildrensHospitalonThomasRd.
3738BestRoutes3938.
91655012246089,-77.
0201626794340738.
91655012246089,-4077.
011709839116538.
907662564641285,-77.
011709839116538.
907662564641285,-77.
020162679434074138.
91655012246089,-77.
0201626794340742434445464748495051EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page36of42B.
2EDXL-DEWithMultipleEncryptedPayloads1ThefollowingisaspeculativeexampleintheformofanEDXL-DEXMLmessage.
234Sandia0015dellis@sandia.
gov62005-08-07T18:05:00-07:007Actual8Report910urn:sandia:gov:sensors:senderRole11SENTRYsensormanagmentsystem1213isrepeatedthreetimes,sinceWarningandreporting16systemswantCAPcontent,HazardPredictionsystemswantdetailedsensor17outputs,andsituationalawarenesssystemswantthelocationandtypeofevent.
18-->1920urn:sandia:gov:sensors:reciepentRole21WarningandReportingDevices22HazardPredictionapplications23SituationalAwarnessapplications24252629containerelements.
30-->313233urn:sandia:gov:sensors:keywords34SNMDetection3536374243DMISCOGs44173445352046474849e-mail50dellis@sandia.
gov51525357Unclassified5859elementswouldbepresent.
-->606164US65California66EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page37of42USA-SF123containerelements.
11-->1213isaddedtoallowreferencingbetweens-->1415"urn:sandia:gov:sensor:detection.
event.
id"1610.
2.
2.
1:2005-08-07T18:00:00Z1718wouldhavetobetransformedinCAP1.
1toCAP1.
021Conversions22-->23Unclassified242526282930deskey.
bin313233GSCinwYBtwJxp6kcZPGqE6rybCfsnvI6Lz+IZVPqnRfnI1hWq7cI2WT4BsjBBQCu34TE68pCQ/keOGtvYJ5yNVZEuAnIhOf37OEiqk1rcBARXb03LCYvlXYKA1zmEC5yFT35CUcyCMV146G4eNU1H7F+wbMjbSgHjOYgYe+rpjOVYAK9Gs4Uj+CWhijjxpr5Y/vX361NEtHFhLsXC9cSfhXWVmi3veXwbDycC+QtcvQL/Rfr45bDwsJnCCutTzfmoqF1CS37BgYUi6osW+XhoRkAttzKbRADVZ6bG5SMkZN0SKiwSaCyKyMKjdpiQwYQhjUXUoAn38veBylXREqfmtOIm/pT7Y45pabWNG9l3aljil8P7qZ5Y26Q0X+i0U+eEGuafHrMVb39S/QBpAkNbP5/f9UR3B4t5t7hLOsvDXdR6CWFBNsrczLjZ7YC2O+g1HBl8YsQdREA40And3PKgoy8QlKv6ZLA+aJzQpSvzbSu3btgN6vyF3GGPqKprVIYRFouaJHYgL81zn41zZovnH4lubwa+YPgD0H48a/FM2LaA8euPzMFDWIki0fm5DoZZzYCmPKmfLJS10RG42lUKzW0svDw8I1AwX6LBssPm+hoBa7HzTnuM40FD+vsmET+p0bqBtaUSnDHrHXLzp43P6TrcNr5R5cxQ4C+shwezFQDNKbioyC6m5PaTH/6qhlTmE32vP8ySnMKvL74QCfP44w8hTZxwq9UVLPq2WKJcI0Phc1e3HoYkBTpVk9OUf/CVaxMXGOiXReeLXGPC1IQnn45a6xw7ImkgeCFcY+rcttq2fE3UqWtc5R6J16/Jv666K9fgCbXRVhaBdMDYpz0GKFa46gMJulUK6zTtah+bidtUrF31UWAX+wqIqmDFJ1ivJaRbLEiEVCrt0jKwOjuR41dDD47VS5j2BuvmZ5TILnOnHFU6H4GudnwjpL01eLrwELSfKmbQmUx2A0L6NBj9SRkXXHW48onZV6uX+c3CR46OekvxYyMi1rxE2zQPykfh/mELRhGgyDVqtdFQwhDx2Klu+Gh2z493nC51yn37laIO5KSvL5Gkb6jxFVrcUvrcp4pX5czw7/VWbxWoRPY7Bus3akhPu+I50/jchv7SiVRP5mX4Ewh+yeduYX+UZLo07m5zhAMtmFdiLJV9tgHVTJf7ZJ3bGWP+h51Et0Nl98hGV362cSRhkoLJwNmOgIpGXSMO6T5nA1MZhJ6CkCP8QV1zpKrLVJSRZRn52fffBjdl8CzipzjE05JVKbyfbq9I33fkWMbda+Vo9ZMiDinOee6KxnDnxll9ca9Lg53+dl9J0qjJz5VwnWLRCeprsOXt+LlmeHC60NJgRarhidlrfuxmONM+QZTk4ZQGIPD54fsk5ftJtzvHgW5G/wN7fxyLh1AqQucW13IAsmfwuJS0+HntYZVoXqGjRg1sK6snx55zteJJm6a2OyG/M5RvLAEVhOKWyU2+9hjzts8ySg6Qb2+KrUTRQ8JBmVBeSjR2svv562AWyBYj29JAdAikX9gfGDDvTG9GqJr+jFE9mfOBtg7lsdLezQKvvNMsntm6RdSpu57dA3vL8uBIliGBNJZSOOKr06BXp6PjbL6Ov47EbOfvP8Vm9vKQD7PmjPaIbN1bUr958V9cHUQ5h6LSecnAy/FZQMLdcamNAIhpiEgoQcwEmaa+1/wTv7LppqxZkFVQQbI2m59nC9Ujcd08g2Qyh+0YCHP50SbCwDe2W+CYBi7QBDdF3qt45zaZnHyRm/yXhVWCJX160+0WY/+OukquhaWJ8Y0fygA1yk7Jyqqpu2XU9X0Vu8oETQlL/+37mEzy/beL9VNnr61eU7bfQBAnYw1CkeXs5rAcc1vllZEU22Uqg3H5saOQlEHgV1NxL+0C+A9/Q2ZsaFI62BDDIiH+f6+6aUno6fotGUA==636465666768697071EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page38of4212345przigAg811cHIqSXpIrFg1BGx20=678BH8MGSS9QAlgq7a7I7PF5XjKsqaDumTt3cSWxBmwErByvQuaarOgH6MMflVLkG0Y9tv6zaOqR6Kis4giTqtZBo8QCkGukpre2gurdi3Ws0yO3Wt8nWrcH3QAUllhocXpV10gXahZ8MzHc9zuJq9+bl+S72czTjS0UdCvk/MMRV/xhwZ/1QSn+ffh0s3RU6Cn1Q011aYSuDtX5mAGUWAzJghKgK/qSM5jF4c233g7M4m+Rul3C+QOFBOMGmp+NodnG9b0z12hycJGVdUpY0a+1r0quu2pmdLZnIQVY1stWNFS3wI9RzdslwzoGP9/nRARGS0kLf113De+WB4Xdar48A9WJwng0iA==1415rsakey.
pem161718242526"urn:sandia:gov:sensor:detection.
event.
id"2710.
2.
2.
1:2005-08-07T18:00:00Z2829Unclassified303132343536deskey.
bin373839MiKRUfL1Yb3Vw9JcewTAYVnYT3Zh2Tf9d0fhRyGreJW0FWoXr1/27AXFXBTmZC/240hw9cMMFaGKeXNr1tK0Os1Lozx9uZZYoF5UiNH18KD/WnNbpwk+ttK3TwRcxBfowm41lzzClMn5suHeUM2PFiCll1Wup8cSfwAqptXVF3sZrLAMsQWJmGfyGYYCiaZ+P3NZ42hiVFamDB7D9id5HJ3qHLNcxucGNFA5TfOwe/euP7O1ah9Q7Rp2nxsXF9PaQYziSS43G4I/J+v+FwuJXhbLqU1PcbP4ofCLg+s6tph2kJxFArGSX9u3k7FHvp3tLZnskXCw44iYRGDqrSGrmLt7bTtMmF/IhFQc4x0aE4ldVEN999uQ6KnDyd22KdUJhupRH8UqZz45+sKVJF3+yatOsroCwOCjTe/GqnNRZNtG59dGC5D247LH2AVn/6WU+txFflZhUg0z46A0PElIMicguTRaEaIDGJF/QvqzTE1r3iYgHXIGfgEhQiix35ZURWUTcATrKyNFFE47/CD8+v6YHGbKrgeJDnvJ5AqjZSU1NajOpCtbhWQm1D878OhjCN+T689PZPB2X2nz48f1kupkZ/Fq6Z6aF77j0xp4wB7bpFW5ssWUHySwdg5vYw4hS3Geg5wn3AQViqTGI849oRaDa3wT9byHq+cq83WqA3aroJOXzD/HQCmKNhmPFqYj503JH3aZcWNrDxHyBQRr50Libv4o9v4LCGviaKT/2y0S25t5KkL/MJA2c6LIngmhHKQFr1sruWgSrjHn9KtagU51KeYqYlgKK6s56X+PHQvusXoxpgDLjXpVVhNpF/mRh+86J4zY3JAIcfIZJQ05DjvX52io2iZY/hstzkTfY5+CPvKH7FmuYqeoU7Nano7+EGSB4w0TnSoDfm9D/RIsAtwdpu537WonmeguEK37u0bNuXQHi9LZTELD0L2HIkPVdo4BYq26WMe5vZdwVkW6up92AIQE547KvADQZZUGDVoKA3Njt9O5s6g+a14wcHqxD+FS8veacDsYFrmhs+0WYlyWtDJERL55+y0qtHLmSi/kTdYoKRGx+/lyUl8FIfqOnk2dk3BicbQ3kyEbngV3qHBrYqrVITTB56eMUKxL3wB5OkcCn3u6Nqun14QFmf8O9KEZGXZZqdQs7jz6MV3yjPvzelmLs9nbCm573eXFGrSlHbbwCLQBconzDWgfoN6W/lTRv3z8RmTg+Z+3CjK2MRt6x5XZTcDqk4JW58wozh2btLz4Yc2xUbclbtVd3muOhBq3eSsGXC6xX4fxW0cuqi6UsOZRA2kiKJHY+V592KFO9/y3x4arscIsBwfmNVZYt6bCoy/Or0yva49yV/A//8JFN7aGLh530Dt53J4H60bcsQ1n3q7kxir5VLuNj0aZYHjtGu7gzPa1UpPAJ0trqro4qinspnkdRueW7SQYcd61ufF5OG4GMTI+VjX4MnOMOgnYiAaZqrBoH3B5t7bAKeszVPs6S9NPfkzx1nkqminG62/Z/hBpmsFlcUlS+qylXU7umHvssE2juap1NQUaL6IyHQ0tZzsQd0e6mYkDuzNNbH634l9czPXXXfvcKRJnJ0Yho9j30YfBWyllF67SMewYhcNg35tAbstXe+Ghg+D/TVcd64SZ4r1Cmk49IQE3SNwIO6vGUtMhmCJGq+yJx89lfMLijZRBr18exdQ1hoVeQ+YzyY65rZ/e6PTZHVkbcHGLsd+InyBdz3MTCmaYLGGG6gGtL42nJYmXDUIwWTAFXcWo0jDh66HO28OimZg8QGhiSAAc8uXzwbtjVHIJTC27e6iqldNxnYDoNWDZxVjI3fccbvUwmz67702I+4Kb/n5M1X5RXeMZ12OvlRRnQi7nhZuTeTMEbRizHptWP5yse3LcNjRJ2Jr268697071EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page39of4212345678910N7NvgXfahdGZPjb9o0XvwejLI5o=111213Tg8zP+/1Cg/3MR9iSareJb7snexQ3DjBxGSL3xH+Kf3Kh5NQq/Uwagw/fmI2wcxc14ac/2fz893HeTkXGn8mShg+wmdoRwNykp5uHPtAzcFBKlh3v7FemtM9M73XbX7KsY15fM0J+RTHUxp4tTMYUPogSEJWiSGSGVbp+MALtUH799fGqqqOREyuljfVIlLvvCog16wOd6n7J8S2sHjyRXEw5AVFnxL6k02TgjztbEuoLu+qvEZOIGXmj9yfy4nj41RNXe17HMOS1IAcOQgx5vNzju2slFIWzlmvjqq+7aVg5hy0yBiXJuljvigTOxrwHScaYW8o18HDpQHwM6EXbgW3uaWnf9Kg==1920rsakey.
pem21222324PhotoimagefromSensor:RADDET-01,Site:GoldenGateBridge,havinga25DetectionclassofSNM2627"urn:sandia:gov:sensor:detection.
event.
id"2810.
2.
2.
1:2005-08-07T18:00:00Z2930Unclassified3132image/jpeg33http://sentry/photoCapture/10.
2.
2.
1:2005-08-07T18:00:00Z3435363738394041424344io7Katgoo77YNfQYdZMB8taoeKg=454647AjQXGgp9h5TC2D+bh9w59sbmtUpgE/IeZVdDQM+zi58XT2RPb7OXAAABni78WduA48uP6nxL6k+BBo4G+TgaqWvCQIqdlDO+qyMnM0ExPui5eg00jstbwiSeYxSt2VQqS249RD2vR811at0XwIkMpugSftKNJBZgB9mhRqQgP+E0nDJJPNYDz0bLJjp0J/EDxn4H506qx6GpDKgDc//53jVhOb4zZPIERsTLjPxpOOnBK31cs5Rf6vU9MyOOBTHZgpvoza51muhejW1CIJfYjd/OoKQ9Hiv4MCX4v/dX7n6ePHZaDxNeCccDIjoVYrAHEWxQ9hE652rqriugNLZ3Lh8sUzhZLTyg==5354rsakey.
pem5556576162PhotoimagefromSensor:RADDET-01,Site:GoldenGateBridge,havinga63DetectionclassofSNM6465"urn:sandia:gov:sensor:detection.
event.
id"6610.
2.
2.
1:2005-08-07T18:00:00Z6768Unclassified6970image/jpeg71EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page40of421/9j//gAoaAkAAAAAAECMWv/mOzNdGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD/2wBDAAgGBgcGBQgH2BwcJCQgKDBQNDAsLDBkSEw8UHRofHh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/3AYG3nGaeEI5BoACp6gmmgKwOBzQBFICRUZXIwOKAE8sjmms5Uc0AU5JwTioxLjpQBHIc5qpJQBGr4YNSgjFACbuacQCtAEIXDVOOlACgUuAaAG4xVbUP+Qdc/9czQB//Z5678910111213141516PkrjafcKUd027EETVu5JwqlubcA=171819NvqlkBLs4GpM+t+uoWQ53rmjNT43qdwbMsEoiB0a2BRwqkmynKQDbA2eIHmxfBfo20xe+q+15v/2IGQQw+5XmWtMx8QIQkGBElSdlybOKibxBqNuWH+J6yR1mIA6bOmBE+21+F2zA9DuvKZVLa8El1pUGke6FeIzoMC7TdDcBtmSAkRMXxe8MjxjxApM3vnMSt9A22iCo2EUx4qYf82iJ9FX7vIFFfL2QW38RvZqY+rjXsHV5OK3fkTPFI+ZE5lIrHKjb323gu409JrdNtSy/wLd/WLypiYFNDZXxT6i5wBbdAvBkQ0jHECOJjfN+h1bHkvT4wLX24Cpc26QQ6Ic3goSLojC3rjw==2526rsakey.
pem272829373839EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page41of42AppendixC.
Acknowledgments1C.
1OASISEmergencyManagementTechnicalCommittee:2PattiAymond,IEM3ArtBotterell,Individual4RexBrooks,HumanMarkup.
org,Inc.
5LenBullard,Individual6MarkCarlson,Conneva,Inc.
7EliotChristian,USDepartmentoftheInterior8JamesBryceClark,OASIS9RobinCover,OASIS10DavidDanko,ESRI11SukumarDwarkanath,Individual12David,Ellis,Individual13JackFox,USDepartmentofHomelandSecurity14TimGrapes,ScienceApplicationsInternationalCorporation15GaryHam,DisasterManagementInteroperabilityServices16AdamHocek,Individual17TravisHubbard,DisasterManagementInteroperabilityServices18RenatoIannella,NICTA19ElysaJones,WarningSystems,Inc.
20JeffKyser,WarningSystems,Inc.
21MaryMcRae,OASIS22TomMerkle,LockheedMartin23GaryPoindexter,Individual24MichelleRaymond,Individual25CarlReed,OpenGISConsortium(OGC)26JuliaRidgely,Individual27EleanorRobinson,AnteonCorporation28KwasiSpeede,AnteonCorporation29AaronTemin,Individual30LeeTincher,ScienceApplicationsInternationalCorporation31BrettTrusko,OASIS32RichardVandame,USDepartmentofHomelandSecurity33SylviaWebb,Individual34KonstantinWilms,Individual35EDXL-DE1.
0OASISStandard1May2006CopyrightOASISOpen2006.
AllRightsReserved.
Page42of42AppendixD.
RevisionHistory12RevisionDateEditorChangesMade3
- pdfnano7相关文档
- 深圳市富满电子集团股份有限公司
- 深圳市富满电子集团股份有限公司
- HCXnano7
- 深圳市富满电子集团股份有限公司
- 拆解iPod nano7拆解
- nano7买了个nano7是不是白买了？他们都说不好
腾讯云CVM云服务器大硬盘方案400GB和800GB数据盘方案
最近看到群里的不少网友在搭建大数据内容网站，内容量有百万篇幅，包括图片可能有超过50GB，如果一台服务器有需要多个站点的话，那肯定默认的服务器50GB存储空间是不够用的。如果单独在购买数据盘会成本提高不少。这里我们看到腾讯云促销活动中有2款带大数据盘的套餐还是比较实惠的，一台是400GB数据盘，一台是800GB数据盘，适合他们的大数据网站。 直达链接 - 腾讯云 大数据盘套餐服务器这里我们看到当前...
ZJI：520元/月香港服务器-2*E5-2630L/32GB/480G SSD/30M带宽/2IP
ZJI发布了一款7月份特别促销独立服务器：香港邦联四型，提供65折优惠码，限量30台(每用户限购1台)，优惠后每月520元起。ZJI是原来Wordpress圈知名主机商家：维翔主机，成立于2011年，2018年9月启用新域名ZJI，提供中国香港、台湾、日本、美国独立服务器(自营/数据中心直营)租用及VDS、虚拟主机空间、域名注册等业务。下面列出这款服务器的配置信息。香港邦联四型CPU：2*E5-2...
Dynadot多种后缀优惠域名优惠码 ，.COM域名注册$6.99
Dynadot 是一家非常靠谱的域名注册商家，老唐也从来不会掩饰对其的喜爱，目前我个人大部分域名都在 Dynadot，还有一小部分在 NameCheap 和腾讯云。本文分享一下 Dynadot 最新域名优惠码，包括 .COM，.NET 等主流后缀的优惠码，以及一些新顶级后缀的优惠。对于域名优惠，NameCheap 的新后缀促销比较多，而 Dynadot 则是对于主流后缀的促销比较多，所以可以各取所...
nano7为你推荐
-
海外虚拟主机空间有免费的性能好的国外虚拟主机空间吗？php虚拟主机如何选择PHP网站虚拟主机免费com域名注册有没有永久免费的.com之类的域名广东虚拟主机如果营业执照上的注册地址是属于广东地区对客户的虚拟主机或者域名的地有没有限制？网络服务器租用服务器租用 使用方法vps主机vps主机用途有哪些?域名主机域名和主机名之间的区别是什么网站空间域名网站制作 域名和空间台湾主机台湾版本的主机好不好？山东虚拟主机山东东营制作网站的公司在哪里？