Henry Andrews

> However, I can add a reference to the relatively new HTTPAPI working group that is far more likely to be receptive to our project than the WG that we...

> There was discussion about "tracks" at one point and it was decided that the group would default to standards track unless there was reason not to. Ah, this is...

@admin-cimug thank you so much for this information! It is very helpful, especially since you were able to confer with a wider audience. While none of this should be taken...

Also pinging @davidgtonge who commented on #526 a while back with a perspective from the ISO. If you don't have time to go through everything here, [this comment](https://github.com/json-schema-org/json-schema-spec/pull/1277#issuecomment-1229528807) summarizes the...

@jdesrosiers this is looking great now! I left one or two threads "unresolved" but only because they have useful info from which I think any new visitors would benefit. specifically...

@admin-cimug are the "optics" concerns not addressed by what we previously discussed regarding an IETF media type registration plus our own publication in the context of being an OpenJS Foundation...

@gregsdennis good point. Should be obvious, but I am well aware that hardly anyone actually reads RFC 3986 no matter how much I xref it 😛

_[EDIT: The requirements I wrote here were wrong, better ones forthcoming in a new comment.]_

OK, thinking this through _again_ and hopefully correctly this time, I think the requirements are: * SHOULD support accepting a retrieval/initial base IRI (RIB IRI) for a schema resource *...

> If you have a default base URI that you treat as a retrieval URI, it's like treating all of your schemas as if they were accessed from the location...