From 4fb2af1d50c2d8fe8b1278ef38d2dbf9a7946fe6 Mon Sep 17 00:00:00 2001
From: about-code <6525873+about-code@users.noreply.github.com>
Date: Sat, 26 Sep 2020 13:00:32 +0200
Subject: [PATCH 1/2] Fix 988 (What is the  tag for the new 2019-09 draft?)

---
 jsonschema-validation.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml
index 0b28869e..722c502c 100644
--- a/jsonschema-validation.xml
+++ b/jsonschema-validation.xml
@@ -178,7 +178,7 @@
         <section title="Meta-Schema" anchor="meta-schema">
             <t>
                 The current URI for the default JSON Schema meta-schema is
-                <eref target="http://json-schema.org/draft/2019-09/schema"/>.
+                <eref target="https://json-schema.org/draft/2019-09/schema"/>.
                 For schema author convenience, this meta-schema describes all vocabularies
                 defined in this specification and the JSON Schema Core specification,
                 as well as two former keywords which are reserved for a transitional period.

From b08f1fcefd0ce92da84188aae1e350bbb1b15192 Mon Sep 17 00:00:00 2001
From: about-code <6525873+about-code@users.noreply.github.com>
Date: Sat, 26 Sep 2020 13:09:09 +0200
Subject: [PATCH 2/2] Fix inconsistencies with use of empty URI fragment

---
 jsonschema-core.xml        | 4 ++--
 jsonschema-hyperschema.xml | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/jsonschema-core.xml b/jsonschema-core.xml
index de3cda14..91c1f228 100644
--- a/jsonschema-core.xml
+++ b/jsonschema-core.xml
@@ -1916,7 +1916,7 @@
                         <figure>
                             <artwork>
         <![CDATA[
-        Link: <https://example.com/my-hyper-schema#>; rel="describedby"
+        Link: <https://example.com/my-hyper-schema>; rel="describedby"
         ]]>
                             </artwork>
                         </figure>
@@ -1962,7 +1962,7 @@
                             <artwork>
         <![CDATA[
         Content-Type: application/schema-instance+json;
-                  schema="https://example.com/my-hyper-schema#"
+                  schema="https://example.com/my-hyper-schema"
         ]]>
                             </artwork>
                         </figure>
diff --git a/jsonschema-hyperschema.xml b/jsonschema-hyperschema.xml
index f3daa676..78997685 100644
--- a/jsonschema-hyperschema.xml
+++ b/jsonschema-hyperschema.xml
@@ -282,7 +282,7 @@
         <section title="Meta-Schemas and Output Schema">
             <t>
                 The current URI for the JSON Hyper-Schema meta-schema is
-                <eref target="https://json-schema.org/draft/2019-09/hyper-schema#"/>.
+                <eref target="https://json-schema.org/draft/2019-09/hyper-schema"/>.
             </t>
             <t>
                 The current URI for this vocabulary, known as the Hyper-Schema vocabulary, is:
@@ -299,7 +299,7 @@
                 Schema, and use of this format can be declared by referencing the normative
                 link description schema as the schema for the data structure that uses the links.
                 The URI of the normative link description schema is:
-                <eref target="https://json-schema.org/draft/2019-09/links#"/>.
+                <eref target="https://json-schema.org/draft/2019-09/links"/>.
             </t>
             <t>
                 JSON Hyper-Schema implementations are free to provide output in any format.
@@ -310,7 +310,7 @@
                 It is RECOMMENDED that implementations be capable of producing output
                 in this format to facilitated testing.  The URI of the JSON Schema
                 describing the recommended output format is
-                <eref target="https://json-schema.org/draft/2019-09/output/hyper-schema#"/>.
+                <eref target="https://json-schema.org/draft/2019-09/output/hyper-schema"/>.
             </t>
             <t>
                 Updated vocabulary and meta-schema URIs MAY be published between