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

How to deal with Hydra's draft status? #11

Open
letmaik opened this issue Jan 31, 2016 · 1 comment
Open

How to deal with Hydra's draft status? #11

letmaik opened this issue Jan 31, 2016 · 1 comment

Comments

@letmaik
Copy link
Contributor

letmaik commented Jan 31, 2016

Since the Hydra vocabulary will be a draft for the foreseeable future, it block our own spec from advancing beyond a draft if Hydra is suggested in various recommendations. Should we care? Alternatives?

@philarcher
Copy link

It depends what status you want for the spec. A formal spec? Then yes, the status of anything you link to matters, especially if you create an actual dependency. If you mean "a stable documentation of what we've done", i.e. not a formal spec, then it won't matter. Hydra has a w3.org namespace which means it's stable, but, no, it's not a formal spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants