Skip to content

v3.2: sync fixes from 3.3#5299

Open
karenetheridge wants to merge 16 commits intoOAI:v3.2-devfrom
karenetheridge:ether/v3.2-sync-with-3.3
Open

v3.2: sync fixes from 3.3#5299
karenetheridge wants to merge 16 commits intoOAI:v3.2-devfrom
karenetheridge:ether/v3.2-sync-with-3.3

Conversation

@karenetheridge
Copy link
Copy Markdown
Member

@karenetheridge karenetheridge commented Apr 22, 2026

Backport of remaining fixes from 3.3 into 3.2: mostly from @valerii15298, and a few from @handrews and @notEthan.

  • no schema changes are needed for this pull request

@karenetheridge karenetheridge requested review from a team as code owners April 22, 2026 23:29
Comment thread src/oas.md
@miqui
Copy link
Copy Markdown
Contributor

miqui commented Apr 23, 2026

@karenetheridge q: Indeed we can reach URL: https://www.w3.org/TR/xml-names11/

however the url checker is not passing. Not sure if this has always been the case and we should merge ? @ralfhandl - thoughts?

@miqui
Copy link
Copy Markdown
Contributor

miqui commented Apr 23, 2026

@ralfhandl , @karenetheridge

links to the W3C TR page for XML Namespaces 1.1 (https://www.w3.org/TR/xml-names11/) check tooling sometimes gets a 403 Forbidden from W3C even though the page is reachable in a normal browser, which trips CI. (is this problem new?)

There’s also a conversion script (scripts/md2html/md2html.js) that rewrites XML namespaces into a bibliographic-style reference ([[xml-names11|XML namespaces]]) for rendered output—so the W3C URL is a known/intentional citation in the project history.

initial thoughts:
Add an allowlist/ignore rule for that URL in the link checker config (best if you want to keep the canonical W3C reference).

@miqui miqui self-requested a review April 23, 2026 13:56
Comment thread src/oas.md
@notEthan
Copy link
Copy Markdown
Contributor

The ones from me are still open (#5290, #5291, #5292). Just noting, I'm not bothered about whether those are merged via those PRs or this one.

@karenetheridge
Copy link
Copy Markdown
Member Author

Let's merge those instead; I was only intending on catching up with syncing that hadn't been done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants