Skip to content

Fix cross-references #742

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 28, 2019
Merged

Fix cross-references #742

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions jsonschema-hyperschema.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,8 +188,8 @@
</t>
<t>
The terms "applicable" and "attached" are to be interpreted as defined in
<xref target="json-schema-validation">Section 3 of the
JSON Schema validation specification</xref>.
<xref target="json-schema">Section 3.1 of the
JSON Schema core specification</xref>.
</t>
<t>
The terms "link", "link context" (or "context"), "link target" (or "target"),
Expand Down Expand Up @@ -329,8 +329,8 @@
<section title="Schema Keywords">
<t>
Hyper-schema keywords from all schemas that are applicable to a position
in an instance, as defined by <xref target="json-schema-validation">Section
3 of JSON Schema validation</xref>, can be used with that instance.
in an instance, as defined by <xref target="json-schema">Section
3.1 of JSON Schema core</xref>, can be used with that instance.
</t>
<t>
When multiple subschemas are applicable to a given sub-instance, all "link"
Expand Down Expand Up @@ -401,8 +401,8 @@
<t>
In JSON Hyper-Schema, the link's context resource is, by default, the
sub-instance to which it is attached (as defined by
<xref target="json-schema-validation">Section 3 of the JSON Schema
validation specification</xref>). This is often not the entire instance
<xref target="json-schema">Section 3.1 of the JSON Schema
core specification</xref>). This is often not the entire instance
document. This default context can be changed using the keywords
in this section.
</t>
Expand Down Expand Up @@ -1364,7 +1364,7 @@ for varname in templateData:
describing possible HTTP request headers that are relevant to the given resource.
</t>
<t>
<xref target="json-schema">Section 11 of the JSON Schema core specification</xref>
<xref target="json-schema">Section 13 of the JSON Schema core specification</xref>
provides guidance on linking instances in a hypermedia system to their schemas.
This may be done with network-accessible schemas, or may simply identify schemas
which were pre-packaged within the client application. JSON Hyper-Schema
Expand Down
4 changes: 2 additions & 2 deletions jsonschema-validation.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,7 @@
</t>
</section>

<section title="enum">
<section title="enum" anchor="enum">
<t>
The value of this keyword MUST be an array. This array SHOULD have at
least one element. Elements in the array SHOULD be unique.
Expand All @@ -263,7 +263,7 @@
</t>
<t>
Use of this keyword is functionally equivalent to an
<xref target="json-schema">"enum"</xref> with a single value.
<xref target="enum">"enum"</xref> with a single value.
</t>
<t>
An instance validates successfully against this keyword if its value is
Expand Down