diff --git a/jsonschema-core.xml b/jsonschema-core.xml index c42d9b34..b63d54db 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -2,12 +2,12 @@ - + ]> @@ -673,7 +673,7 @@ JSON has been adopted widely by HTTP servers for automated APIs and robots. This section describes how to enhance processing of JSON documents in a more RESTful manner when used with protocols that support media types and - Web linking. + Web linking.
@@ -685,7 +685,7 @@ In HTTP, such links can be attached to any response using the - Link header. An example of such a header would be: + Link header. An example of such a header would be:
@@ -924,9 +924,9 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0 - &RFC5988; &RFC7049; &RFC7231; + &RFC8288; &fragid-best-practices; diff --git a/jsonschema-hyperschema.xml b/jsonschema-hyperschema.xml index 4d7b4935..afb02e10 100644 --- a/jsonschema-hyperschema.xml +++ b/jsonschema-hyperschema.xml @@ -7,7 +7,6 @@ - @@ -15,7 +14,7 @@ - + ]> @@ -95,11 +94,7 @@ The primary mechanism introduced for specifying links is the Link Description Object (LDO), which is a serialization of the abstract link model - defined in RFC 5988bis, section 2. - - This section references the work-in-progress RFC5988bis, with the expectation - that it will reach RFC before this specification does. - + defined in RFC 8288, section 2. This specification will use the concepts, syntax, and terminology defined by the @@ -163,7 +158,7 @@ The terms "link", "link context" (or "context"), "link target" (or "target"), and "target attributes" are to be interpreted as defined in - Section 2 of RFC 5988bis. + Section 2 of RFC 8288. The term "user agent" is to be interpreted as defined in @@ -224,7 +219,7 @@ A JSON Hyper-Schema implementation is able to take a hyper-schema, an instance, and in some cases client input, and produce a set of fully resolved valid links. As defined by - RFC 5988bis, section 2, + RFC 8288, section 2, a link consists of a context, a typed relation, a target, and optionally additional target attributes. @@ -327,12 +322,8 @@
- - This section references the work-in-progress RFC5988bis, with the expectation - that it will reach RFC before this specification does. - A Link Description Object (LDO) is a serialization of the abstract link model - defined in RFC 5988bis, section 2. + defined in RFC 8288, section 2. As described in that document, a link consists of a context, a relation type, a target, and optionally target attributes. JSON Hyper-Schema's LDO provides all of these, along with additional features using JSON Schema to describe input @@ -439,7 +430,7 @@
The value of this property MUST be a string, and MUST be a single - Link Relation Type as defined in RFC 5988bis, Section 2.1. + Link Relation Type as defined in RFC 8288, Section 2.1. This property is required. @@ -492,7 +483,7 @@ When no registered relation (aside from "related") applies, users are encouraged to mint their own extension relation types, as described in - section 4.2 of RFC 5988. The simplest + section 2.1.2 of RFC 8288. The simplest approaches for choosing link relation type URIs are to either use a URI scheme that is already in use to identify the system's primary resources, or to use a human-readable, non-dereferenceable URI scheme @@ -2238,13 +2229,12 @@ Link: rel=describedBy &rfc4151; &rfc5789; - &rfc5988; &rfc6068; &rfc6573; &rfc7230; &rfc7231; &rfc7807; - &I-D.nottingham-rfc5988bis; + &rfc8288;
@@ -2331,7 +2321,7 @@ Link: rel=describedBy Top to bottom reorganization and rewrite - Group keywords per RFC 5988bis context/relation/target/target attributes + Group keywords per RFC 8288 context/relation/target/target attributes Additional keyword groups for template resolution and describing input Added section on general implementation requirements Expanded overview to provide context