Skip to content

Conversation

handrews
Copy link
Member

@handrews handrews commented Sep 1, 2025

Please review carefully, as there's more going on here than in the other reorg PRs.

These sections had gotten rather bloated, plus moving them under the OpenAPI Object changes how it all reads. These two commits first move things (with as few changes as possible) and then make significant edits to the results for conciseness and readability. None of the changes are intended to change any actual requirements.

While there are a lot of changes, there are also a lot of unchanged blocks, including the former Appendixes F and G which are now in reversed order and (in one case) a subsection of the new appendix. Here are git diff --color-moved=dimmed-zebra diffs which make that a lot more clear (but are not good for detailed reviewing).


1st commit message:

  • Remove "OpenAPI Description" and "OpenAPI Document" section
    headings and reorder those paragraphs and the intro
    "OpenAPI Description Structure" paragraph to define the terms inline
  • Switch Appendixes F and G
    • F->G stays as-is, with base URI examples
    • G->F is expanded to a more general "Parsing and Resolution Guidance" section
  • Move several pieces of "Parsing Documents" to Appendix G
    • How to parse complete documents as the intro section
    • A "Warnings Regarding Fragmentary Parsing" section
  • Move "Structural Interoperability" under Appendix G and rename it to "Conflicts Between Field Types and Reference Contexts"
  • Move most of "Resolving Implicit Connections to Appendix G and rename it "Guidance Regarding Implicit Connections"
    • Put the original Section F implicit connection examples as a "Implicit Connection Resolution Examples" subsection
  • Minimal adjustments were made to links to keep the build functional.

2nd commit message:

A lot of what was here is no longer needed, and other things can
be said better either because of the new arrangement or because
I thought of better wording since I first wrote things.


  • schema changes are included in this pull request
  • schema changes are needed for this pull request but not done yet
  • no schema changes are needed for this pull request

* Remove "OpenAPI Description" and "OpenAPI Document" section
  headings and reorder those paragraphs and the intro
  "OpenAPI Description Structure" paragraph to define the terms inline
* Switch Appendixes F and G
    * F->G stays as-is, with base URI examples
    * G->F is expanded to a more general
      "Parsing and Resolution Guidance" section
* Move several pieces of "Parsing Documents" to Appendix G
    * How to parse complete documents as the intro section
    * A "Warnings Regarding Fragmentary Parsing" section
* Move "Structural Interoperability" under Appendix G and rename
  it to "Conflicts Between Field Types and Reference Contexts"
* Move most of "Resolving Implicit Connections to Appendix G and
  rename it "Guidance Regarding Implicit Connections"
    * Put the original Section F implicit connection examples as
      a "Implicit Connection Resolution Examples" subsection

Minimal adjustments were made to links to keep the build functional.
A lot of what was here is no longer needed, and other things can
be said better either because of the new arrangement or because
I thought of better wording since I first wrote things.
@handrews handrews added this to the v3.2.0 milestone Sep 1, 2025
@handrews handrews requested review from a team as code owners September 1, 2025 00:01
@handrews handrews added the editorial Wording and stylistic issues label Sep 1, 2025
@handrews
Copy link
Member Author

handrews commented Sep 1, 2025

Note that despite my care to not overlap any changes, git can't understand changes to adjacent lines and wants this to conflict with PR #4915. Please approve and merge that first, and let me fix the conflict because there will not be any changes to these commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial Wording and stylistic issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant