Ideas for additional features/vocabularies

HydraCG / Specifications

Specifications created by the Hydra W3C Community Group

Other

139 stars 25 forks source link

Ideas for additional features/vocabularies #20

Closed lanthaler closed 5 years ago

lanthaler commented 10 years ago

[ ] Allow the documentation of sample requests/responses, can be used to build mock services and to improve documentation. This should probably not be part of the core vocabulary.
[ ] Create separate vocabulary for CRUD applications
[ ] More advanced querying

elf-pavlik commented 10 years ago

i would like to add way to negotiate vocabularies... one could offer/request FOAF or Schema.org version of same resource foaf:Person || schema:Person, similar with gr:Offer || schema:Offer

akuckartz commented 10 years ago

@elf-pavlik negotiating vocabularies is an interesting suggestion. Is that already done anywhere else?

lanthaler commented 10 years ago

Thomas Hoppe said on the mailing list:

I suggest this as a staring point [for a CRUD vocabulary]:

GET RetrieveResourceOperation POST AppendResourceOperation (ID is generated and not provided in the POSTed data) PUT CreateOrReplaceOperation (ID is provided within the PUTed data) PATCH UpdateResourceOperation (Single or multiple property updates) DELETE DeleteResourceOperation

The given HTTP actions are not a strict mapping but merely a "best fit" suggestion how they could map to the operations. There is also a corresponding discussion on SO. The operations itself should be self explaining.

alien-mcl commented 5 years ago

Due to lack of activity in this issue, I'd like to close it. Still, whole this GitHub repo is a great place for suggesting features!