CamelCase convention recommendation from OpenCSA liaison committee

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:  

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