TopBraid 7.8.1: skos:inScheme value no longer populated

[Yves Forkl]

Hi,

after upgrading to TopBraid 7.8.1 and migrating our collections, we observe the following situation.

1) In the concept editing form of any taxonomy, the property skos:inScheme (http://www.w3.org/2004/02/skos/core#inScheme) with label "is in scheme" is now shown under "Undeclared Properties".

2) In any existing taxonomy, while all existing (i.e. migrated) ordinary concepts have that property set to the Concept Scheme of the taxonomy, any newly created concept does neither allow to set this property nor does the value get set automatically to the Concept Scheme.

How can we remedy both issues so that when adding a new concept to the taxonomy, the concept's skos:inScheme property value is automatically set to the taxonomy's Concept Scheme just like it worked before in TopBraid 6?

Thank you,

Yves

[Holger Knublauch]

Hi Yves,

Apologies if I don’t remember how all this worked in TopBraid 6 which must have been years ago. It probably didn’t use SHACL for the form definitions but relied on a mix of various technologies including rdfs:domain statements. But in order to make properties properly show up on forms and edit their values, they need to be declared as (SHACL) property shapes. I don’t see a definition of a property shape for skos:inScheme in out default ontology skos.shapes.ttl so I guess you’d need to add this. You could create a new Ontology that extends skos.shapes.ttl and then adds this shape.

Maybe you could also just “infer” it using a sh:values rule based on a combination of skos:broader and skos:hasTopConcept, if you don’t want to maintain those triples explicitly.

So do you want to really assert these triples or can they just be derived automatically?

Holger