Create IRI reservation process and registry
Opened this issue · 1 comments
mark-jensen commented
Maintain a csv of taken IRIs in a directory with instructions on process.
Have a persistent branch for editing it.
When a developer needs an IRI, they edit the file and then make a PR on develop.
Add QC check to confirm no duplicates across the ontologies AND that all IRIs in the ontologies are in registry
neilotte commented
@mark-jensen -- just to capture this while I'm thinking about it: We should probably start a deprecation.ttl file that houses deprecated IRIs. This came to mind in reading the QC query you recommend above, which would then need to know about this file in order to ensure a deprecated IRI didn't sneak back in to circulation in CCO.