Merge pull request #628 from CommonCoreOntology/545-create-iri-reservation-process-and-registry

Adding IRI registry
This commit is contained in:
Mark Jensen
2025-03-28 14:44:04 -04:00
committed by GitHub
3 changed files with 2016 additions and 7 deletions

View File

@@ -23,17 +23,19 @@ CCO itself is not intended to grow indefinitely by including content that is pro
## Contributing
Users may find the current release files for [CCO here](https://github.com/CommonCoreOntology/CommonCoreOntologies/releases/latest)
Users may find the current release files for [CCO here](https://github.com/CommonCoreOntology/CommonCoreOntologies/releases/latest).
Developers may clone this repository and directly import AllCoreOntology.ttl in an ontology editor such as [Protégé](https://protege.stanford.edu/) to generate the merged version of the eleven CCO ontologies. Those who wish to forego managing imports may find a merged version of the files at src/cco-merged/
Developers may clone this repository and directly import AllCoreOntology.ttl in an ontology editor such as [Protégé](https://protege.stanford.edu/) to generate the merged version of the eleven CCO ontologies. Those who wish to forego managing imports may find a merged version of the files at `src/cco-merged/`
Users who wish to view the content of CCO in a web browser may view the current CCO release on the [Industrial Ontology Portal viewer](https://industryportal.enit.fr/ontologies/CCO)
Instructions and guidelines for contributors can be found [here](https://github.com/CommonCoreOntology/CommonCoreOntologies/tree/develop/documentation/contributing).
For information regarding the management of CCO, tutorials, lists of projects that extend CCO, associated research, standards activities in the IEEE, and more, please navigate to the [CCO home page](https://commoncoreontology.github.io/cco-webpage/)
Users who wish to view the content of CCO in a web browser may view the current CCO release on the [Industrial Ontology Portal viewer](https://industryportal.enit.fr/ontologies/CCO).
For bug fixes, developed suggestions for improvement, or minor updates, please open an issue using the template [here](https://github.com/CommonCoreOntology/CommonCoreOntologies/issues)
For information regarding the management of CCO, tutorials, lists of projects that extend CCO, associated research, standards activities in the IEEE, and more, please navigate to the [CCO home page](https://commoncoreontology.github.io/cco-webpage/).
For more open-ended discussion, general questions, or compliments, please navigate to the discussion board [here](https://github.com/CommonCoreOntology/CommonCoreOntologies/discussions)
For bug fixes, developed suggestions for improvement, or minor updates, please open an issue using the template [here](https://github.com/CommonCoreOntology/CommonCoreOntologies/issues).
For more open-ended discussion, general questions, or compliments, please navigate to the discussion board [here](https://github.com/CommonCoreOntology/CommonCoreOntologies/discussions).
## Who Oversees CCO Today?
@@ -83,4 +85,4 @@ For more information about the governance of CCO, please navigate to the [Common
**[Website]([https://commoncoreontology.github.io/cco-webpage/)** | **[Contact Us](mailto:jensen.mark@icloud.com)**
![Visitor Count](https://profile-counter.glitch.me/CommonCoreOntology/count.svg)
![Visitor Count](https://profile-counter.glitch.me/CommonCoreOntology/count.svg)

View File

@@ -0,0 +1,11 @@
## Instructions for contributors who are creating new terms as part of a pull request.
Before starting work, you'll need to record the IRIs that you need in a csv file that is hanging out on a separate branch.
To this end:
1. Navigate to the IRI Registry branch here: https://github.com/CommonCoreOntology/CommonCoreOntologies/tree/iri-registry-branch
2. Open the file `iri-registry.csv` located in the documentation/contributing/ directory and navigate to the bottom row of the file.
3. On the next empty bottom row, add the next IRI as an increment from the last one, your name, the date, and associated issue to the next available IRI(s).
4. Commit your changes to the IRI Registry Branch but do not open a PR.
5. Now you can open a new branch to execute your work using the IRIs that you have registered.

File diff suppressed because it is too large Load Diff