55<!ENTITY rfc3986 SYSTEM " http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml"
66<!ENTITY rfc4151 SYSTEM " http://xml.resource.org/public/rfc/bibxml/reference.RFC.4151.xml"
77<!--<!ENTITY rfc4287 SYSTEM " http://xml.resource.org/public/rfc/bibxml/reference.RFC.4287.xml"
8- <!--<!ENTITY rfc5226 SYSTEM " http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml"
98<!ENTITY rfc5789 SYSTEM " http://xml.resource.org/public/rfc/bibxml/reference.RFC.5789.xml"
109<!ENTITY rfc6068 SYSTEM " http://xml.resource.org/public/rfc/bibxml/reference.RFC.6068.xml"
1110<!ENTITY rfc6570 SYSTEM " http://xml.resource.org/public/rfc/bibxml/reference.RFC.6570.xml"
@@ -2492,9 +2491,10 @@ Link: <https://api.example.com/trees/1/nodes/456> rev=up
24922491 &rfc3986;
24932492 <!-- &rfc4287;-->
24942493 &rfc6570;
2494+ &rfc6573;
24952495 &rfc6901;
2496+ &rfc8288;
24962497 &I-D.luff-relative-json-pointer;
2497- &I-D.reschke-http-jfv;
24982498 <reference anchor =" json-schema"
24992499 <front >
25002500 <title >JSON Schema: A Media Type for Describing JSON Documents</title >
@@ -2518,15 +2518,13 @@ Link: <https://api.example.com/trees/1/nodes/456> rev=up
25182518 </references >
25192519 <references title =" Informative References"
25202520 &rfc2046;
2521- <!-- &rfc5226;-->
25222521 &rfc4151;
25232522 &rfc5789;
25242523 &rfc6068;
2525- &rfc6573;
25262524 &rfc7230;
25272525 &rfc7231;
25282526 &rfc7807;
2529- &rfc8288 ;
2527+ &I-D.reschke-http-jfv ;
25302528 </references >
25312529 <section title =" Using JSON Hyper-Schema in APIs" anchor =" apis"
25322530 <t >
0 commit comments