Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ontology Template #2

Open
mmaltsev opened this issue Apr 15, 2018 · 2 comments
Open

Ontology Template #2

mmaltsev opened this issue Apr 15, 2018 · 2 comments
Assignees

Comments

@mmaltsev
Copy link
Collaborator

One of the crucial topics as I see it - is to create a "Standard template" so that we could compare against it

  1. existing standards;
  2. enrichment results;
  3. new standards.

The idea is that it will help to fill all necessary fields and ensure that all objects following same predicates have the same datatype (URI / String / Date / ...).

I made an attempt to create such a template in JSON format and as an image:

On the image above, red area consists of predicates which are necessary for each standard. Yellow - useful predicates that can help to find out more about it and to enrich the ontology if needed. Green - predicates, providing additional information. Inside parenthesis you can see the datatypes of each predicate.

Comparison against the template was implemented here. While checking the structure, this piece of code saves its logs to the file. Here you can find automatically generated logs after applying the approach to the original ontology.

From my point of view, the hierarchy of predicates along with their datatypes should be carefully revised.

@igrangel
Copy link
Collaborator

igrangel commented May 8, 2018

This is definitely a great idea. First of all, the template SHOULD NOT be in a JSON file. This checking should be made based on the STO ontology. We should ask for all the properties in which the Standard class is the domain. Second, all the predicates should be carefully checked especially the mandatory predicates. Some properties are missing: sto:officialResource, sto:hasClassification.

@mmaltsev
Copy link
Collaborator Author

JSON is the simplest implementation of the "hierarchical" (necessary-useful-additional) structure of the Standards' predicates. In addition, it is easy to create a visualisation of the "hierarchy", based on JSON.

Unfortunately, at the current state, STO is not fully consistent. Here you can find some statistics regarding the usage of predicates. Only rdf:type and rdfs:label are used in 100 out of 100 standards. That's why it is hard to rely only on STO.

Regarding missing predicates - you can find sto:hasOfficialResource at the first row in the yellow layer and sto:hasClassification at the second row in the yellow layer on the image above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants