Dependence on rdfs:label

[BenjaminHofstetter]

Blueprint depends on rdfs:label. It is used everywhere. New users hit this problem a lot.

They use for example:

• schema:name
• skos:prefLabel

workarounds:
add rdfs:label to your data with an insert SPARQL query.
e.g.

insert {
  ?s rdfs:label ?label 
} WHERE {
   ?s schema:name ?label .
}

This is the way to go right now.

Another approach is to add the schema.org or skos ontology to the triple store and enable inference.

skos:prefLabel is a subProperty of rdfs:label
schema:name is a subProperty of rdfs:label

But this can lead to have more labels than expected and the user may not enable inference.

We can still do that and do "manual" inference using sparql something like

CONSTRUCT {...} WHERE {
     ?labelPredicate rdfs:subPropertyOf* rdfs:label .
    ?s ?labelPredicate ?label . 
}

For this a code change is required and the triple store must contain the ontology definitions.

Another thing is the dependence on Full Text Search. If we support other labels we must ensure that Full Text Search is indexing all the required labels (rdfs:label, skos:prefLabel, or schema:name).

Another approach is to make the label predicate configurable. This may lead to a lot of code change in I am not sure if it is possible. Probably yes but we still need to ensure that Full Text Search is indexing the required labels.