Should we create a top level /merged/ as this is claimed by ontobee

[cmungall]

OntoBee places merged ontologies into $OBO/merged/uc($ONTID).

E.g.

http://sparql.hegroup.org/sparql?default-graph-uri=&query=SELECT+distinct+%3Fgraph_uri+WHERE+%7B+GRAPH+%3Fgraph_uri+%7B+%3Fs+rdf%3Atype+owl%3AOntology+%7D+%7D&format=text%2Fhtml&timeout=0&debug=on

We should register merged by making a file merged.yml

• We would have a way to resolve PURLs like: http://purl.obolibrary.org/obo/merged/GO -- presumably to ontobee?
• We would prevent anyone accidentally registering an ontology called "merged" (OK, unlikely)
• It's just generally good for us to have a handle on what PURLs in the OBO space are being used and how.

Of course, we would not make a md file in the other repo, as this is not an ontology, it's a prefix.

In future, we must discourage unregistered injections into the OBO purl space, but I suggest we treat this one as grandfathered in.

We as OBO should also try and encourage standards for naming of named graphs, especially for triplestores that bring in OBOs. Some suggestions here: https://docs.google.com/document/d/1sQnNoCmneLjZPsUc6iBgbEkuqhxihFn09u9RrpHcUc8/edit