You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Going forward we need a plan for creating new IRIs. We currently have few hosts and namespaces in the vivo-isf-ontology that we can continue to use and that are to some degree under our control. purl.obolibrary.org/obo/ARG_* is an example.
Things to discuss:
Should we continue to use the purl.obolibrary.org domain?
Should we register and use the vivo-isf.org domain?
The VIVO community will likely contribute content with the vivoweb.org domain.
How do we coordinate the creation of new identifiers to avoid name clashes? This is especially a problem for numerical IRIs when working in Protege.
Will we consider moving any of the existing IRIs to a different namespace?
Please feel free to comment, and raise any other issues related to the creation, resolution, etc. of IRIs, especially the ones for OWL classes and properties.
The text was updated successfully, but these errors were encountered:
Going forward we need a plan for creating new IRIs. We currently have few hosts and namespaces in the vivo-isf-ontology that we can continue to use and that are to some degree under our control. purl.obolibrary.org/obo/ARG_* is an example.
Things to discuss:
Please feel free to comment, and raise any other issues related to the creation, resolution, etc. of IRIs, especially the ones for OWL classes and properties.
The text was updated successfully, but these errors were encountered: