-
Notifications
You must be signed in to change notification settings - Fork 45
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
Map the yaml config to the W3C meta-data ontologies #180
Comments
Below is a snippet from the JSON-LD output for the
|
I started the map in my fork. Still has some ways to go, but could already be usable. When the DataProperty column has content a literal is sufficient. Otherwise, if the content is in the ObjectProperty column then a new instance is necessary, of the type in the Range column |
Update: this issue is considerably broader than initially assessed, the output RDF has semantic flaws at various levels that aren't solvable with the current parser. I will start by creating a thorough map between each keyword in the yaml configuration file to classes and predicates in the W3C ontologies (DCat, VCard, Prov, etc). From that map a new parser can be developed with a more direct RDF generation.
I transformed the JSON-LD output to Turtle for legibility (see below). The organisation instance is using the vcard:fn predicate, which is a data property of the Individual class. Basically it says that the full name of EC is "Tom Kralidis". The semantics of VCard must be revised.
The text was updated successfully, but these errors were encountered: