/
601.txt
34 lines (24 loc) · 1.56 KB
/
601.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
[FIG(quote)[
[FIGCAPTION[
[1] [CITE@en[Linked Data Platform 1.0]]
([TIME[2015-02-27 16:08:53 +09:00]] 版)
<https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#h-ldpr-gen-pubclireqs>
]FIGCAPTION]
> 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.
]FIG]
[FIG(quote)[
[FIGCAPTION[
[2] [CITE@en[Web Annotation Protocol]]
([TIME[2017-02-24 02:14:26 +09:00]])
<https://w3c.github.io/web-annotation/protocol/wd/#h-container-retrieval>
]FIGCAPTION]
> 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.
]FIG]
[FIG(quote)[
[FIGCAPTION[
[3] [CITE@en[Web Annotation Protocol]]
([TIME[2017-02-24 02:14:26 +09:00]])
<https://w3c.github.io/web-annotation/protocol/wd/#h-containers-for-related-resources>
]FIGCAPTION]
> 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.
]FIG]