Skip to content

profile in Accept header must be a quoted-string #2

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
Aug 5, 2015
Merged

profile in Accept header must be a quoted-string #2

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
20 changes: 10 additions & 10 deletions jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -380,23 +380,23 @@
<t>
JSON Schema uses <xref target="json-reference">JSON Reference</xref> as a
mechanism for schema addressing. It extends this specification in two ways:

<list>
<t>JSON Schema offers facilities to alter the base URI against which a
reference must resolve by the means of the "id" keyword;</t>
<t>it offers schemas a mechanism to declare their own URIs, placing no limits on the structure of the URI</t>
</list>

</t>

<t>
Altering the URI within a schema is called defining a new resolution scope.
The initial resolution scope of a schema is the URI of the schema itself, or a suitable substitute URI if none is known.
</t>
</section>

<section title='URI resolution scope alteration with the "id" keyword'>

<section title="Valid values">
<t>
The value for this keyword MUST be a string, and MUST be a valid URI (relative or absolute).
Expand Down Expand Up @@ -455,7 +455,7 @@
Subschemas at the following URI-encoded <xref target="json-pointer">JSON
Pointer</xref>s (starting from the root schema) define the following
resolution scopes:

<list style="hanging">
<t hangText="# (document root)">http://x.y.z/rootschema.json#</t>
<t hangText="#/schema1">http://x.y.z/rootschema.json#foo</t>
Expand All @@ -465,7 +465,7 @@
<t hangText="#/schema3">some://where.else/completely#</t>
</list>
</t>

</section>

<section title="Methods for dereferencing">
Expand All @@ -474,7 +474,7 @@
This is known as "canonical referencing".
</t>
<t>
Tools MAY also take note of the URIs schemas provide for themselves using "id", and use these values for schema dereferencing as well.
Tools MAY also take note of the URIs schemas provide for themselves using "id", and use these values for schema dereferencing as well.
This is known as "inline referencing".
</t>

Expand Down Expand Up @@ -516,7 +516,7 @@
schema, and choose to use the appropriate subschema.</t>
</list>
</t>

</section>

<section title="Inline dereferencing and fragments">
Expand Down Expand Up @@ -547,7 +547,7 @@
An implementation choosing to support inline dereferencing SHOULD be able to use this kind of reference.
</t>
</section>

</section>

<section title="Interoperability considerations">
Expand Down Expand Up @@ -593,7 +593,7 @@ Link: <http://example.com/my-hyper-schema#>; rel="describedBy"
</figure>

</section>

<section title='Correlation by means of the "Content-Type" header'>
<t>
Instances may also specify a schema using the "profile" MIME type parameter in the Content-Type header, when the MIME type MUST be "application/json", or any other subtype.
Expand All @@ -608,7 +608,7 @@ Link: <http://example.com/my-hyper-schema#>; rel="describedBy"
<artwork>
<![CDATA[
Content-Type: application/my-media-type+json;
profile=http://example.com/my-hyper-schema#
profile="http://example.com/my-hyper-schema#"
]]>
</artwork>
</figure>
Expand Down
Loading