Many thanks for the hint! I am learning all of this right now. Perhaps the terminology really is not 100% correct. I need to look at the link you gave me. Do you have time to read the article? I am very much interested in your expert opinion on whether the concepts hold up. Thank you very much for your support!
I read the entire article. The implementation is a basic SKOS RDF vocabulary, not an ontology. And ontologies do encode decisions and constraints:exactly what ontologies do do. But it seems that the vocabulary is conflated in your piece as the ontology. You are correct that a vocabulary and SKOS cannot encode decisions and constraints. That’s because it’s not an ontology—it’s a vocabulary. A vocabulary is the hierarchy of terms with parent child relations, definitions and alt labels. An ontology encodes rules and constraints—relationships beyond the hierarchy. We have two basic elements in ontology construction: the ABox (assertions and data) and Tbox (terminology or the classes)
Ontologies also vary unique identifiers for each class, property relation.
Not sure if you’ve had time to read my explainers and tutorials on ontologies that perhaps that may help to demystify
1-6 is a controlled vocabulary in SKOS RDF but not an ontology. You have expressed a controlled vocabulary. We call this the CBOx or controlled vocabulary box or category box. By definition you have built a vocabulary. An ontology has relationships outside of the broad-narrow hierarchy. An ontology has rules and constraints—direct and indirect relations.
I would say the title can be “What the Heck is a SKOS vocabulary” not ontology
Seems you’ve confused vocabulary with ontology? An ontology is logical reasoning model with constraints, ranges and value.
I currently work in big finance and indeed, actual ontology is one able to describe and enforce decisions, constraints and encode judgement.
This is not something that can be done with the SKOS vocabulary model.
This is the industry standard ontology for banking and finance:
https://spec.edmcouncil.org/fibo/
This is ontology. SKOS is an RDF data model.
Many thanks for the hint! I am learning all of this right now. Perhaps the terminology really is not 100% correct. I need to look at the link you gave me. Do you have time to read the article? I am very much interested in your expert opinion on whether the concepts hold up. Thank you very much for your support!
I read the entire article. The implementation is a basic SKOS RDF vocabulary, not an ontology. And ontologies do encode decisions and constraints:exactly what ontologies do do. But it seems that the vocabulary is conflated in your piece as the ontology. You are correct that a vocabulary and SKOS cannot encode decisions and constraints. That’s because it’s not an ontology—it’s a vocabulary. A vocabulary is the hierarchy of terms with parent child relations, definitions and alt labels. An ontology encodes rules and constraints—relationships beyond the hierarchy. We have two basic elements in ontology construction: the ABox (assertions and data) and Tbox (terminology or the classes)
Ontologies also vary unique identifiers for each class, property relation.
Not sure if you’ve had time to read my explainers and tutorials on ontologies that perhaps that may help to demystify
Thank you so much for your help!
Would it be correct to say, that the building blocks 1-6 are partially elements of ontology?
Or what would be the correct term?
Than I will make the corrections in the article.
1-6 is a controlled vocabulary in SKOS RDF but not an ontology. You have expressed a controlled vocabulary. We call this the CBOx or controlled vocabulary box or category box. By definition you have built a vocabulary. An ontology has relationships outside of the broad-narrow hierarchy. An ontology has rules and constraints—direct and indirect relations.
I would say the title can be “What the Heck is a SKOS vocabulary” not ontology
I have included a clarifying paragraph and changed the title.
Ontologies are logical descriptive models and this includes supporting judgements and constraints: