-
Notifications
You must be signed in to change notification settings - Fork 13
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
Missing import - PEP ontology #38
Comments
Thanks for reporting. The server was down for an unknown reason. |
Thanks for fast response! :-) |
Hi ! |
Thanks for the notice. It's up and running again. This app is a bit unstable. I'll correct that when I find some time. |
Hi :-) I have another remark on PEP: Today, I am able to load https://w3id.org/pep/pep-1.1 with Protege, but not https://w3id.org/pep/pep-1.0, since there is no file available. The older version must still be in the import statements in https://w3id.org/seas/seas-1.1, so that I cannot load it completely. |
Since SEAS was suggested to us again, I had another look at it. I foud further missing imports from the seas namespace:
|
Trying to load the SEAS Ontology with Protege and https://w3id.org/seas/ results in some missing imports.
The ontology tries to load:
none of which are available. Is there a chance to fix this for SEAS?
If I see correctly, both versions are available on GitHub:
while the w3id points to https://ci.mines-stetienne.fr/pep/, cf. https://github.com/perma-id/w3id.org/blob/master/pep/.htaccess
Thanks for considering!
cf. also #27 import of both versions
http://www.w3id.org/pep
The text was updated successfully, but these errors were encountered: