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


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

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

Subject: Re: [sca-assembly] CamelCase convention recommendation from OpenCSAliaison committee

This only documents the existing practice within SCA dating back to pre 
1.0 days. I, personally don't remember any extensive discussion on the 
convention before being used in SCA. The LSC recommended documenting the 
convention that already exists. I suspect, the reason SCA chose to use 
this convention is because it lines up with the conventions used in the 
OO world, similar to the rationale on Eric van der Vlist's blog [1] that 
you already list at [2].



[2] http://xml.coverpages.org/ndr.html

Robin Cover wrote:
> Mike,
> I think it would be of interest to understand how the new
> formulations relate to one or more of the NDR specifications
> that document common practice in related environments.  In
> any case, this information would be useful to me for creating
> a new entry in my NDR overview document:
> http://xml.coverpages.org/ndr.html
> [and: http://xml.coverpages.org/camelCase.html ]
> Thanks if someone can provide this kind of description.
>  - Robin
> Robin Cover
> OASIS, Director of Information Services
> Editor, Cover Pages and XML Daily Newslink
> Email: robin@oasis-open.org
> Staff bio: http://www.oasis-open.org/who/staff.php#cover
> Cover Pages: http://xml.coverpages.org/
> Newsletter: http://xml.coverpages.org/newsletterArchive.html
> Tel: +1 972-296-1783
> On Fri, 21 Nov 2008, Mike Edwards wrote:
>> Folks,
>> The SCA-Policy TC noticed that intents defined in various SCA
>> spec do not follow any particular convention. That TC decided to fix it
>> for the policy specs by adopting the convention of using camelCase with
>> first letter lower case unless the word was an acronym (such as SOAP
>> or JMS). They then asked the liaison committee to make this
>> recommendation to the rest of the OpenCSA TCs.
>> The Liaison subcommittee today decided the following:
>> Liaison committee recommends that all the TC's adopt the Policy TC
>> recommendation that intents use camelCase (first letter lowercase)
>> except for acronyms which would be all upper case.
>> and
>> LSC recommends adding some text to the "conventions" section of the
>> specs which describes the naming conventions:
>> e.g. intents as above, type names are CamelCase, element names are
>> camelCase, attributes are @camelCase are preceded by an "@" sign, etc.
>> ....and that the Assembly TC should take the lead on documenting these
>> conventions by adding
>> a new section at the start of the spec.
>> I will raise an issue for this.
>> Yours,  Mike.
>> Strategist - Emerging Technologies, SCA & SDO.
>> Co Chair OASIS SCA Assembly TC.
>> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
>> Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431
>> Email:  mike_edwards@uk.ibm.com
>> Unless stated otherwise above:
>> IBM United Kingdom Limited - Registered in England and Wales with number
>> 741598.
>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 
>> 3AU
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

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