----- Original Message -----
Sent: Monday, April 05, 2004 4:00
PM
Subject: [emergency] Implementation Guide
Outline
Hi Folks,
This is a first draft, strawman for the implementation or implementer's
guide. So please view it as a point of departure. I left out tentative
contacts from the justice/law enforcement community that I have already tried
to arrange, and our recent discussions on XML examples on the list.
Common Alerting Protocol
Implementation Guide Outline
(Note: the first question we need to ask
is "What does this audience of implementers need to know?" It is suggested
that getting answers from this community is the best way to determine this, so
it is also suggested that a method for that be
adopted.)
1.Introduction
1.1 Purpose of
CAP--Single Consistent Message Across All Primary Audience
Boundaries
1.1.1
Provide Common Message Format and
Terminology
1.1.2
Transport Independence
1.1.2.1 Data
Dictionary
1.1.2.2 XML
Schema for API s and Web Serivces
1.1.2.3
One-way Broadcast Capability
2. Basic Concepts
2.1 Notification Messages
Protocol
2.1.1 Not
Signal Protocol
2.1.2 Code
of Conduct, Rules of Conduct, Conventions
2.2 Implementer
Audience
2.2.1.
Emergency Management
2.2.2. First
Responders
2.2.3. Public Immediately At
Risk
2.2.4.
Updates and Secondary Audiences
2.2.4.1.
Update Consistency for Changes to Area, Severity, Urgency,
Recommendations
2.2.4.2.
Update Consistency for Additional Related
Incidents
(Subsequent
Incidents impacting Traffic, Responders, Recommendations)
3. Broadcast
Considerations (Need Implementer[s] Feedback from Broadcast/Cable/Satellite
Community)
3.1.
Video
3.1.1.
Broadcast
3.1.2.
Cable/Satellite
3.2.
Radio
3.2.1.
Broadcast
3.2.1.
Satellite
4. Internet Considerations (Need Implementer[s] Feedback from
Public Health, Public Safety Community)
4.1.
Data Dictionary
4.1.1. What
Motivates the Developer's Use of the DD? (What App Types?)
4.1.2.1,
Alert, .2. Info, .3. Area, .4. Description, etc. ...
4.1.2. How
Does Developer Use DD as Normative Source?
4.2.2.1,
Alert, .2. Info, .3. Area, .4. Description, etc. ...
4.2. XML
Schema
4.1.1. What Motivates the Developer's Use of the XSD? (What App
Types?)
4.2.2.1,
Alert, .2. Info, .3. Area, .4. Description, etc. ...
4.1.2. How
Does Developer Use XSD as Normative Source? (What App
Types?)
4.2.2.1,
Alert, .2. Info, .3. Area, .4. Description, etc. ...
5. GML
Implementor's Note (Literal Drop In) CAP Alert Messages as GML
FeatrueCollection
6. Examples(?)
Ciao,
Rex
--
Rex Brooks
GeoAddress: 1361-A Addison, Berkeley,
CA, 94702 USA, Earth
W3Address: http://www.starbourne.com
Email:
rexb@starbourne.com
Tel: 510-849-2309
Fax: By Request