OASIS Emergency Management TC

Hi Everyone,

There are a few items in the CAPv1.1-IPAWS-Profile-WD05.doc 
specification document I'd like to point out.

In Section 2 in the Profile Note column for responseType we 
"recognize" the non-standard use of the value "Avoid" and note that 
it will not validate against the CAP1.1 schema. This does not 
represent any kind of endorsement and is meant only to show that we 
are aware of the non-standard practice. We decided not to say 
anything more about this because we can't promise that "Avoid" will 
become part of the next version of the standard in any future 
timeframe even though there is general agreement that it will.

In Section 2 in the Profile Specification column for resourceDesc we 
chose to specify "EAS Broadcast" rather than "EAS Audio" and "EAS 
StreamingAudio" to allow for future inclusion of other media types.

In Section 2 in the Profile Specification column for mimeType we made 
these values explicit to avoid ambiguity about existing and possible 
future MIME types.

In Section A (Appendix) we include several Questions in lines.  We should decide whether to retain the commented 
questions in the Public Review version to gather public review 
opinion or to include restrictions in the schema or provide 
annotations explaining the intention to:

require the TimeZone offset in 

On 17 Feb 2009, at 01:58, Rex Brooks wrote:

> There are a few items in the CAPv1.1-IPAWS-Profile-WD05.doc
> specification document I'd like to point out.


Also, you can't use the *same* Namespace identifier for both CAP 1.1  
and CAP 1.1 IPAWS Profile.

Cheers...  Renato Iannella
NICTA

Thanks Renato,

We discussed this. Hopefully, someone can refresh my memory on our decision.

I'll have to go back over the Meeting Notes otherwise.

Cheers,
Rex

At 8:57 AM +1000 2/17/09, Renato Iannella wrote:
>On 17 Feb 2009, at 01:58, Rex Brooks wrote:
>
>>There are a few items in the CAPv1.1-IPAWS-Profile-WD05.doc
>>specification document I'd like to point out.
>
>
>Also, you can't use the *same* Namespace identifier for both CAP 1.1 
>and CAP 1.1 IPAWS Profile.
>
>Cheers...  Renato Iannella
>NICTA
>
>
>
>---------------------------------------------------------------------
>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

Thanks Renato,

We discussed this. Hopefully, someone can refresh my memory on our decision.

I'll have to go back over the Meeting Notes otherwise.

Cheers,
Rex

At 8:57 AM +1000 2/17/09, Renato Iannella wrote:
>On 17 Feb 2009, at 01:58, Rex Brooks wrote:
>
>>There are a few items in the CAPv1.1-IPAWS-Profile-WD05.doc
>>specification document I'd like to point out.
>
>
>Also, you can't use the *same* Namespace identifier for both CAP 1.1 
>and CAP 1.1 IPAWS Profile.
>
>Cheers...  Renato Iannella
>NICTA
>
>
>
>---------------------------------------------------------------------
>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