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

Improving enriching STO with dbpedia data #1

Open
igrangel opened this issue Nov 1, 2017 · 4 comments
Open

Improving enriching STO with dbpedia data #1

igrangel opened this issue Nov 1, 2017 · 4 comments
Assignees

Comments

@igrangel
Copy link
Collaborator

igrangel commented Nov 1, 2017

The improvement of rdfs:label and rdfs:comment is good for us
On top of that we should check what is convenient to map to the dbpedia ontology
Question, the abstract property

  1. Should we include it or should we map it with a better name?
@mmaltsev
Copy link
Collaborator

Unfortunately, I don't have any good suggestions about this issue. The property seem to carry a big ammount of information that can be useful. On the other hand, the difference between it and such properties as rdfs:comment and skos:definition is not always quite clear for me.

@igrangel
Copy link
Collaborator Author

igrangel commented Nov 13, 2017

rdfs:comment described here is used to provide a human-readable description of a resource.
skos:definition described here is used to provide a complete explanation of the intended meaning of a concept.
Basically, they are similar but I propose to keep it simple, i.e., use or improve the rdfs:comment.
The question here is if it would be better to improve the existing rdfs:comment with the abstract information or to create a version of the abstract property in the STO ontology to include the information that comes with the abstract.

@mmaltsev
Copy link
Collaborator

Since I can't think of any good arguments for or against the alternatives, I would rather prefer not to create an additional property in STO if there is no necessity.

@igrangel
Copy link
Collaborator Author

Then we just add the abstract to our Knowledge Base (KB) as a DBPedia property.
Which other property from DBPedia can be of importance for enriching our KB?

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