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

[Eric Johnson <eric@tibco.com>]

Is it just me, or does the scope of this make it sounds like it should 
be raised as an issue?

-Eric.

Anish Karmarkar wrote:
> It was noticed in the SCA-Policy TC 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 its 1st 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 on its call today decided the following:
>
> LSC 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.
>
>
> -Anish
> -- 
>
>
> ---------------------------------------------------------------------
> 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