-
Notifications
You must be signed in to change notification settings - Fork 11
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
Permanent Identifiers #47
Comments
Agree, w3id.org is definitely the best choice now. At least, it is not read-only since last year... |
I'm not confident about it, once it is not a pattern and only 34 people are inscribed in W3C (https://www.w3.org/community/perma-id/ ) in contrast of the author said in previous link something around 10k people. However, I liked it as an option for unavailability of Purl.org |
Done. |
Beware that forwarding https://w3id.org/mex/ to http://aksw.github.io/mexproject/ means that you cannot use the w3id identifier for the MEX vocabulary (http://mex.aksw.org/), which is actually the intended use. I'd suggest the following:
|
That's true 👍 @cirola2000 could you please update the rules? |
folks, 1 - https://w3id.org/mex/$1 redirects to http://mex.aksw.org/$1 (AKSW proxy) GitHub: last version/update of the vocabulary stays without versioning in the name, e.g.: We keep each version by adding the version number, e.g.: https://raw.githubusercontent.com/AKSW/mexproject/master/vocabulary/mexcore1.0.1.ttl (it does not exist, just an example). HTML documentation stays at dne5.com, once GitHub is not able to render HTML content. |
Also, @DiegoMoussallem has created the SPARQL link here |
update the uris in order to support content negotiation
https://w3id.org/
The text was updated successfully, but these errors were encountered: