json-schema-org
diff --git a/‎pages/_document.page.tsx
Lines changed: 1 addition & 1 deletion b/‎pages/_document.page.tsx
Lines changed: 1 addition & 1 deletion
diff --git a/‎pages/blog/posts/6-river-systems-case-study.md
Lines changed: 3 additions & 3 deletions b/‎pages/blog/posts/6-river-systems-case-study.md
Lines changed: 3 additions & 3 deletions
diff --git a/‎pages/blog/posts/and-then-there-were-three.md
Lines changed: 1 addition & 1 deletion b/‎pages/blog/posts/and-then-there-were-three.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎pages/blog/posts/applicability-json-schema-fundamentals-part-1.md
Lines changed: 5 additions & 6 deletions b/‎pages/blog/posts/applicability-json-schema-fundamentals-part-1.md
Lines changed: 5 additions & 6 deletions
diff --git a/‎pages/blog/posts/bowtie-intro.md
Lines changed: 4 additions & 3 deletions b/‎pages/blog/posts/bowtie-intro.md
Lines changed: 4 additions & 3 deletions
diff --git a/‎pages/blog/posts/bundling-json-schema-compound-documents.md
Lines changed: 1 addition & 1 deletion b/‎pages/blog/posts/bundling-json-schema-compound-documents.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎pages/blog/posts/code-of-conduct-for-json-schema.md
Lines changed: 2 additions & 2 deletions b/‎pages/blog/posts/code-of-conduct-for-json-schema.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎pages/blog/posts/custom-annotations-will-continue.md
Lines changed: 2 additions & 2 deletions b/‎pages/blog/posts/custom-annotations-will-continue.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎pages/blog/posts/hello-2023--hello-json-schema-community.md
Lines changed: 2 additions & 2 deletions b/‎pages/blog/posts/hello-2023--hello-json-schema-community.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎pages/blog/posts/hello-world-hello-postman.md
Lines changed: 1 addition & 1 deletion b/‎pages/blog/posts/hello-world-hello-postman.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎pages/blog/posts/hyperborea.md
Lines changed: 1 addition & 1 deletion b/‎pages/blog/posts/hyperborea.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎pages/blog/posts/interpreting-output.md
Lines changed: 2 additions & 2 deletions b/‎pages/blog/posts/interpreting-output.md
Lines changed: 2 additions & 2 deletions
@@ -16,7 +16,7 @@ class MyDocument extends Document {
           <link href='https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700;900&family=JetBrains+Mono:wght@300;400&display=swap' rel='stylesheet' />
           <link rel='stylesheet' href='https://cdn.jsdelivr.net/npm/@docsearch/css@3' />
         </Head>
-        <body className='w-screen relative'>
+        <body className='relative'>
           <Main />
           <NextScript />
         </body>
 
@@ -6,10 +6,10 @@ cover: /img/posts/2023/6-river-systems-case-study/cover.webp
 authors:
   - name: Melinda Gutermuth
     photo: /img/avatars/melinda.webp
-    link: https://twitter.com/shelikeswords
+    link: https://www.twitter.com/shelikeswords
   - name: Ben Hutton
     photo: /img/avatars/benhutton.webp
-    link: https://twitter.com/relequestual
+    link: https://www.twitter.com/relequestual
 excerpt: "Explore the powerful impact of JSON Schema on 6 River Systems' fulfillment operations. Discover how they enabled enhanced collaboration, time savings, and data quality assurance, propelling their successful scaling journey."
 ---
 
@@ -113,4 +113,4 @@ While 6 River Systems had previously used JSON Schema in a number of areas acros
 
 Thank you to [Jacob Thomas](https://www.linkedin.com/in/jake-thomas/) and 6 River Systems for enabling us to share this case study with you.
 
-Images used with permission.
+Images used with permission.
@@ -72,4 +72,4 @@ I'm really excited about the opportunity that Postman has given me to work full
 
 Thank you to everyone I've met on this journey, used my libraries, asked questions, contributed code, or just offered opinions!  I love being a part of this community!
 
-Cover photo by me 😁
+Cover photo by me 😁
@@ -8,7 +8,7 @@ cover: /img/posts/2022/fundamentals-part-1/cover.webp
 authors:
   - name: Ben Hutton
     photo: /img/avatars/benhutton.webp
-    link: https://twitter.com/relequestual
+    link: https://www.twitter.com/relequestual
     byline: JSON Schema Specification Lead @Postman
 excerpt: "We explore the fundamental JSON Schema concepts: Applicability, Subschemas, and Assertion Boolean Logic - Everyone needs good fundamentals."
 ---
@@ -31,7 +31,7 @@ The validation process for JSON Schema begins with applying the whole JSON Schem
 A JSON Schema may be a Boolean or an Object. In the introductory article mentioned above, we noted how a Boolean Schema of `true` or `false` resulted in the same assertion result (true and false respectivly) regardless of the instance data. We also noted how the equivalent Object Schemas were `{ }` and `{ "not": { } }` respectively. (The `not` keyword inverts the assertion result.)
 
 <div className="bg-blue-200 border-l-4 border-blue-500 px-4 py-1 relative text-blue-700">
-  <p className="font-bold"><svg className="w-6 h-6 mr-2 float-left mt-0" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20" fill="currentColor"><path fillRule="evenodd" d="M18 10a8 8 0 11-16 0 8 8 0 0116 0zm-8-3a1 1 0 00-.867.5 1 1 0 11-1.731-1A3 3 0 0113 8a3.001 3.001 0 01-2 2.83V11a1 1 0 11-2 0v-1a1 1 0 011-1 1 1 0 100-2zm0 8a1 1 0 100-2 1 1 0 000 2z" clipRule="evenodd" /></svg>Vocabulary check</p>
+  <p className="font-bold"><svg className="w-6 h-6 mr-2 float-left mt-0" xmlns="https://www.w3.org/2000/svg" viewBox="0 0 20 20" fill="currentColor"><path fillRule="evenodd" d="M18 10a8 8 0 11-16 0 8 8 0 0116 0zm-8-3a1 1 0 00-.867.5 1 1 0 11-1.731-1A3 3 0 0113 8a3.001 3.001 0 01-2 2.83V11a1 1 0 11-2 0v-1a1 1 0 011-1 1 1 0 100-2zm0 8a1 1 0 100-2 1 1 0 000 2z" clipRule="evenodd" /></svg>Vocabulary check</p>
   <p>An "assertion" is a statement of fact. This is used in reference to the result of testing in Computing. The test might be called "X is 1". If the test passes, the assertion is true!</p>
 </div>
 
@@ -394,7 +394,7 @@ When you apply the second subschema in `oneOf` to the instance, there are no con
 
 We can use the same approach as before to make sure our subschemas have sufficient constraints. <a href="https://jsonschema.dev/s/Cbcss" target="_blank">Give it a try</a>, and see if you can manage to make the validation work as expected.
 
-The link is pre-loaded with your starting Schema and instance. Let me know if you get stuck via <a href="/slack" target="_blank">Slack</a> or <a href="https://twitter.com/relequestual" target="_blank">Twitter</a>.
+The link is pre-loaded with your starting Schema and instance. Let me know if you get stuck via <a href="/slack" target="_blank">Slack</a> or <a href="https://www.twitter.com/relequestual" target="_blank">Twitter</a>.
 
 # In summary
 
@@ -412,7 +412,7 @@ I've really enjoyed being able to share the first of our fundamentals series wit
 
 You can find all of the example instances and schemas in the <a href="https://github.com/Relequestual/json-schema-fundamentals" target="_blank">JSON Schema Fundamentals repo</a>.
 
-All feedback is welcome. If you have questions or comments, you can find me on the <a href="/slack" target="_blank">JSON Schema Slack</a> or reach out to me on Twitter <a href="https://twitter.com/relequestual" target="_blank">@relequestual</a>.
+All feedback is welcome. If you have questions or comments, you can find me on the <a href="/slack" target="_blank">JSON Schema Slack</a> or reach out to me on Twitter <a href="https://www.twitter.com/relequestual" target="_blank">@relequestual</a>.
 
 # Useful links and further reading
 
@@ -430,5 +430,4 @@ All feedback is welcome. If you have questions or comments, you can find me on t
 - [JSON Schema live playground (hyperjump validator) for all drafts (from draft-04)](https://json-schema.hyperjump.io)
 - [Links to RFC specification documents](/specification)
 
-
-Photo by [Heidi Fin](https://unsplash.com/@heidijfin?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)
+Photo by Heidi Fin on [Unsplash](https://unsplash.com/?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)
@@ -45,7 +45,7 @@ Bowtie attempts to bring these ideas to JSON Schema.
 
 From the existing [list of JSON Schema implementations](https://json-schema.org/implementations.html#validators), Bowtie already [supports](https://github.com/orgs/bowtie-json-schema/packages) *12* implementations across *9* programming languages, allowing anyone to run any of these implementations and see what they have to say about schemas and instances.
 
-It ships with a [command line program](https://bowtie-json-schema.readthedocs.io/en/latest/cli/), but perhaps more excitingly, ongoing automated runs of this CLI have been set up, such that Bowtie emits a [report across all of its supported implementations](https://bowtie-json-schema.github.io/bowtie/draft2020).
+It ships with a [command line program](https://docs.bowtie.report/en/stable/cli/) but perhaps more excitingly, ongoing automated runs of this CLI have been set up, such that Bowtie emits a [report across all of its supported implementations](https://bowtie.report).
 
 To produce this report, Bowtie runs the [official JSON Schema Test Suite](https://github.com/json-schema-org/JSON-Schema-Test-Suite), which is our existing set of tests meant to exercise compliance with the JSON Schema specifications.
 Many implementations already [use the suite within their own continuous integration](https://github.com/json-schema-org/JSON-Schema-Test-Suite#who-uses-the-test-suite), but this is the first time both users of JSON Schema as well as implementers can see results of running the suite in a single place, across many implementations.
@@ -76,7 +76,7 @@ The medium-term goal is to combine these onto one unified report (at which point
 
 If you want to go beyond the test suite reports, you can run Bowtie locally as well, on whatever input you'd like.
 Bowtie is written in Python and published [on PyPI](https://pypi.org/project/bowtie-json-schema/).
-If you have no existing preferred setup for installing Python applications, [install `pipx` using the platform-specific instructions for your OS](https://pypa.github.io/pipx/#install-pipx), then run:
+If you have no existing preferred setup for installing Python applications, [install `pipx` using the platform-specific instructions for your OS](https://pipx.pypa.io/stable/), then run:
 
 ```sh
 $ pipx install bowtie-json-schema
@@ -146,7 +146,7 @@ This is probably the most beneficial area you can help in.
 I myself am not a frontend developer, in case that wasn't obvious.
 What I put together (with Bootstrap) is essentially the bare minimum of what's needed to show off results Bowtie emits.
 If you have more experience or headspace to think about how to effectively report test results, or compare implementations, please help!
-All of Bowtie's "frontend code" today lives in one place, [a Jinja2 template which gets formatted into a static single page site](https://github.com/bowtie-json-schema/bowtie/blob/main/bowtie/templates/report.html.j2).
+All of Bowtie's "frontend code" today lives in one place, [a Jinja2 template which gets formatted into a static single page site](https://github.com/bowtie-json-schema/bowtie/blob/b23644eb86cf9bcbdf1d98149cf3d976339f7cdf/bowtie/templates/report.html.j2).
 Beyond generally "make it prettier, more responsive, or more usable", here are a few specific issues to look at:
 
 * [Add client-side filtering and sorting](https://github.com/bowtie-json-schema/bowtie/issues/37)
@@ -173,6 +173,7 @@ Bowtie also allows for a wider range of `$ref`-related testing, because its prot
 [This issue](https://github.com/bowtie-json-schema/bowtie/issues/61) is the relevant one, but ideas are welcome here on kinds of tests we can now add.
 
 #### I Found a Bug, or Have an Idea for Bowtie Itself
+
 If it's with an implementation, you likely should take it to the implementation's issue tracker.
 Please be polite, as there's still a small but non-zero chance that issues are caused by Bowtie itself.
 And even if there isn't, please do be kind to maintainers, many (including myself!) are already aware of issues Bowtie is flagging and may really want to fix them but have things which make doing so difficult.
 
@@ -269,7 +269,7 @@ The astute among you might have noticed that Compound Documents may not be corre
 
 If you’d like a more in-depth look at edge case situations, please do let us know.
 
-You can reach out to us [@jsonschema](https://twitter.com/jsonschema) or our [Slack server](/slack).
+You can reach out to us [@jsonschema](https://www.twitter.com/jsonschema) or our [Slack server](/slack).
 
 *I hope you’ll agree, Ben has clarified the process for us all here, and we can use this example to fully meet JSON Schema’s bundling expectations when writing tools which bundle multiple resources into compound OpenAPI documents. Thanks, Ben!* - Mike
 
 
@@ -97,8 +97,8 @@ Second is our [Open Community Working Meetings](https://github.com/json-schema-o
 
 Both sets of calls are open for anyone to join. Both are recorded, but only the Open Community Working Meeting is shared publicly. The Office Hours session is not shared, hopefully allowing people to speak more freely.
 
-Besides Slack, GitHub Discussions, and regular meetings, we do make use of Twitter. You can find me running the [@jsonschema account](https://twitter.com/jsonschema). Any mention of "JSON Schema" feeds into a channel on Slack, so we see most of the discussion, and can lend a hand or point people in a direction as appropriate.
+Besides Slack, GitHub Discussions, and regular meetings, we do make use of Twitter. You can find me running the [@jsonschema account](https://www.twitter.com/jsonschema). Any mention of "JSON Schema" feeds into a channel on Slack, so we see most of the discussion, and can lend a hand or point people in a direction as appropriate.
 
 Hopefully, this has been a helpful look at why JSON Schema specifically needs a Code of Conduct. Maybe you're considering if your project needs a Code of Conduct. If you have any questions, thoughts, or comments as a result of this article, please feel free to use any of the above methods to make contact.
 
-Image by <a href="https://pixabay.com/users/broesis-5213623/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=2366955">Maike und Björn Bröskamp</a> from <a href="https://pixabay.com/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=2366955">Pixabay</a>
+Image by <a href="https://pixabay.com/users/broesis-5213623/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=2366955">Maike und Björn Bröskamp</a> from <a href="https://pixabay.com/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=2366955">Pixabay</a>
@@ -13,7 +13,7 @@ authors:
 excerpt: "Custom annotations are one of JSON Schemas most-used features.  Here's how we're still supporting them."
 ---
 
-[Last time](./the-last-breaking-change), I wrote about how we had to remove support for unknown keywords.  I ended that post with a note saying that we were still searching for a way that we can support non-functional custom keywords, that is, simple annotations.
+[Last time](the-last-breaking-change), I wrote about how we had to remove support for unknown keywords.  I ended that post with a note saying that we were still searching for a way that we can support non-functional custom keywords, that is, simple annotations.
 
 In this post, I'd like to review the solution and how we came to it, as well as a brief overview of some of the other solutions we dreamed up and were offered.  Buckle up, 'cause it's gonna be a mild ride!
 
@@ -43,7 +43,7 @@ This option actually builds on the one we selected by defining a new Core keywor
 
 It was pointed out, however, that in order for a schema to be validated by the meta-schema, the meta-schema would need to be able to read this new keyword to get the prefix so that it could ignore the keywords that started with it.  This requires a whole lot of new mechanisms that we don't currently have in JSON Schema, so it's not very practical at this time.
 
-We also noted that we couldn't figure out what the scope of this keyword would be.  Would it be only the schema resource (indicated by `$id`) where the keyword was used?  Would it be the whole document?  What if we `$ref` to another schema resource or document that doesn't define a prefix?  There's a balance somewhere between inferring intent and requiring too much repetition. 
+We also noted that we couldn't figure out what the scope of this keyword would be.  Would it be only the schema resource (indicated by `$id`) where the keyword was used?  Would it be the whole document?  What if we `$ref` to another schema resource or document that doesn't define a prefix?  There's a balance somewhere between inferring intent and requiring too much repetition.
 
 ### Alternative #2 - Listing the custom keywords to ignore in a new keyword
 
 
@@ -35,8 +35,8 @@ If you like to know more about me, check out [this intro post](https://www.twili
 2023 will be a fantastic year for JSON Schema, and I am excited to be part of this journey with all of you! I can't wait to start connecting with you in the upcoming [working meetings](https://github.com/json-schema-org/community/discussions/35), in [Slack](https://json-schema.org/slack), and [Github](https://github.com/orgs/json-schema-org/discussions).
 
 >* Email: [email protected]
->* Twitter: [@benjagm](https://twitter.com/benjagm)
+>* Twitter: [@benjagm](https://www.twitter.com/benjagm)
 >* Linkedin: [benjagranados](https://www.linkedin.com/in/benjagranados/)
 >* Github: [benjagm](https://github.com/benjagm)
 
-Cover photo by [Jai Cano](https://www.jaicano.com/redes) on [Instagram](https://www.instagram.com/jaicano).
+Cover photo by [Jai Cano](https://www.jaicano.com/redes) on [Instagram](https://www.instagram.com/jaicano).
@@ -20,7 +20,7 @@ If you're a user of JSON Schema, you may know me as the author of [a popular Pyt
 
 I'd love to share some good news with the JSON Schema community.
 
-In short: I've joined [Postman's](https://www.postman.com/) Open Technology team to work on JSON Schema full-time. In doing so I'm joining a growing existing group of folks from the ecosystem, including amongst them [Ben Hutton](https://twitter.com/relequestual), JSON Schema's specification lead. This brings the number of people working on JSON Schema full-time up to 2 (and counting!).
+In short: I've joined [Postman's](https://www.postman.com/) Open Technology team to work on JSON Schema full-time. In doing so I'm joining a growing existing group of folks from the ecosystem, including amongst them [Ben Hutton](https://www.twitter.com/relequestual), JSON Schema's specification lead. This brings the number of people working on JSON Schema full-time up to 2 (and counting!).
 
 What does this mean? Primarily, on my part, more mindspace dedicated to JSON Schema, and hopefully thereby some long-needed improvements to the test suite, to my implementation, to new implementations, and beyond. We hope to grow the community even further, and to connect more strongly with it.
 
 
@@ -743,5 +743,5 @@ it's all JSON, and we know darn well how to munge that.
 [repo]: https://git.babyl.ca/yanick/hyperborea-character-sheet
 [jsonschema]: https://json-schema.org/
 [ASSH]: https://www.hyperborea.tv/
-[gizmo]: https://twitter.com/gizmomathboy
+[gizmo]: https://www.twitter.com/gizmomathboy
 [yaml]: https://yaml.org/
@@ -18,7 +18,7 @@ I've received a lot of questions (and purported bugs) and had quite a few discus
 
 Let's dig in.
 
-_The last time we [talked about output](./fixing-json-schema-output), it was to announce changes from the 2019-09/2020-12 version.  I'm going to use the new formats because it's easier to read and more compact._
+_The last time we [talked about output](fixing-json-schema-output), it was to announce changes from the 2019-09/2020-12 version.  I'm going to use the new formats because it's easier to read and more compact._
 
 ## No Problem
 
@@ -338,6 +338,6 @@ JSON Schema output gives you all of the information that you need in order to kn
 
 If you have any questions, feel free to ask on our Slack workspace (link in the footer) or [open a discussion](https://github.com/orgs/json-schema-org/discussions).
 
-_All output was generated using my online evaluator https://json-everything.net/json-schema._
+_All output was generated using my online evaluator <https://json-everything.net/json-schema>._
 
 _Cover image by [Tim Gouw](https://unsplash.com/@punttim) on [Unsplash](https://unsplash.com/photos/man-wearing-white-top-using-macbook-1K9T5YiZ2WU)_
Original file line number	Diff line number	Diff line change
`@@ -72,4 +72,4 @@ I'm really excited about the opportunity that Postman has given me to work full`
`72`	`72`
`73`	`73`	`Thank you to everyone I've met on this journey, used my libraries, asked questions, contributed code, or just offered opinions! I love being a part of this community!`
`74`	`74`
`75`		`-Cover photo by me 😁`
	`75`	`+Cover photo by me 😁`