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: draft-zyp-json-schema-03.xml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -551,7 +551,7 @@ The value of the "rel" property indicates the name of the
551
551
relation to the target resource. 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. If a resource JSON representation contains a sub object with a property interpreted as a link, that sub-object holds the relation with the target. A relation to target from the top level resource MUST be indicated with the schema describing the top level JSON representation.
552
552
</t>
553
553
<t>
554
-
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 <xreftarget='RFC4287'>RFC 4287</xref>). However, we define these relation here for clarity of normative interpretation within the context of JSON hyper schema defined relations:
554
+
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 <xreftarget='RFC4287'>RFC 4287</xref>). However, we define these relations here for clarity of normative interpretation within the context of JSON hyper schema defined relations:
555
555
<liststyle="hanging">
556
556
<thangText="self">
557
557
If the relation value is "self", when this property is encountered in
@@ -625,7 +625,7 @@ GET /Resource/
625
625
]]></artwork>
626
626
</figure>
627
627
628
-
This would indicate that for the first item in the collection, it's own
628
+
This would indicate that for the first item in the collection, its own
629
629
(self) URI would resolve to "/Resource/thing" and the first item's "up"
630
630
relation SHOULD be resolved to the resource at "/Resource/parent".
631
631
The "children" collection would be located at "/Resource/?upId=thing".
@@ -971,7 +971,7 @@ instead of numbers</t>
971
971
<liststyle="symbols">
972
972
<t>Replaced "maxDecimal" attribute with "divisibleBy" attribute.</t>
973
973
<t>Added slash-delimited fragment resolution protocol and made it the default.</t>
974
-
<t>Added language about using links outside of schemas by referencing it's normative URI.</t>
974
+
<t>Added language about using links outside of schemas by referencing its normative URI.</t>
975
975
<t>Added "uniqueItems" attribute.</t>
976
976
<t>Added "targetSchema" attribute to link description object.</t>
0 commit comments