|
14 | 14 | <!ENTITY rfc7231 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7231.xml">
|
15 | 15 | <!ENTITY I-D.nottingham-rfc5988bis SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-nottingham-rfc5988bis-08.xml">
|
16 | 16 | <!ENTITY I-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 |
| -<!ENTITY I-D.kelly-json-hal SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-kelly-json-hal-08.xml"> |
18 | 17 | <!ENTITY I-D.reschke-http-jfv SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-reschke-http-jfv-06.xml">
|
19 | 18 | <!ENTITY ldp SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.REC-ldp-20150226.xml">
|
20 | 19 | ]>
|
|
160 | 159 | Hyper-schemas allow representations to take up fewer bytes on the wire, and
|
161 | 160 | distribute the burden of link construction from the server to each client.
|
162 | 161 | A user agent need not construct a link unless a client application requests
|
163 |
| - that link. |
164 |
| - </t> |
165 |
| - <t> |
166 |
| - JSON Hyper-Schema can also be used on the server side to generate other |
167 |
| - link serializations at runtime, such as HTTP Link headers or |
168 |
| - <xref target="I-D.kelly-json-hal">JSON HAL</xref>. Because hyper-schema offers |
169 |
| - a superset of the features of many other systems, using it on the server |
170 |
| - can make it easier to support multiple representation media types and |
171 |
| - linking mechanisms. It is even possible to support features such as JSON HAL's |
172 |
| - embedded resources by automatically following links on the server and |
173 |
| - inlining the results. |
| 162 | + that link. JSON Hyper-Schema can also be used on the server side to generate |
| 163 | + other link serializations or representation formats at runtime, or pre-emptively |
| 164 | + follow links to faciliate server push usage. |
174 | 165 | </t>
|
175 | 166 | </section>
|
176 | 167 |
|
@@ -1248,7 +1239,6 @@ for varname in templateData:
|
1248 | 1239 | &rfc6573;
|
1249 | 1240 | &rfc7231;
|
1250 | 1241 | &I-D.nottingham-rfc5988bis;
|
1251 |
| - &I-D.kelly-json-hal; |
1252 | 1242 | &ldp;
|
1253 | 1243 | </references>
|
1254 | 1244 | <section title="JSON Hyper-Schema and HTTP" anchor="HTTP">
|
|
0 commit comments