First, congratulations @ethanresnick and @dgeb for merging #1268! 🎉

I'm incredibly excited for v1.1 to be released and to (hopefully) be one of the first adopters :)

I see that the registration concept was removed from #1195. Are there plans to reincorporate that?

Should we proceed on the assumption that our profile URIs will typically have our own domain or the jsonapi.org domain?

Personally, I'd love to contribute the profiles we generate back the JSON API community. I think a profile registered with a jsonapi.org domain would make them more discoverable.

To give a few concrete examples of the profiles I'd like to register:

• a filtering syntax
• a pagination syntax
• handling CRUD on relationships that can target a resource object more than once
• handling access restrictions on individual resource objects in a collection
• a way to represent RFC8288 link objects (with rel and other link-params under the meta key)
• a home document format and standard API entry point
• a JSON API compliant implementation of resource versioning using RFC5829