-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ontological data annotation to utilise data sets with OEKG in the future #6
Comments
The only requirement is that all fields in the meta information (under the tables) and that all column names should be associated with some OEO concepts or some concepts from other ontologies (in case OEO does not cover the concept yet). Also this might help. As the OEKG can be populated repeatedly, we can read the values (via Python) from different formats (i.e., JSON) and update the knowledge graph accordingly. The main point here is that the development of the OEKG is not a static and one-shot operation. It is a recurring and evolving process. In this process, data formats seem not to be very critical, however, conceptualization (matching meta-data to ontological concepts) is important. |
That is an important information and should be documented properly. |
From this, I understand that connecting a concept and the data is paramount and how it is done secondary. For documentation here is how we go about it in the SEDOS project. We'll use the oemetadata v1.5.1 ----- Case1 ----- ----- Case2 ----- (UPDATED) For example: thermal efficiency of a heat power plant (as column in a tabular data set) The concept thermal efficiency is not (yet, as of 23.09.22) available in the OEO, but the concepts:
(UPDATED example)
We're aware that this violates the use of ----- Case3 ----- For example: fantasy power plant paramter
|
In the second case, thermal efficiency can fully expressed with the OEO: |
Thanks for the hint! However, the metadata should only annotate concepts and do not have the role of mapping relations. The mapping of relations, in the context of a subset of the OEO, is after all achieved by the OEKG. |
I don't think that simply listing classes that are somehow involved is a good solution. We once talked about about an oeo-module for composed classes. So there could then be a composed class @stap-m : Do you remember if we documented the idea of this oeo-module for composed classes for data annotation and the knowledge graph somewhere? |
We documented the idea in the etherpad of the 6th project meeting. However, the notes that were taken are not elaborate in any way... That's it:
|
The partners in the SEDOS project will use the oemetadata and OEO in the user role rather than the developer role. Thus, it should be as user-friendly and easy as possible to work with both. |
Are there requirements to be met when annotating data sets today so that these data sets can be used with OEKG applications in the future?
I understand that the OEKG build upon metadata in RDF format. However, at the moment, no OEmetadata standard has been developed in RDF format. Therefore, currently, OEMetadata v151 in JSON format must be used to annotate tabular data ontologically.
I ask to prevent us from having to put a lot of work into annotating data sets ontologically, which might then not be usable in the future.
The text was updated successfully, but these errors were encountered: