Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The use of URNs instead of scheme structures #259

Open
gra-moore opened this issue Nov 3, 2021 · 3 comments
Open

The use of URNs instead of scheme structures #259

gra-moore opened this issue Nov 3, 2021 · 3 comments
Labels
next-major-release Confirms that an issue has been deferred until the next major version release.

Comments

@gra-moore
Copy link
Collaborator

The scheme structure that is used extensively feels a bit clunky but is there for good reason. To allow different kinds of identification scheme and to know which scheme is in play.

An alternative to the rich structure of scheme, would be to use URNs to capture the same data.

urn:scheme:scheme-bit1:scheme-bit2

The use of single string to capture identifiers creates and simple and more common way to identity and also makes it easier to align with the use of URIs, either for identity or for addressing.

I am not sure what impact this would have on the current model and how to have the two live in harmony.

The list of schemes would be registered from adewg, and each scheme owner should publish a web page describing their scheme.

@stale
Copy link

stale bot commented Feb 8, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Feb 8, 2022
@gra-moore gra-moore removed the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Feb 9, 2022
@gra-moore
Copy link
Collaborator Author

This is a 2.0 issue but should not be closed now.

@cookeac cookeac added the next-major-release Confirms that an issue has been deferred until the next major version release. label Feb 10, 2022
@cookeac
Copy link
Collaborator

cookeac commented Feb 10, 2022

Added next-major-release label which will keep this open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next-major-release Confirms that an issue has been deferred until the next major version release.
Projects
None yet
Development

No branches or pull requests

2 participants