A lot of development has happened, since I am using GitHub to document ideas and implementations this TODO is going slowly obsolete. The idea is to replace it with a CHANGELOG during the initial release.
- Important question: is every transportation facility part of some transportation infrastructure?
- Import from RO: has role, has quality etc...
- Reworked pipeline
- Follow this to avoid botching parking ontology: ontodev/robot#1150
Produced first version of paper diagrams. These show the commitments of existing ontologies.
- Produce diagrams of implementations from this ontology.
- Considering importing parking related competency questions from the iCity project report
Implemented a strong basis for imports coming from the CCO and the OEO. There are still some classes that have to be redefined and added to the ontology as possible equivalents via annotation properties.
- Implement key classes from scenario 1
- Add potential associations using "may be identical to"
Implemented the imports from CCO and the IAO (used the imports from OEO), I had to manually add the sub-class relation between the information entities and BFO. Realized that there are numerous classes from CCO that can be valuable for this ontology.
- I should implement a script that automatically extracts and collects
subclasses of
change,GeographicalLocationsand others. - I should add correct attribution to the imported modules.
Imported some concepts from the Common Core Ontologies. This might need an extra step of replacing the iris when releasing. Also assigned them with identifiers specific to the current ontology, so they are easily recognizable.
- Currently the CCO imports cause a duplication of some BFO classes axioms. I have to figure out how to make this leaner.
Added documentation online in gitlab pages.
- I Figured out I need to rethink the approach for competency questions, this paper has good examples of competency questions and their SPARQL implementation. Maybe I can use it to inspire the ones in this ontology.
I set everything up to have a working developer documentation, this has still to be filled with more content.
- Setup CI to render docs.
- Consider adding documentation versioning.
This ontology project is a small practical application intended for demonstration of the concepts explored in one of my publications. This should serve as practice for ontology development. Initial setup requirements:
- Set documentation environment up using mkdocs
, and probably the gitbook theme. - Setup of the testing framework using competency questions.
- Write down the use case scenarios (these are also going in the paper).
- Decide in a proper name (CHIO?)
- Decide on the ontology term conventions, maybe use identifiers with the following form "CHIO_XXXXXXXX"
- Import the necessary OEO Terms.