[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency] Groups - CAP 1.1 Subcommittee Draft(CAP_1.1-draft_1-4-05) uploaded
At last, a constructive suggestion! Personally I'd have no problem with that suggested language, although my opinion isn't what matters. I think this issue was referred back to the GIS subcommittee last week, so I'm forwarding this to them. Thanks! - Art At 5:44 AM -0600 1/18/05, Jeff Kyser wrote: >Still seems to me that the following is clearer >and more precise (Section 3.3.1): > > Latitudes in the Southern Hemisphere and longitudes in the > Western Hemisphere are signed negative with a leading dash. > >(as opposed to 'Coordinates in the Southern and Western Hemispheres ...') > >A similar sentence has been added to Section 1.5, it would benefit from >the same language. > >-jeff > > >On Jan 9, 2005, at 10:14 PM, Art Botterell wrote: > >>Bob - >> >>Your concern was discussed at some length by both the GIS and >>Messaging Subcommittees. During the 11/30 call the Messaging >>Subcommittee took up Issue 14 and voted to stick with this >>formulation, which is in line with GIS industry and ISO usage. >> >>Of course you're welcome to offer an amendment to the full TC for >>discussion on our next call, hopefully with some specific alternate >>language. After that it'll be up to the Committee. >> >>- Art >> >> >>At 10:35 PM -0500 1/9/05, Bob Wyman wrote: >>>Art Botterell wrote: >>>> The CAP 1.1 spec as approved by the Messaging Subcommittee. Please >>>> review for approval to move it to public comment ASAP. >>> In the issues list for the CAP specification, it is stated that >>>issue 14 would be addressed in 1.1... Yet, the offending and non-sensical >>>sentence "Coordinates in the Southern and Western hemispheres are signed >>>negative with a leading dash." remains in the specification. As I have been >>>saying, since before 1.0 was approved by this working group, "coordinates" >>>can't be signed -- only the components of a coordinate can be signed. >>> I suggest that an effort should be made to incorporate committed >>>changes to the specification before it is released for public comment. >>> >>> bob wyman >>> >>> >>>-----Original Message----- >>>From: firstname.lastname@example.org [mailto:email@example.com] >>>Sent: Friday, January 07, 2005 6:33 PM >>>To: firstname.lastname@example.org >>>Subject: [emergency] Groups - CAP 1.1 Subcommittee Draft >>>(CAP_1.1-draft_1-4-05) uploaded >>> >>>The CAP 1.1 spec as approved by the Messaging Subcommittee. Please review >>>for approval to move it to public comment ASAP. >>> >>>- Art >>> >>> -- Art Botterell >>> >>>The document named CAP 1.1 Subcommittee Draft (CAP_1.1-draft_1-4-05) has >>>been submitted by Art Botterell to the OASIS Emergency Management TC >>>document repository. >>> >>>Document Description: >>>A draft update to the CAP specification incorporating issues identified to >>>date. Approved by the Messaging Subcommittee on 1/4/05. >>> >>>Download Document: >>>http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/10905/CA >>>P_1.1-draft_1-4-05 >>> >>>View Document Details: >>>http://www.oasis-open.org/apps/org/workgroup/emergency/document.php?document >>>_id=10905 >>> >>> >>>PLEASE NOTE: If the above links do not work for you, your email application >>>may be breaking the link into two pieces. You may be able to copy and paste >>>the entire link address into the address field of your web browser. >>> >>>-OASIS Open Administration >>> >>> >>>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. >> >> >>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.