http://www.w3.org/ns/ldp#constrainedBy

[1] Linked Data Platform 1.0 (2015-02-27 16:08:53 +09:00 版) <https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#h-ldpr-gen-pubclireqs>

4.2.1.6 LDP servers must publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with an appropriate context URI, a link relation of http://www.w3.org/ns/ldp#constrainedBy, and a target URI identifying a set of constraints [RFC5988], to all responses to requests that fail due to violation of those constraints.

[2] Web Annotation Protocol (2017-02-24 02:14:26 +09:00) <https://w3c.github.io/web-annotation/protocol/wd/#h-container-retrieval>

It must advertise that it imposes Annotation protocol specific constraints by including a link where the target IRI is http://www.w3.org/TR/annotation-protocol/, and the rel parameter value is the IRI http://www.w3.org/ns/ldp#constrainedBy.

[3] Web Annotation Protocol (2017-02-24 02:14:26 +09:00) <https://w3c.github.io/web-annotation/protocol/wd/#h-containers-for-related-resources>

Containers for related resources must support the same HTTP methods as described above for the Annotation Container, and must support identifying their type with a Link header. The constrainedBy link header on the response when dereferencing the Container should refer to a server specific set of constraints listing the types of content that are acceptable.

[4] Linked Data Notifications (2017-05-02 20:42:58 +09:00) <https://linkedresearch.org/ldn/#constraints>

Inbox URLs can announce their own constraints (e.g., SHACL, Web Annotation Protocol) via an HTTP Link header or body of the resource with a rel value of http://www.w3.org/ns/ldp#constrainedBy.