search

HydraCG / Specifications

Specifications created by the Hydra W3C Community Group
Other
139 stars 25 forks source link

Remove predefined operations from the core vocabulary. #11

Closed lanthaler closed 7 years ago

lanthaler commented 10 years ago

There have been some discussions about the use and consistency of the pre-defined operations (CreateResourceOperation, ReplaceResourceOperation, and DeleteResourceOperation).

The only reason they have been defined was to help developers to get started. This may not be a strong enough argument to keep the in the core vocabulary.

RubenVerborgh commented 10 years ago

I would personally start the other way round. Instead of arguing keep/remove, let's first see what we want to achieve. What do we want clients to be able to do? AKA What affordances do we want to give them—bearing in mind that they need more explicit affordances than humans?

Based on that, we can check whether or not the operations help in achieving that.

lanthaler commented 10 years ago

The outcome of this issue affects #4

lanthaler commented 10 years ago

PROPOSAL: Remove all *ResourceOperations by replacing them with their schema.org counterparts CreateAction (CreateResourceOperation), DeleteAction (DeleteResourceOperation), ReplaceAction (ReplaceResourceOperation). As Schema.org now has a more or less complete Action model, describe in more detail how it can be used with Hydra.

cdchapman commented 10 years ago

:+1:

lanthaler commented 10 years ago

Call for consensus: http://lists.w3.org/Archives/Public/public-hydra/2014Jul/0078.html

lanthaler commented 10 years ago

RESOLVED: Do not introduce RetrieveResourceOperation and remove other Operation types.