Context Specific Constraints
From Hydra Community Group
Page to capture existing conversation on this topic from which we can compile more coherent information
http://lists.w3.org/Archives/Public/public-hydra/2014Nov/0093.html
- How do you intend to (or usually) communicate constraints which aren't for
- everyone but only for users of a particular Web API.. in other words, how
- would a client find constraints that apply only in certain contexts? In
- Hydra we solve this by sending an HTTP Link header which points to a
- hydra:ApiDocumentation that contains information which is intended to be
- used only in the context of the specific request. For instance the
- constraint that the name property is obligatory for instances of
- schema:Event applies only in a specific Web API and not for all instances of
- schema:Event on the Web.
