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
DOSDP json schema docs need a simple, persistent URL that implementers can use for validation and that can be used in JSON-schema import statements once core and OBO are split.
@cmungall Any suggestions on a purl pattern? Would it be an abuse of the obo-library domain do re-use that?
The text was updated successfully, but these errors were encountered:
@jamesaoverton and I have discussed this for other things (e.g. shared sparql) but I can't find the ticket. I think the idea was an obolibrary purl, but instead of /obo/ sometimes link like /tools/, but would require a fair bit of plumbing I believe
From a technical perspective, I think the minimal change would be a hand-written www/tools/.htaccess file, which is easy enough (https://github.com/OBOFoundry/purl.obolibrary.org/tree/master/www). The next step would be YAML config files for each tool project, which would require updating the Python scripts.
DOSDP json schema docs need a simple, persistent URL that implementers can use for validation and that can be used in JSON-schema import statements once core and OBO are split.
@cmungall Any suggestions on a purl pattern? Would it be an abuse of the obo-library domain do re-use that?
The text was updated successfully, but these errors were encountered: