ebxml-architecture message


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

 


Help: OASIS Mailing Lists Help | MarkMail Help
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

Subject: Re: Capitalization Styles


We should probably make it explicit that names are case sensitive.

I would advocate not to have two different camel case styles, e.g. one for 
elements and then one for attributes.

--
Jeff.Suttor@Sun.com      http://sun.com/xml
XML Technology Center    http://web.eng/xml


>Date: Mon, 04 Dec 2000 17:46:30 -0500
>From: Nikola Stojanovic <nhomest1@twcny.rr.com>
>Subject: Capitalization Styles
>To: ebXML-Architecture List <ebxml-architecture@lists.ebxml.org>
>X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
>List-Owner: <mailto:ebxml-architecture-help@lists.ebxml.org>
>List-Post: <mailto:ebxml-architecture@lists.ebxml.org>
>List-Subscribe:  
<mailto:ebxml-architecture-request@lists.ebxml.org?body=subscribe>
>List-Unsubscribe:  
<mailto:ebxml-architecture-request@lists.ebxml.org?body=unsubscribe>
>List-Archive: <http://lists.ebxml.org/archives/ebxml-architecture>
>List-Help: <http://lists.ebxml.org/doc/email-manage.html>, 
<mailto:ebxml-architecture-request@lists.ebxml.org?body=help>
>
>As discussed in our last con call, here are 2 proposals for Capitalization
>Style in ebXML. It seems that the final proposal could be merged with other
>Naming Convention docs that are being produced in CC. I can also imagine
>that we would allow for submissions of new proposals as well as for
>modifications of the current ones, but would suggest that we don't expand
>the scope before we agree on what we have now.
>
><objective>
>
> <provide a consistent "Capitalization Style">
>
> <programming languages are not in scope>
>  Cobol, Smalltalk, C++, Java, C#, ... rules are irrelevant. Only languages
>used in ebXML, like: XML & others, UML, OCL, ...
> </programming languages are not in scope>
>
> <composition of names are not in scope>
>  usage of verbs, nouns, adjectives, prefix (postfix) notations,  Hungarian
>notation, namespace hierarchy (root, ...) are not part of these proposals
> </composition of names are not in scope>
>
></objective>
>
><proposals>
>
> <simpleNaming>
>  useLowerCamelCase (Camel Casing)
> </simpleNaming>
>
> <capitalizationAndCategorisation>
>  <useLowerCamelCase (Camel Casing) for XML attributes, UML attributes,
>operations, methods, .../>
>  <UseUpperCamelCase (Pascal Casing) for XML Elements, UML Classes,
>Interfaces, .../>
> </capitalizationAndCategorisation>
>
></proposals>
>
><otherConstraints>
>
> <no '.' '_' '-' prefix (postfix) notations>
>  don't use: header.manifest, stock_quote_12345, commercial-transaction, ...
> </no '.' '_' '-' prefix (postfix) notations>
>
> <capitalization of acronyms>
>  avoid acronyms, but if ... use ebXmlHeader instead of ebXMLHeader
> </capitalization of acronyms>
>
></otherConstraints>
>
><someComments>
>
> <OMG UML Specification 1.3 does contain Style Guidelines with some aspects
>similar to capitalizationAndCategorisation/>
>
> <some standards - http://www.w3.org/TR/xhtml1/ >
>  4.2 Element and attribute names must be in lower case
> <some standards - http://www.w3.org/TR/xhtml1/ />
>
></someComments>
>
>Regards,
>Nikola
>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC