Re: [emergency-cap-profiles] Please review Abstract from WorkingDraft

[Rex Brooks <rexb@starbourne.com>]

Yes, but I do expect we will include a schema to explicitly apply constraints.

I prefer the previous Abstract, minus the last sentence, but I could 
live with this if that's the SC's will.

Cheers,
Rex

At 11:13 AM -0500 1/30/09, Jacob Westfall wrote:
>  > Declared XML Namespace(s):
>>  urn:oasis:names:tc:emergency:cap:1.1:profile:ipaws
>
>Will this namespace entry be removed if the profile spec doesn't 
>include a schema?
>
>My suggestion on a shorter abstract:
>
>This profile of the XML-based Common Alerting Protocol (CAP) 
>describes an intepretation of the OASIS CAP v1.1 standard necessary 
>to meet the needs of the Integrated Public Alert and Warning System 
>(IPAWS), a public alerting "system of systems" created by the U.S. 
>Federal Emergency Management Agency.
>
>--
>jake@jpw.biz
>--
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  Follow this link to all your TCs in OASIS at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


-- 
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670