Document the ory.sh/kratos object (schema extensions) with a schema

[space88man]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Network project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe your problem

The ory.sh/kratos object used in Identity Schema Extension is not clearly defined but instead is presented by example and in several locations. See the discussion here: ory/kratos#3389

It would be useful for a single JSON schema to be used to describe the properties and types allowed in this object.

Describe your ideal solution

A JSON schema for the object used as a ory.sh/kratos property

Workarounds or alternatives

See by example what properties this object contains as listed in the discussion ory/kratos#3389

Version

v1.0.0

Additional Context

In the examples, the ory.sh/kratos property suddenly pops up as it is needed for Identity Schema Extensions. There isn't a section in the documentation that clearly defines the purpose and schema of this object.

[vinckr]

Thanks for the issue!
I transferred it to /docs as it just documenting something that is implemented.
I am not sure where to look but if anyone reading this wants to work on this and needs help with our docs, let me know!

[github-actions]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️