OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [emergency] HAVE comments - explicitly identifying thenormative parts in the data dictionary

Title: Re: [emergency] HAVE comments - explicitly identifying the
Terrific Sukumar, Alessandro!

This applies directly to EDXL-RM, too. We should also discuss a proposal Tuesday that we discussed in today's EM-Msg SC meeting: Normatively define geo-oasis:WhereType in an EDXL-HAVE Appendix (because it will be done first) and reference it in EDXL-RM.

This would include a clear note in the text for this specific appendix that our long term goal is to help OGC define a standard geo-oasis profile, which we can reference in future versions of EDXL specifications, while also explicitly allowing the use of any properly specified and namespaced Coordinate Reference System.


At 12:42 PM -0400 9/27/07, Dwarkanath, Sukumar wrote:
We reviewed all of Alessandro's comments (it was a grueling 3.5 hr session), and many comments could be attributed to an underlying theme - lack of information in the data dictionary that explicitly identified the normative parts. As a resolution, many of the comments can be addressed by the following items:
-         Separating the comments row into two rows: Constraints (which will include normative language) and Comments (non-normative), and
-         Including a few sentences at the beginning of the data dictionary that identifies that the data dictionary is non-normative, except for the following: 'Element', 'Usage' and the new 'Constraints' row. The schema would be identified as normative, which I think was an implicit understanding.  
So, my suggestion is to include the above given that:
-         it is directly relevant to compliance
-         it would not take too much effort to create the above pieces since, following the new compliance requirements from OASIS, I had earlier identified the normative pieces in the HAVE specification. If we decide on Tuesday, I can have an updated version by the end of the week.
-         it addresses most comments
I wanted to run it by the TC to get view and thoughts from others
Most of the other comments are editorial and can be incorporated quite easily. It definitely provides clarity. I feel a few of them should be deferred to the next release. I will post the document with the suggested disposition soon.
Sukumar Dwarkanath
SRA International
1920 N Street NW
Washington DC 20002
202-449-7761 (direct)
703-629-4074 (mobile)
202-338-6106 (fax)
This electronic message transmission contains information from SRA International, Inc., which may be confidential, privileged or proprietary. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution, or use of the contents of this information is strictly prohibited. If you have received this electronic information in error, please notify SRA immediately by telephone at 866-584-2143.

Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]