Organization for the Organization for the Advancement of Structured Advancement of Structured Information Standards Information Standards (OASIS) (OASIS) www.oasis-open.org www.oasis-open.org Elysa Jones, Chair Elysa Jones, Chair Emergency Management Technical Emergency Management Technical Committee Committee ejones@warningsystems.com ejones@warningsystems.com Rev. 10-19-2006
OASIS Overview OASIS Overview � Introduction � Introduction � Committee Process � Committee Process � Emergency Management Technical � Emergency Management Technical Committee Committee � Current Standards � Current Standards � Work in Progress � Work in Progress � Example � Example
Introduction Introduction � OASIS is an international body � OASIS is an international body � Standards are free and open � Standards are free and open � OASIS Standards are approved within an OASIS � OASIS Standards are approved within an OASIS Committee, submitted for public review, implemented Committee, submitted for public review, implemented by at least three organizations, and finally ratified by by at least three organizations, and finally ratified by the Consortium’s membership at large. the Consortium’s membership at large. � Membership � Membership � Liaison � Liaison � Contributors � Contributors � Sponsors � Sponsors
Committee Process Committee Process � Charter � Charter � Committee Draft � Committee Draft � Public Review � Public Review � Committee Specification � Committee Specification � OASIS Standard � OASIS Standard
Emergency Management Emergency Management Technical Committee Technical Committee � Charter � Charter The Technical Committee will apply itself to The Technical Committee will apply itself to answering requirements for data exchange among answering requirements for data exchange among emergency management, public safety, homeland emergency management, public safety, homeland security and related applications and systems. security and related applications and systems. � Subcommittee Structure � Subcommittee Structure � GIS � GIS � Infrastructure � Infrastructure � Messaging and Notification � Messaging and Notification � Adoption � Adoption
Current Standards Current Standards � � Common Alerting Protocol (CAP) 1.0 Common Alerting Protocol (CAP) 1.0 � Simple and standardized format for exchanging alerts and warnings � Simple and standardized format for exchanging alerts and warnings over various types of networks over various types of networks � Compatible with legacy and emerging “transport” methods, such as � Compatible with legacy and emerging “transport” methods, such as NOAA National Weather Radio specification and Web Services NOAA National Weather Radio specification and Web Services � Flexible geographic targeting � Flexible geographic targeting � Phased and delayed effective times and expirations � Phased and delayed effective times and expirations � Message update and cancellation features � Message update and cancellation features � Facility for including inline digital images and audio � Facility for including inline digital images and audio � Ratified April 2004 � Ratified April 2004 � Significant Uptake � Significant Uptake � � Common Alerting Protocol (CAP) 1.1 Common Alerting Protocol (CAP) 1.1 � Added < responseType> element � Added < responseType> element � Made < category> element mandatory � Made < category> element mandatory � Amended enumerated values for the < certainty> element � Amended enumerated values for the < certainty> element � Deleted the < password> element � Deleted the < password> element � Various editorial corrections and clarifications � Various editorial corrections and clarifications � Ratified October 2005 � Ratified October 2005
CAP Document Object Model CAP Document Object Model
Current Standards (Cont’d) Current Standards (Cont’d) � Emergency Data Exchange Language – � Emergency Data Exchange Language – Distribution Element (EDXL-DE) Distribution Element (EDXL-DE) � Overview � Overview � Open Container Model � Open Container Model � Provide flexible mechanisms to inform message routing and/or � Provide flexible mechanisms to inform message routing and/or processing decisions processing decisions � Dissemination of messages based on geographic delivery area � Dissemination of messages based on geographic delivery area � Use and re-use of data content and models developed by other � Use and re-use of data content and models developed by other initiatives initiatives � Business process-driven specific messaging needs across emergency � Business process-driven specific messaging needs across emergency professions professions � Supporting everyday events and incident preparedness, as well as � Supporting everyday events and incident preparedness, as well as disasters disasters � Facilitate emergency information sharing and data exchange � Facilitate emergency information sharing and data exchange � Multi-use format � Multi-use format � Introduced to the EM-TC November 2004 � Introduced to the EM-TC November 2004 � Two public reviews completed � Two public reviews completed � 60-Day August 29 - October 28, 2005 � 60-Day August 29 - October 28, 2005 � 15-Day February 17 - March 4, 2006 � 15-Day February 17 - March 4, 2006 � Ratified May, 2006 � Ratified May, 2006
EDXL Distribution Element DOM EDXL Distribution Element DOM 0…* < targetArea> < distribution> 0…* < contentObject> 1 < nonXMLContent> OR < xmlContent>
Work in Progress Work in Progress � Emergency Data Exchange Language – � Emergency Data Exchange Language – Hospital Availability Exchange (HAVE) Hospital Availability Exchange (HAVE) � Overview � Overview � The intent of the Hospital AVailability Exchange (HAVE) � The intent of the Hospital AVailability Exchange (HAVE) is to enable the exchange of information related to is to enable the exchange of information related to medical and health organizations and their resources medical and health organizations and their resources among other hospitals, state health departments and among other hospitals, state health departments and associations, emergency managers, and other associations, emergency managers, and other responsible emergency agencies involved in response responsible emergency agencies involved in response and preparedness. It is designed for everyday use, mass and preparedness. It is designed for everyday use, mass disasters, and preparedness scenarios. disasters, and preparedness scenarios. � Progress � Progress � Introduced to the EM-TC 1/25/06 � Introduced to the EM-TC 1/25/06 � Voted to accept 2/7/06 � Voted to accept 2/7/06 � Voted Committee Draft 8/22/06 � Voted Committee Draft 8/22/06 � Public Comment Period Anticipated Nov 1- Dec 30, 2006 � Public Comment Period Anticipated Nov 1- Dec 30, 2006
Work in Progress - 2 Work in Progress - 2 � � Emergency Data Exchange Language – Resource Message Emergency Data Exchange Language – Resource Message (EDXL-RM) (EDXL-RM) � Overview � Overview � Response to Request Resource � Response to Request Resource � Order Resource � Order Resource � Dispatch Resource � Dispatch Resource � Request for Resource Information (RFI) � Request for Resource Information (RFI) � Response to Request for Resource Information (RFI) � Response to Request for Resource Information (RFI) � Unsolicited Resource Offer � Unsolicited Resource Offer � Request Resource � Request Resource � Release Resource � Release Resource � Request to Return Resource � Request to Return Resource � Response to Request Return Resource � Response to Request Return Resource � Request Resource Quote � Request Resource Quote � Response to Request Resource Quote � Response to Request Resource Quote � Request for Resource Status � Request for Resource Status � Resource Request Status � Resource Request Status � Introduced to the EM-TC 8/29/05 � Introduced to the EM-TC 8/29/05 � Voted to accept 9/6/05 � Voted to accept 9/6/05 � Currently in Subcommittee � Currently in Subcommittee � Anticipate Committee Draft Fall 2006 � Anticipate Committee Draft Fall 2006
Legacy System Reach Back Legacy System Reach Back
Recommend
More recommend
