search

HydraCG / Specifications

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

Implement “remove predefined operations” #86

Closed RubenVerborgh closed 7 years ago

RubenVerborgh commented 9 years ago

This pull request partially addresses #11 by removing the predefined operations from the vocabulary. However, I need some input to finalize this.

  1. Should hydra:Operation be removed/replaced? And if so, what about hydra:supportedOperation, hydra:operation, hydra:method, hydra:expects, hydra:returns?
  2. In the specification document, should we remove explanations about CreateResourceOperation, ReplaceResourceOperation and DeleteResourceOperation? Or should we, as suggested in #11, replace them by Schema.org explanations? The latter, however, need not necessarily be part of the spec.

As a temporary resolution for the second point, I propose to remove. We can always add explanations later (but perhaps already create an issue for that then).

luchsamapparat commented 8 years ago

Hi,

is there any roadmap on when to expect this Change? I'm currently exploring Hydra and I'm unsure how to proceed

tpluscode commented 7 years ago

@RubenVerborgh Why do you propose removing hydra:Operation and others? Following this comment in #2 I think that operations do have their place describing HTTP protocol and actions being used in API-specific terms.

For second point, I think it may be good to actually add schema actions as illustrations of suggested usage.

RubenVerborgh commented 7 years ago

@tpluscode I think the question should be the other way round: why do we need them? As announced on the mailing list, I'd like to take a step back and start with a clean slate from the lessons we learned. It might well be that we need something like operation.

(Sketching a proposed architectural diagram as we speak, I expect to send this out today.)

RubenVerborgh commented 7 years ago

Architectural diagram (draft)

lanthaler commented 7 years ago

I'm fine with removing CreateResourceOperation, ReplaceResourceOperation, and DeleteResourceOperation. I agree with @tpluscode that we will likely need hydra:Operation etc. Should we proceed with merging this PR and discuss the rest separately?

Unless I hear objections, I'll merge this PR on the weekend (we previously agreed to delete them in #11).

asbjornu commented 7 years ago

👍 for deleting the concrete operations while keeping the generic hydra:Operation.