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

[ashok malhotra <ashok.malhotra@oracle.com>]

Eric:
Isn't it a bit early to bring up backwards compatibility?  Some of the 
OASIS drafts are not even at the CD stage.
If we accept this limitation it seriously limits our ability to make 
changes.

All the best, Ashok


Eric Johnson wrote:
> Hi Anish,
>
> I'm not opposed to this change, but....
>
> If we change the capitalization of our policy intents, have we broken 
> backwards compatibility?  Do we need to preserve that, by perhaps 
> supporting both new and old forms, but mark the old form as 
> deprecated?  Or is the version # 1.1 really meaningless in terms of 
> compatibility?
>
> -Eric.
>
> Anish Karmarkar wrote:
>> I could go either way: a new issue or treat this as editorial.
>>
>> -Anish
>> -- 
>>
>> Eric Johnson wrote:
>>> 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
>>
>> ---------------------------------------------------------------------
>> 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
>
> ---------------------------------------------------------------------
> 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