Re: [emergency] Issue #22: Proposed Changes

[Art Botterell <acb@incident.com>]

While these would definitely be refinements, they don't appear to be 
essential to core functionalities.  Might these not be good 
candidates for 1.1?

- Art


At 9:53 AM -0500 12/30/03, R. Allen Wyke wrote:
>Ok, I went through the spec again and here are the elements that could
>benefit from tapping the <xsd:restriction> and <xsd:pattern> elements. I
>took a crack at coming up with the new definitions, but they need to be
>double checked against some code....they need to be tested. In places
>where more than 1 element has the same type of situation, just replace
>the value of the name attribute appropriately.
>
>1. <cap:identifier> and <cap:sender>: "no spaces or restricted
>characters (< and &)". Question: "restricted characters" aren't allowed
>in XML, so I *think* there is no reason to include this. OR, are you
>saying people can not use escaped versions of these either? Such as &lt
>and &amp?
>
><xsd:simpleType name="identifier">
>   <xsd:restriction base="xsd:string">
>     <xsd:pattern value="[^\s]">
>   </xsd:restriction>
></xsd:simpleType>
>
>2. <cap:addresses> and <cap:incidents>: "Multiple space-delimited
>addresses may be included. Addresses including whitepace must be
>enclosed in double-quotes."
>
><xsd:simpleType name="addresses">
>   <xsd:restriction base="xsd:string">
>     <xsd:pattern value="[\".*\"][\s\".*\"]?*">
>   </xsd:restriction>
></xsd:simpleType>
>
>3. <cap:references>: "...(in the form identifier/sender)...must be
>separated by whitepace." Question: Unable to fully understand what this
>was suppose to be - must have missed this in my ealier review. Are you
>basically saying it would be in the form <cap:identifier> + "/" +
><cap:sender>? If so, then we *might* be able to use the ealier
>definition of these elements to create the definition of reference,
>which means we only define in 1 place.
>
>4. <cap:eventCode>, <cap:parameter>, <cap:geocode>: "...in the form
>code_type=code...may not include spaces or XML-restricted
>characters...". This basically says any number of non-digits followed by
>"=" and any number of non-digits. Question: is "non-digit" what we want?
>
><xsd:simpleType name="eventCode">
>   <xsd:restriction base="xsd:string">
>     <xsd:pattern value="\D*=\D*">
>   </xsd:restriction>
></xsd:simpleType>
>
>5. <cap:headline>: "...160 characters may be useful target limit..."
>Question: Restrict to 160??
>
><xsd:simpleType name="eventCode">
>   <xsd:restriction base="xsd:string">
>     <xsd:pattern value=".{160}">
>   </xsd:restriction>
></xsd:simpleType>
>
>[GIS Related]
>Can one of the GIS experts in the group please sum up the patterns for
>the following for me, and then I can take a crack at improving the
>schema? I do not know enough about these items to ensure everything is
>covered.
>
>6. <cap:polygon>: two things here - "...represented by a
>whitespace-delimited list of WSG-84 coordinate values..." and "...first
>and last pairs of coordinates must be the same".
>
>7. <cap:circle>: "...represented by a central point given WSG-84
>coordinate value..."
>
>8. <cap:altitude>: "...altitude measure is in feet above mean sea
>level..."
>
>9. <cap:ceiling>: "...altitude measure is in feet above mean sea
>level..."
>
>--
>R. Allen Wyke
>Chair, OASIS Emergency Management Technical Committee
>http://www.oasis-open.org/committees/emergency
>
>
>To unsubscribe from this mailing list (and be removed from the 
>roster of the OASIS TC), go to 
>http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php.