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

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

From: Markus Lanthaler <markus.lanthaler@gmx.net>
Date: Mon, 5 Jan 2015 20:22:50 +0100
To: "'Hydra'" <public-hydra@w3.org>
Message-ID: <037901d0291c$ffd69360$ff83ba20$@gmx.net>
On 5 Jan 2015 at 09:02, Ruben Verborgh 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.

Entrypoint is debatable.. readonly and writeonly will be replaced with
readable and writable, see ISSUE-14 [1].


>> A similar naming inconsistency appends with the plural form:
>> 
>> 	• supportedClass / supportedOperation (singular)
>> 	• statusCodes (plural)
>> Is it intended?

No, statusCodes will be dropped. See ISSUE-27 [2]

So, summarized, this is mostly due to a currently outdated spec.

 
> 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.


[1] https://github.com/HydraCG/Specifications/issues/14
[2] https://github.com/HydraCG/Specifications/issues/27


--
Markus Lanthaler
@markuslanthaler
Received on Monday, 5 January 2015 19:23:18 UTC

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