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

Replace broken www.co-ode.org namespace #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

stain
Copy link

@stain stain commented May 4, 2017

http://www.co-ode.org/ontologies/pizza stopped working - presumably the domain name registration lapsed.

not sure what would be an appropriate domain name.. I suggest using https://rawgit.com/ - but then versionIRI has to be updated per release tag (which is probably good).
(e.g. previous version is https://cdn.rawgit.com/owlcs/pizza-ontology/v1.5.0/pizza.owl )

http://www.co-ode.org/ontologies/pizza stopped working - not sure what would be an appropriate domain name.. I suggest using https://rawgit.com/ - but then versionIRI has to be updated per release tag (which is probably good).
(e.g. previous version is https://github.com/owlcs/pizza-ontology/blob/v1.5.0/pizza.owl )
Copy link

@ignazio1977 ignazio1977 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not necessary for an ontology IRI to be resolvable (although it's convenient and a good practice).

I'm not against this change (as it is an example ontology, an ontology IRI change has no impact on live systems), just wondering what should be the general policy.

@matthewhorridge
Copy link
Contributor

I would prefer something nicer like:

http://owl.cs.manchester.ac.uk/ontologies/pizza

I'm not sure how to put things on the owl.cs site though!

@matthewhorridge
Copy link
Contributor

.... this also attributes the ontology to Manchester, which is appropriate. At a push a gh-pages site would perhaps do e.g.

http://owlcs.github.io/ontologies/pizza

@matentzn
Copy link

matentzn commented May 8, 2017

I can put things there, but again, as @ignazio1977 points out, the resolvable IRIs are merely good practice, and I am not sure whether it is worth changing the old IRIs. (In particular, as I might add here because some of our unit testings for OWL Pizza ontology related coursework requires Unit tests that reference some of these classes directly, as do other teaching materials. :P )

However, I am down with anything. If you vote to move it to owl.cs, no problem. I can add stuff there. If you want to go with @stain idea or @matthewhorridge owlcs.github.io idea, I think its fine as well.

@matthewhorridge
Copy link
Contributor

@matentzn thanks for the clarification.

Changing the ontology IRI doesn't mean we have to change IRIs of entities in the signature of the ontology. Those would remain the same.

@matentzn
Copy link

matentzn commented May 8, 2017

Ah okay, then all is fine. Let me know if you need anything from me. :)

@stain
Copy link
Author

stain commented May 18, 2017

As an example ontology, it would be nice if the URIs were clickable, as users new to ontologies will recognize it as an URL and try to click it :)

I think owlcs.github.io is also OK -- but then we have to manually publish it to the equivalent gh-pages branch.

@stain
Copy link
Author

stain commented May 18, 2017

In fact I wish teaching would mention something about long-term URIs when deciding on a namespace.. e.g. https://w3id.org/ or ye old http://purl.org/ (which has now been woken from the dead).

Yet that is typically something to be finalized when publishing (aka releasing) an ontology, which then should cover roughly the same procedures as when releasing software, e.g. versioning, tags, release notes, unit tests, incompatibility checks...

I can't tell you how many times I've reviewed papers where the namespace of the ontology has died just in the short period between writing the ontology and writing up the paper...

@matthewhorridge
Copy link
Contributor

I think owlcs.github.io is also OK -- but then we have to manually publish it to the equivalent gh-pages branch.

Which isn't a bad idea. I don't think pushing commits to the repo should update the release/published version of the ontology.

@carsonlloyd
Copy link

RawGIT is gone now too :)

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

Successfully merging this pull request may close these issues.

5 participants