Should properties and types that only differ in their capitalization be avoided?

HydraCG / Specifications

Specifications created by the Hydra W3C Community Group

Other

139 stars 25 forks source link

Should properties and types that only differ in their capitalization be avoided? #28

Closed lanthaler closed 5 years ago

lanthaler commented 10 years ago

If the properties are changed to singular, even more properties will differ from their ranges only in their capitalization:

hydra:apiDocumentation -> hydra:ApiDocumentation

hydra:operation -> hydra:Operation
hydra:supportedProperty -> hydra:SupportedProperty

Do we want to avoid that (as Schema.org does for example)?

gkellogg commented 10 years ago

Alternatively:

hydra:hasApiDocumentation -> hydra:ApiDocumentation

hydra:hasOperation -> hydra:Operation
hydra:hasSupportedProperty -> hydra:SupportedProperty

which has some precedent in other vocabularies and removes case confusion.

RubenVerborgh commented 10 years ago

While the has option is valid, I don't think there is a need to make property names longer. The names could be left as they are, I think. If you want to change, here are suggestions:

hydra:documentedBy with range hydra:ApiDocumentation
hydra:supportsOperation with range hydra:Operation
hydra:supportsProperty with range hydra:SupportedProperty

One could question the need for Supported with Property, when seeing the above.

lanthaler commented 10 years ago

PROPOSAL: The most important thing is to be consistent. Typos like these are also quite easy to detect automatically, do nothing.

alien-mcl commented 5 years ago

This seems to be resolved with no further actions required. I believe changing names of core elements after several years would do more harm than good. I think it's OK to close it without any changes in the spec.