OASIS Organization for the Advancement of Structured Information Standards Introduction Slide Decks

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

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

Maintenance Schedule n Updated quarterly l As of end of quarter l Updates to be submitted in month following quarter n TC deck updates by TC’s l Subject to TC discussion n Reviewed by ___ before publishing to web

Targets n Single slide summaries n <=10 slide presentations

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

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

Technical Committee introduction page n Mission statement n Vision statement n Primary Beneficiaries

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

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

Product listing n Title and acronym only l Ex. Common Alerting Protocol (CAP)

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

Sub-Committee introduction page n Mission statement n Vision statement n Direct stakeholders

Product introduction pages n Purpose statement n Usage status n Current version n Status / current activity

Ex. Common Alerting Protocol (CAP) n Purpose l 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. n Usage status l Adopted throughout US, Canada, Europe for public alerting and to lesser extent, restricted alerts n Current version l v1.1 Errata 28 August 2006 n Status l v1.2 at technical committee review stage. ETA Q l v2.0 efforts to commence when v1.2 completed

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

Common Alerting Protocol (CAP) n Purpose l 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. n Usage status l Adopted throughout US, Canada, Europe for public alerting and to lesser extent restricted alerts n Current version l v1.1 Errata 28 August 2006 n Status l v1.2 at technical committee review stage. ETA Q l v2.0 efforts to commence when v1.2 completed

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

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

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

CAP is in the background profile:CAP-CP:Location: fr-CA Routier - Fermeture de route Monitor Immediate Minor Observed Doug Allport T12:00:00+00: T12:00:00+00:00 Doug Allport Routier - Fermeture de route - Doug Allport, Exercise Transport profile:CAP-CP:Event:0.3 roadClose layer:CAPAN:eventLocation:point , Saint John CAP-CP:Location: NBMASASui10286 DAllport T23:49: :00 Exercise Public profile:CAP-CP:0.3 Alert en-CA Roadway - Roadway Closure Monitor Immediate Minor Observed Doug Allport T12:00:00+00: T12:00:00+00:00 Doug Allport This is a test Road Closure Alert Free form text field More free form text here NB DOT Transport profile:CAP-CP:Event:0.3 roadClose layer:CAPAN:eventLocation:point , Saint John Issuer interfaces with form, IVR, custom application, etc. Issuing Application produces CAP Aggregator collects and shares CAP Distributor converts CAP to common and proprietary protocols Recipient interfaces with common products and services. Ex. Television, phone,...

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