I was wondering what we get out of the JSON-LD semantically if we use skos like this. I think currently we get a triple that says our isAbout blank object has a skos:mappingRelation to a string literal. What we want to express with that is rather that the value in the string should be treated as the actual predicate of that triple towards the isAbout term placed in "@id".
So semantically we should rather replace the isAbout property with the actual names of the skos properties:
So instead of :
{
"isAbout": [
{ "@id": "http://other.stuff", "label": "troll"},
{ "@id": "http://more.stuff"}
]
}
{
"exactMatch": [
{ "@id": "http://other.stuff", "label": "troll"}
],
"narrowMatch": [
{ "@id": "http://more.stuff"}
]
}
But that would probably affect everything that relies on isAbout. So I am not sure this is wise (though semantically correct).
Originally posted by @Cpprentice in #307 (comment)
I was wondering what we get out of the JSON-LD semantically if we use skos like this. I think currently we get a triple that says our isAbout blank object has a skos:mappingRelation to a string literal. What we want to express with that is rather that the value in the string should be treated as the actual predicate of that triple towards the isAbout term placed in "@id".
So semantically we should rather replace the isAbout property with the actual names of the skos properties:
So instead of :
But that would probably affect everything that relies on isAbout. So I am not sure this is wise (though semantically correct).
Originally posted by @Cpprentice in #307 (comment)