You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: jsonschema-hyperschema.xml
+4-16Lines changed: 4 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,6 @@
15
15
<!ENTITYI-D.nottingham-rfc5988bis SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-nottingham-rfc5988bis-08.xml">
16
16
<!ENTITYI-D.luff-relative-json-pointer SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-luff-relative-json-pointer-00.xml">
17
17
<!ENTITYI-D.reschke-http-jfv SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-reschke-http-jfv-06.xml">
18
-
<!ENTITYldp SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.REC-ldp-20150226.xml">
19
18
]>
20
19
<?rfc toc="yes"?>
21
20
<?rfc symrefs="yes"?>
@@ -1257,7 +1256,6 @@ for varname in templateData:
1257
1256
&rfc6573;
1258
1257
&rfc7231;
1259
1258
&I-D.nottingham-rfc5988bis;
1260
-
&ldp;
1261
1259
</references>
1262
1260
<sectiontitle="JSON Hyper-Schema and HTTP"anchor="HTTP">
1263
1261
<t>
@@ -1300,8 +1298,8 @@ for varname in templateData:
1300
1298
<t>
1301
1299
The relationship between a resource's representation and HTTP requests and
1302
1300
responses is determined by <xreftarget="RFC7231">RFC 7231, section 4.3.1 -
1303
-
"GET", section 4.3.4 "PUT", and section 3.1.4.2,
1304
-
"Content-Location"</xref>. In particular, "targetSchema" suggests what a
1301
+
"GET", section 4.3.4 "PUT", and section 3.1.4.2, "Content-Location"</xref>.
1302
+
In particular, "targetSchema" suggests what a
1305
1303
client can expect for the response to an HTTP GET or any response for which
1306
1304
the "Content-Location" header is equal to the request URI, and what a client
1307
1305
should send if it replaces the resource in an HTTP PUT request.
@@ -1318,25 +1316,15 @@ for varname in templateData:
1318
1316
</t>
1319
1317
<t>
1320
1318
HTTP POST requests are determined by the "submissionSchema" and
1321
-
"submissionMediaType" fields. Alternatively, the "Accept-Post" header has
1322
-
been defined and registered by the
1323
-
<xreftarget="W3C.REC-ldp-20150226">Linked Data Platform</xref>, and MAY be
1319
+
"submissionMediaType" fields. Additionally, the "Accept-Post" header
1320
+
can be used to specify the necessary media type, and MAY be
1324
1321
advertised via the "targetHints" field.
1325
1322
<cref>
1326
1323
What happens if both are used? Also, "submissionSchema" is a MUST
1327
1324
to support, while "targetHints" are at most a SHOULD. But forbidding
1328
1325
the use of "Accept-Post" in "targetHints" seems incorrect.
1329
1326
</cref>
1330
1327
</t>
1331
-
<!-- targetMediaType and "Accept"
1332
-
<t>
1333
-
If this property's value is specified, and the link's target is to be obtained
1334
-
using any protocol that supports the HTTP/1.1 "Accept" header
1335
-
<xref target="RFC7231">RFC 7231, section 5.3.2</xref>, then user agents MAY use
1336
-
the value of this property to aid in the assembly of that header when making the
1337
-
request to the server.
1338
-
</t>
1339
-
-->
1340
1328
</section>
1341
1329
<sectiontitle='Optimizing HTTP discoverability with "targetHints"'>
0 commit comments