Resolving human readable APs in OMO

[matentzn]

As @balhoff mentions here:

#82 (comment)

I'm going to abstain because I came too late to say that I would have liked to first see a plan for how the non-opaque terms will be resolved by the PURL infrastructure, and what the recommended prefix would be. It would be inconsistent and confusing for OMO: to expand to anything but http://purl.obolibrary.org/obo/OMO_, since it's registered in OBO.

We plunged right into a vote on human readable IRIs without thinking about how to manage them within the confines of our PURL system. I will offer the following options for now, maybe there are more:

• obo:definedByPattern: <http://purl.obolibrary.org/obo/definedByPattern>
• omo:definedByPattern: <http://purl.obolibrary.org/obo/omo#defindedByPattern> (note lower case omo, also a widely used IRI pattern across our ontologies).
• OMO_PROP:definedByPattern: <http://purl.obolibrary.org/obo/omo/defindedByPattern>

Please let me hear your ideas!

[matentzn]

Some thoughts:

• we generally do not want to use hashes in OBO, we use / to avoid having to download the whole file during resolution
• @jamesaoverton suggests we could go here http://purl.obolibrary.org/obo/OMO_definedByPattern

[balhoff]

+1 to camelCase for this situation; I think it meshes better with our underscore separator than snake_case.

[matentzn]

Not anymore relevant, as the motion to use readable IRIs was dismissed! #82