[emergency-cap-profiles] Re: schema

[Rex Brooks <rexb@starbourne.com>]

Thanks Jacob,

This puts the discussion in exactly the light I was hoping you would 
provide. It is clear that there are some decisions we need to 
consider beyond the simple changes done to fulfill the Issues. I 
haven't come to my own conclusion on these issues. In my opinion the 
question is how we make it as straightforward as possible for 
implementations to be testably conformant.

Cheers,
Rex

At 12:09 PM -0400 6/8/09, Jacob Westfall wrote:
>  > Could you look at the schema for CAP v1.2 and advise me what needs to
>>  adjusted for the proflile? I'm making the changes in the spec doc and
>
>When CAP 1.2 is used, there are first of all some changes to the 
>profile itself.  The DateTime Data Type can be removed from 
>Terminology and the profile table row for <sent> can be removed and 
>the row for <expires> can be updated to remove the timezone 
>language.  The <expires> language could be updated to say "An 
>expiration date/time is REQUIRED for back compatility with EAS" or 
>something similiar.  The <responseType> row can also be removed.
>
>Regarding adding a schema, there is still the open question of 
>whether a schema will add value to the profile.  Much of the 
>normative content of the profile cannot be represented in W3C 
>schema.  Validating that content would mean using an additional 
>component like Schematron to extend the W3C schema.  Also some of 
>the constraints cannot even be represented properly using Schematron 
>either.  So to what lengths do we go to try and validate this 
>content?  Do we just provide a schema for "structure" and leave 
>validation of content to 3rd party application logic?
>
>A quick review accounting for just W3C schema capable changes that 
>the profile would make to the CAP 1.2 schema, there are the 
>following:
>
><code> - moves from optional to at least 1 instance required
><info> - moves from optional to at least 1 instance required
><eventCode> - moves from optional to at least 1 instance required
><expires> - moves from optional to required
><area> - moves from optional to at least 1 instance required
>
>--
>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