Merge branch 'master' of github.com:json-schema-org/json-schema-spec into aaa-uri-fix

Author: awwright

jsonschema-core.xml

@@ -382,23 +382,22 @@
                 <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
                         URI 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>
                     <!-- TODO: RFC3986 defines exactly how to do this -->
                     The initial base URI of a schema is the URI of the schema itself, or a suitable substitute URI if none is known.
                 </t>
             </section>
 
             <section title='Base URI 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-reference [RFC3986].
@@ -458,7 +457,7 @@
                             <t hangText="#/schema3">urn:uuid:ee564b8a-7a87-4125-8c96-e9f123d6766f</t>
                         </list>
                     </t>
-    
+
                 </section>
 
                 <section title="Methods for dereferencing">
@@ -467,7 +466,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>
 
@@ -509,13 +508,13 @@
                             schema, and choose to use the appropriate subschema.</t>
                         </list>
                     </t>
-                                
+
                 </section>
 
                 <section title="Inline dereferencing and fragments">
                     <t>
                         When using inline dereferencing, a base URI may lead to a URI which
-                        has a non empty fragment part which is not a JSON Pointer, as in this
+                        has a non-empty fragment part which is not a JSON Pointer, as in this
                         example:
                     </t>
 
@@ -540,7 +539,7 @@
                         An implementation choosing to support inline dereferencing SHOULD be able to use this kind of reference.
                     </t>
                 </section>
-                    
+
             </section>
 
             <section title="Interoperability considerations">
@@ -587,7 +586,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.
@@ -602,7 +601,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>