I believe our thinking was that since messages that conform to the Profile are, perforce, valid instances of a CAP 1.1 message, having a different namespace wasn't mandatory. And if we give them a different namespace it will break interoperability with non-IPAWS transports.
- Art
Art Botterell, Manager
Community Warning System
Contra Costa County Office of the Sheriff
50 Glacier Drive
Martinez, California 94553
(925) 313-9603
fax (925) 646-1120
>>> Rex Brooks <> 02/16/09 3:55 PM >>>
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
---------------------------------------------------------------------
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
