search

HydraCG / Specifications

Specifications created by the Hydra W3C Community Group
Other
138 stars 26 forks source link

Naming style: camelCase or not? Plural or not? #81

Closed dunglas closed 9 years ago

dunglas commented 9 years ago

Hi,

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.

Ex:

A similar naming inconsistency appends with the plural form:

Is it intended?

RubenVerborgh commented 9 years ago

Hi @dunglas, thanks for noting this. Let's have the actual discussions on public-hydra@w3.org and use GitHub for issue status tracking. I forwarded your mail.

RubenVerborgh commented 9 years ago

This issue seems to be resolved by #14 and #27, which are implemented by #84 and #85.

lanthaler commented 9 years ago

Hi Kévin,

Some property's names follow the camelCase style and some other are all in lowercase. Ex: • entrypoint / readonly / writeonly (all in small caps) • statusCodes / supportedProperty / supportedOperation

Entrypoint is debatable.. readonly and writeonly will be replaced with readable and writable, see issue #14.

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

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