Closed lanthaler closed 5 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.
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.
PROPOSAL: The most important thing is to be consistent. Typos like these are also quite easy to detect automatically, do nothing.
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.
If the properties are changed to singular, even more properties will differ from their ranges only in their capitalization:
Do we want to avoid that (as Schema.org does for example)?