OASIS Organization for the Advancement of Structured Information Standards

1. OASISOrganization for the Advancement of Structured Information Standards Presentation Title Appears Here Appears Here Appears Here Appears Here

2. Last Updated: 01 January 2010 Presentation Summary (Can be Introduction) • Name & Acronym/Abbrv of Spec/Cmte • Topic/Activity Area of Spec/SC or TC • Purpose of Product • Target Audience • Features for Spec; Interests/Domains for SC • Benefits for Spec; Goals/Objectives for SC • Adoption/Usage for Spec; Track Record for SC • Outlook: Current & Future

3. OASIS Specification/Committee Introduction (Can be Summary) • Mission/Purpose Statement • Sample: To drive the development of emergency-related open standards for data interoperability. • Vision Statement • Sample: Issue once, for distribution to all with a need to know, and authority to receive. • Beneficiaries: Direct Stakeholders • Sample: Public safety officials, broadcasters

4. Spec/Cmte Features • Sample: Public, private & restricted • Sample: Updates and cancels • Sample: Actual, testing and exercises • Sample: Defined by urgency, severity and certainty • Sample: Categorized to common categories; e.g. ContactInfo • Sample: Area defined using GML, Coordinate Reference Systemes, geocodes • Sample: Supports resources • Sample: Adaptable to specific user communities

5. Spec/Cmte Benefits • Sample: Single system can be used to support all urgencies, severities and certainties • Sample: May be filtered by category, location, etc. • Sample: Easily converted into last mile formats, including SMS, Broadcast, E-911, etc. • Sample: Available for all user communities.

6. Spec/Cmte Adoption • In OASIS Process; OASIS Standard: Adopted as ITU standard; etc. • In Evaluation: Endorsed by US federal and state governments: In Evaluation by state systems; In use in state systems; etc. • In Evaluation by Canadian federal and provincial governments; Endorsed by Canadian federal and provincial governments; In Use in provincial systems; In implementation process in national alert aggregation system; etc.

7. Additional Info Example 1 <?xml version="1.0" encoding="utf-8"?> <alert xmlns="urn:oasis:names:tc:emergency:cap:1.1"> <identifier>NBMASASui10286</identifier> <sender>DAllport</sender> <sent>2009-07-17T23:49:40.0436089+00:00</sent> <status>Exercise</status> <scope>Public</scope> <code>profile:CAP-CP:0.3</code> <msgType>Alert</msgType> <info> <language>en-CA</language> <event>Roadway - Roadway Closure</event> <responseType>Monitor</responseType> <urgency>Immediate</urgency> <severity>Minor</severity> <certainty>Observed</certainty> <audience>Doug Allport</audience> <onset>2009-07-18T12:00:00+00:00</onset> <expires>2009-07-19T12:00:00+00:00</expires> <senderName>Doug Allport</senderName> <headline>This is a test Road Closure Alert</headline> <description>Free form text field</description> <instruction>More free form text here</instruction> <web>http://www.gnb.ca/0113/index-e.asp</web> <contact>NB DOT 888-555-5555</contact> <category>Transport</category> <eventCode> <valueName>profile:CAP-CP:Event:0.3</valueName> <value>roadClose</value> </eventCode> <parameter> <valueName>layer:CAPAN:eventLocation:point</valueName> <value>45.2449203344103,-66.11091613769532</value> </parameter> <area> <areaDesc>1301006 - Saint John</areaDesc> <geocode> <valueName>profile:CAP-CP:Location:0.3</valueName> <value>1301006</value> </geocode> </area> </info> <info> <language>fr-CA</language> <event>Routier - Fermeture de route</event> <responseType>Monitor</responseType> <urgency>Immediate</urgency> <severity>Minor</severity> <certainty>Observed</certainty> <audience>Doug Allport</audience> <onset>2009-07-18T12:00:00+00:00</onset> <expires>2009-07-19T12:00:00+00:00</expires> <senderName>Doug Allport</senderName> <headline>Routier - Fermeture de route - Doug Allport, Exercise</headline> <web>http://www.gnb.ca/0113/index-e.asp</web> <category>Transport</category> <eventCode> <valueName>profile:CAP-CP:Event:0.3</valueName> <value>roadClose</value> </eventCode> <parameter> <valueName>layer:CAPAN:eventLocation:point</valueName> <value>45.2449203344103,-66.11091613769532</value> </parameter> <area> <areaDesc>1301006 - Saint John</areaDesc> <geocode> <valueName>CAP-CP:Location:0.3</valueName> <value>1301006</value> </geocode> </area> </info> </alert> Issuer interfaces with form, IVR, custom application, etc. Aggregator collects and shares Issuing Application produces Recipient interfaces with common products and services; e.g. Television, cellphone, ... Distributor converts to common and proprietary protocols

8. Additional Info Example 2 • US Integrated Public Alert and Warning System Profile • Defines event codes and location code references and requirements, in support of Emergency Alert System and other legacy systems • Canadian Profile • Defines event codes and location code references and requirements in support of national needs, including automated translation • Canadian Profile includes event location references

9. Last Updated: 01 January 2010 Presentation Summary (Can Repeat Slide 2 or add emphasis) • Name & Acronym/Abbrv of Spec/Cmte • Topic/Activity Area of Spec/SC or TC • Purpose of Product • Target Audience • Features for Spec; Interests/Domains for SC • Benefits for Spec; Goals/Objectives for SC • Adoption/Usage for Spec; Track Record for SC • Outlook: Current & Future