Skip to content

Commit b3c7d4f

Browse files
committed
Hyper-schema: Clarify use of "rel" property, remove Atom reference
1 parent 4011815 commit b3c7d4f

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

jsonschema-hyperschema.xml

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<!ENTITY rfc2046 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2046.xml">
55
<!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
66
<!ENTITY rfc3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
7-
<!ENTITY rfc4287 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4287.xml">
7+
<!--<!ENTITY rfc4287 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4287.xml">-->
88
<!--<!ENTITY rfc5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">-->
99
<!ENTITY rfc5988 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5988.xml">
1010
<!ENTITY rfc6570 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6570.xml">
@@ -218,7 +218,7 @@
218218
</artwork>
219219
</figure>
220220
<figure>
221-
<preamble>An example of a JSON instance using this schema to produce a rel="self" and rel="next" links</preamble>
221+
<preamble>An example of a JSON instance using this schema to produce rel="self" and rel="next" links</preamble>
222222
<artwork>
223223
<![CDATA[
224224
{
@@ -510,16 +510,15 @@
510510

511511
<section title="rel">
512512
<t>
513-
The value of the "rel" property indicates the name of the relation to the target resource.
513+
The value of the "rel" property indicates the name of the relation to the target resource. The value MUST be a registered link relation from the <xref target="RFC5988">IANA Link Relation Type Registry established in RFC 5988</xref>, or a normalized URI following the <xref target="RFC3986">URI production of RFC 3986</xref>.
514514
</t>
515515

516516
<t>
517-
The relation to the target SHOULD be interpreted as specifically from the instance object that the schema (or sub-schema) applies to, not just the top level resource that contains the object within its hierarchy.
518-
A link relation from the top level resource to a target MUST be indicated with the schema describing the top level JSON representation.
517+
The relation to the target is interpreted as from the instance that the schema (or sub-schema) applies to, not any larger document that the instance may have been found in.
519518
</t>
520519

521520
<t>
522-
Relationship definitions SHOULD NOT be media type dependent, and users are encouraged to utilize existing accepted relation definitions, including those in existing relation registries (see <xref target="RFC4287">RFC 4287</xref>).
521+
Relationship definitions are not normally media type dependent, and users are encouraged to utilize existing accepted relation definitions.
523522
</t>
524523

525524
<figure>
@@ -851,7 +850,7 @@ GET /foo/
851850
&rfc2045;
852851
&rfc2119;
853852
&rfc3986;
854-
&rfc4287;
853+
<!--&rfc4287;-->
855854
&rfc6570;
856855
<reference anchor="json-schema">
857856
<front>

0 commit comments

Comments
 (0)