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

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

From: Kévin Dunglas <dunglas@gmail.com>
Date: Mon, 5 Jan 2015 09:11:15 +0100
Message-ID: <CAOv1iQY4xbtwc-n8ieBGNSsaLodXBUQrMGFBrBS9mp377L57bQ@mail.gmail.com>
To: Ruben Verborgh <ruben.verborgh@ugent.be>
Cc: Hydra <public-hydra@w3.org>
Thank you Ruben.

I prefer the CamelCased style too.

2015-01-05 9:02 GMT+01:00 Ruben Verborgh <ruben.verborgh@ugent.be>:

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



-- 
Kévin Dunglas
Consultant et développeur freelance

http://dunglas.fr
Tél. : 06 60 91 20 20
Received on Monday, 5 January 2015 08:12:03 UTC

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