-
Notifications
You must be signed in to change notification settings - Fork 128
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
Add PURLs for Apollo-SV modules #502
Comments
Hi James, That's acceptable. Thank you. Apologies for the error. |
Ok. I'll make a Pull Request. Is there a reason why only one of these PURLs uses undescores, while the others use hyphens? It doesn't matter to me, but users appreciate consistency. |
Sorry, I'm not thinking straight. Where are the OWL files that these PURLs should point to? I need the kind of information that's in this file: https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/apollo_sv.yml. The PURL entries should end up looking like this:
The |
Fair point. We originally had these in an internal application ontology in a different repo. I'm coordinating with our team to now to ensure that moving them to the Apollo-SV doesn't break anything. Apologies of the inconvenience. |
Thanks, James. I have updated the .yml file to include the desired redirects |
Sorry for the delay. Can you please email me a copy of the updated file? (Or make a Pull Request here on GitHub, if you're familiar with that process.) |
Apollo-SV would like PURLs for several modules. @aellenhicks included the following list in an email to OBO Discuss today:
Apollo-SV has a PURL configuration file here: https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/apollo_sv.yml
The requested PURLs don't conform to our OBO ID policy http://obofoundry.org/id-policy.html, which requires a slash after the ontology ID, e.g. http://purl.obolibrary.org/obo/apollo_sv/region_neutral_instances_and_classes.owl. @aellenhicks Is this change acceptable?
The text was updated successfully, but these errors were encountered: