Skip to content

Commit 0553c8b

Browse files
committed
Add a bit about conditional links
This is a common question, so make a note of it where we introduce link validity. There are some other ways of doing this like "templateRequired" which I think are already covered well enough. A higher-level guide on various techniques is, I think, outside the scope of the specification.
1 parent 7401514 commit 0553c8b

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

jsonschema-hyperschema.xml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,10 @@
215215
<t hangText="link validity">
216216
A valid link for an instance is one that is applicable to that
217217
instance and does not fail any requirement imposed by the keywords
218-
in the Link Description Object.
218+
in the Link Description Object. Note that invalid links can
219+
occur when using keywords such as "if" or "oneOf" (from the
220+
Core specification) to describe links that are conditional on
221+
the representation's structure or value.
219222
</t>
220223
<t hangText="generic user agent">
221224
A user agent which can be used to interact with any resource, from

0 commit comments

Comments
 (0)