-
Notifications
You must be signed in to change notification settings - Fork 15
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
BOT Version IRIs do not resolve #80
Comments
Accepted as of CG Call 02 June 2020 Pending check if it causes problems |
Changed version IRIs according to #80
tested vom protege and issue remains -> revision of htaccess needed |
Potentially this can be revised by @AnnaWagner |
Tested https://w3id.org/bot-0.2.0 with Protégé v5.5.0 (most recent) and still does not load the versioned ontology. Also did some quick tests with Postman for RDF/XML and Turtle which do not return RDF (404). @GeorgFerdinandSchneider : can you give a quick update? I see the pull request is merged in w3id, but there's still an open issue there. |
The following was decided in the LBD call of 29th of June:
Can someone who's listed on the w3id folder of BOT update this or appoint the current chairs to w3id? @MadsHolten , @GeorgFerdinandSchneider , @pipauwel , @maximelefrancois86 ? The w3id only accepts pull requests from listed editors |
see the following pull request: perma-id/w3id.org#2292 |
The redirect to a dedicated version of BOT from Protege, e.g. 0.2.0 yields an error:
! Originally the version has been added using a slash; however, it has been changed to a dash:
This should be caused by the convention of defining the version IRIs.
Changing the version IRIs of BOT version to, e.g.
Should resolve this issue as the file(s)
https://w3c-lbd-cg.github.io/bot/bot-0.2.0.ttl
exist and is returned by the server.A similar approach has been followed by the seas ontologies, e.g.:
The text was updated successfully, but these errors were encountered: