tokenUrl in 3.1 schema does not support relative urls as specified

[markrzen]

I am not super familiar with the OpenAPI 3.1 specification, so please excuse me if I misunderstood anything.

It appears that tokenUrl, a fixed field, should have been modeled in the 3.1 JSONSchema as a uri-reference to support relative urls.

REF: https://github.com/OAI/OpenAPI-Specification/blob/main/schemas/v3.1/schema.yaml#L899-L901

Note that the 3.0 schema has the format as uri-reference, as I would expect.

Happy to put in a pull request if this makes sense to someone with more experience in the repository.

REL: seriousme/openapi-schema-validator#178

[handrews]

Yeah AFAICT that falls under the rule that "URI" and "URL" really mean URI-reference and URL-reference (which is still format: uri-reference) in the spec (a rule I find confusing, personally).

@karenetheridge any thoughts here on this schema issue?

[karenetheridge]

I agree -- given https://spec.openapis.org/oas/v3.1.1#relative-references-in-api-urls, most things in the schema that are "format": "uri" should be uri-reference instead. We should probably revise the text in the spec as well to be more clear about that (or at least point back to section 4.7).

[markrzen]

In what is likely optimism, I filed a PR attempting to fix the issue I filed here. Hopefully I read between the lines well enough on both your conversation and the repo instructions.

[markrzen]

@handrews @karenetheridge Is there anything else I can do to help resolve this?

[handrews]

@markrzen probably not, we'll look at it in tomorrow's weekly call if no one gets to it before that.

[baywet]

from the meeting:

• let's start by documenting the process to release independent schema changes (no new spec version) Document & automate release process #4278 (in contributing)
• then we'll be in a position to release the updated schema
• and update the automation

Some context that might help with the documentation step:

• ralf already did some automation work https://github.com/OAI/OpenAPI-Specification/actions/workflows/schema-publish.yaml
• Publish OpenAPI Schema Iterations #4355
• this automation is taking its source from main:/schemas, which seems wrong?
• @ralfhandl to double check branches/content location https://github.com/OAI/OpenAPI-Specification/tree/main/schemas, and example
• @duncanbeevers suggests using the main branch as the source of truth for simplicity.
• @handrews the context is we don't want people to look at the repo as they are only placeholders and will confuse people.