Skip to content

Commit e1d1290

Browse files
committed
Discuss connecting instances and hyper-schemas
Mostly just refer to the core spec and note that there are many approaches depending on the use case and environmental constraints.
1 parent bf580f3 commit e1d1290

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

jsonschema-hyperschema.xml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1302,6 +1302,15 @@ for varname in templateData:
13021302
Additionally, guidance is provided on hinting at HTTP response header values and
13031303
describing possible HTTP request headers that are relevant to the given resource.
13041304
</t>
1305+
<t>
1306+
<xref target="json-schema">Section 11 of the JSON Schema core specification</xref>
1307+
provides guidance on linking instances in a hypermedia system to their schemas.
1308+
This may be done with network-accessible schemas, or may simply identify schemas
1309+
which were pre-packaged within the client application. JSON Hyper-Schema
1310+
intentionally does not constrain this mechanism, although it is RECOMMENDED that
1311+
the techniques outlined in the core specification be used to whatever extent
1312+
is possible.
1313+
</t>
13051314
<section title="One link per target and relation type">
13061315
<t>
13071316
Link Description Objects do not directly indicate what operations, such

0 commit comments

Comments
 (0)