W3C home > Mailing lists > Public > public-hydra@w3.org > January 2015

Re: Naming style: camelCase or not? Plural or not? (#81)

From: <tomasz@t-code.pl>
Date: Mon, 05 Jan 2015 08:17:06 +0000
Message-ID: <9024dd67ca6c27d2aa7c00ecea42d418@rainloop.t-code.pl>
To: "Ruben Verborgh" <ruben.verborgh@ugent.be>, "Hydra" <public-hydra@w3.org>
January 5 2015 9:03 AM, "Ruben Verborgh" <ruben.verborgh@ugent.be> wrote: 
> Hi Kévin,
> 
>> I'm working on implementing a JSON-LD+Hydra API. Some property's names follow the camelCase style
>> and some other are all in lowercase.
> 
> I think we should normalize this ASAP.
> 
>> • entrypoint / readonly / writeonly (all in small caps)
>> • statusCodes / supportedProperty / supportedOperation
> 
> CamelCase is what we want, I believe.
>

Readonly and writeonly are getting changed to writeable and readable anyway. We all seemed to agree with Markus' call for consensus [1].

By the way there have been quite a few changes since June 19 (last draft). Any chance for a spec spec update? I'm getting the impression that people start to discuss matters already resolved becaus the documentation is out-of-date.

> 
>> A similar naming inconsistency appends with the plural form:
>> 
>> • supportedClass / supportedOperation (singular)
>> • statusCodes (plural)
>> Is it intended?
> 
> Another issue has tracked the singularization of properties:
> https://github.com/HydraCG/Specifications/issues/25
> 
> This has been fully completed, with the exception of statusCodes,
> because there were two properties statusCode and statusCodes:
> https://github.com/HydraCG/Specifications/issues/27
> We agreed to remove statusCodes, so this shouldn't be an issue.
> However, it still needs to be edited in the spec.
> 
> Best,
> 
> Ruben

Regards,
Tom

[1] http://lists.w3.org/Archives/Public/public-hydra/2014Jul/0082.html
Received on Monday, 5 January 2015 08:18:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:44 UTC