OASIS Organization for the Advancement of Structured Information Standards

1. OASISOrganization for the Advancement of Structured Information Standards Introduction Slide Decks

2. Purpose • Education and orientation • By members • By prospective members • Promotional briefings • By members • By prospective members • Ex. To their mgmt, for approval to join OASIS

3. Slide Decks to be produced • OASIS introduction • OASIS process introduction • Technical Committee (TC) introductions • Sub-Committee (SC) introductions • Product overviews

4. Maintenance Schedule • Updated quarterly • Updates to be submitted in month following quarter • Status statements as of end of quarter • TC deck updates by TC’s • Subject to TC discussion

5. Targets • Single slide summaries • <=10 slide presentations

6. Technical Committee Slide Deck • OASIS introduction page • Technical committee introduction page • Sub-committee listings • Products listings • Sub-committee / product associations • Sub-committee introduction pages • Product introduction pages

7. OASIS • Mission • To drive the development, convergence and adoption of open standards for the global information society. • Not-for-profit consortium • Founded in 1993 as SGML Open • Global representation • 5,000+ participants representing … • 600+ organizations and individual members in … • 100+ countries

8. Technical Committee introduction page • Mission statement • Vision statement • Primary Beneficiaries

9. Ex. Emergency Management TC • Mission • Create emergency-related standards for data interoperability. • Vision • Issue once, for distribution to all with a need to know, and authority to receive. • Direct Stakeholders • Public safety officials, broadcasters

10. Sub-committee listing • Title and acronym only • Ex. Messages and Notification (Msg-Not)

11. Product listing • Title and acronym only • Ex. Common Alerting Protocol (CAP)

12. Sub-committee / product associations • Sub-committee acronym followed by product acronyms (or names) • Ex. Msg-Not: CAP, EDXL, EDXL-DE, ...

13. Sub-Committee introduction page • Mission statement • Vision statement • Direct stakeholders

14. Product introduction pages • Purpose statement • Usage status • Current version • Status / current activity

15. Ex. Common Alerting Protocol (CAP) • Purpose • Open, non-proprietary digital message format for all types of alerts and notifications, public, restricted and private. Supports routing, filtering and conversion to other formats. • Usage status • Adopted throughout US, Canada, Europe for public alerting and to lesser extent, restricted alerts • Current version • v1.1 Errata 28 August 2006 • Status • v1.2 at technical committee review stage. ETA Q4 2009 • v2.0 efforts to commence when v1.2 completed

16. Product Overview • Product introduction page • Features summary • Benefits summary • Adoption • Timeline • Additional information • Focus on clarity, highlight key feature, implementation challenges, etc.

17. Ex. Product introduction page Common Alerting Protocol (CAP) • Purpose • Open, non-proprietary digital message format for all types of alerts and notifications, public, restricted and private. Supports routing, filtering and conversion to other formats. • Usage status • Adopted throughout US, Canada, Europe for public alerting and to lesser extent restricted alerts • Current version • v1.1 Errata 28 August 2006 • Status • v1.2 at technical committee review stage. ETA Q4 2009 • v2.0 efforts to commence when v1.2 completed

18. Ex. Features CAP Features • Public, private and restricted messaging • Updates and cancels • Actual, testing and exercises • Every alert defined by urgency, severity and certainty • Categorized to common themes. Ex. Meteorological • Alert area may be defined using GIS, and or geocodes • Supports resources • Adaptable to specific user communities

19. Ex. Benefits CAP Benefits • Single system can be used to support alerts of all urgencies, severities and certainties • Messages may be filtered based on urgency, severity and certainty, category, location, etc. • Easily converted into last mile formats, including SMS, RSS, etc.

20. Ex. Adoption CAP Adoption • Adopted as ITU standard • Endorsed by US federal and state governments, in use in state systems, being implemented in national systems • Endorsed by Canadian federal and provincial governments, in use in provincial system, being implemented in national alert aggregation system

21. Ex. Timeline CAP Timeline • Submission by Art Botterrell • 1.0 March 2004 • 1.1 October 25 • 1.1 Errata October 2007 • ITU Adoption • 1.2 ETA October 2009 • 2.0 ETA 2011

22. Ex. Elaboration CAP is in the background <?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 CAP Issuing Application produces CAP Recipient interfaces with common products and services. Ex. Television, phone, ... Distributor converts CAP to common and proprietary protocols

23. Ex. Elaboration CAP is adaptable • US Integrated Public Warning System Profile • Defines event codes and location code references and requirements, in support of Emergency Alert System and other legacy systems • Canadian Profile of CAP (CAP-CP) • Defines event codes and location code references and requirements in support of national needs, including automated translation • Canadians are including event location references