RE: [emergency-msg] Federal XML Guidelines

[Rex Brooks <rexb@starbourne.com>]

Hey, this sounds like a good idea! I vote for it.

Cheers,
Rex

At 1:29 PM -0500 3/28/06, Ham, Gary A wrote:
>Based on the this and the previous reference to ebXML as doing the 
>same, we may want to keep Resource in upper camel case and live with 
>the inconsistency until the 2.0 versions of CAP and the DE.  If one 
>or the other were different, we could be too. 
>
>How many other standards out there that are NOT using these rules? 
>Is it a significant group, or are we out on a limb?
>
>
>R/s
>Gary A. Ham
>Senior Research Scientist
>Battelle Memorial Institute
>540-288-5611 (office)
>703-869-6241 (cell)
>"You would be surprised what you can accomplish when you do not care 
>who gets the credit." - Harry S. Truman
>
>
>
>From: Mark Carlson - Conneva, Inc. [mailto:conneva@gmail.com]
>Sent: Tuesday, March 28, 2006 1:09 PM
>To: emergency-msg@lists.oasis-open.org
>Subject: Fwd: [emergency-msg] Federal XML Guidelines
>
>More background for our XML element and type naming convention 
>discussion.  (Thanks, Robin).
>
>BTW, the June 2005 Federal XML Guidelines are consistent with regard 
>to element and attribute naming with the April 2002 draft I 
>referenced earlier.
>
>Mark
>
>Federal XML Naming and Design Rules Project
>
>Reference document: 
><http://xml.coverpages.org/Federal-NDR-20050609.pdf>Federal XML 
>Naming and Design Rules. Draft Version 2. June 09, 2005. 105 pages.
>
>Extracted text:
>
>lines 1038-1039
>
>[GNR8] The UpperCamelCase (UCC) convention MUST be used for naming 
>elements and types.
>
>lines 1041-1041:
>
>[GNR9] The lowerCamelCase (LCC) convention MUST be used for naming attributes.
>
>lines 1045-1049
>
>4.2.1 Complex Type Names for Complex Data Elements
>[CTN1] An xsd:complexType name based on a complex data element MUST 
>be the Dictionary Entry Name with the separators removed and with 
>with the suffix "Type" appended following the upper camel case 
>convention.
>
>lines 989-995
>
>[Note] The use of CamelCase for Dictionary Entry Names has been 
>considered, but has been rejected for following reasons:
>
>Use of CamelCase will not allow the use of spell checkers
>Strict use of CamelCase makes it impossible to use separators (" .") 
>and therefore doesn't allow an unambiguous identification of the 
>composing parts of the Dictionary Entry Name.
>
>
>---------- Forwarded message ----------
>From: Robin Cover <<mailto:robin@oasis-open.org> robin@oasis-open.org>
>Date: Mar 28, 2006 10:55 AM
>Subject: Re: [emergency-msg] Federal XML Guidelines
>To: "Mark Carlson - Conneva, Inc." 
><<mailto:conneva@gmail.com>conneva@gmail.com >
>
>Hi Mark. I don't know what the thread was about,
>but these docs may be of interest:
>
><http://xml.coverpages.org/camelCase.html>http://xml.coverpages.org/camelCase.html
><http://xml.coverpages.org/ndr.html>http://xml.coverpages.org/ndr..html
>
>Robin Cover
>
>=================
>
>On Tue, 28 Mar 2006, Mark Carlson - Conneva, Inc. wrote:
>
>>  >From the April 2002 Draft Federal XML Developer's
>>  Guide< 
>><http://xml.gov/documents/in_progress/developersguide.pdf>http://xml.gov/documents/in_progress/developersguide.pdf>
>>
>>  3.1 STANDARDIZED CASE CONVENTION GUIDANCE
>>
>>  Federal developers SHALL adopt the camel case convention, as defined by the
>>  ebXML Technical Architecture, when creating XML component names. Excerpts
>>  are provided in Appendix A.
>>
>>    - XML Elements and XML Schema data types use upper camel case: The
>>    first letter in the name is upper case, as is the letter beginning each
>>    subsequent word.
>>    - XML Attributes use lower camel case: Like upper camel case, except
>>    the first letter of the first word is lower case.
>>
>>
>>  Mark
>>
>
>--


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