On Jun 13, 2019, at 4:39 AM, Eva Ibarra Sicilia <eva.ibarr...@gmail.com> wrote:
Since update to 6.2.2 rdfs:labels are ignored and do not appear for entities in Reference Datasets, even if they are directly indicated by SHACL.Is this correct?
--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/e240c654-ad01-4510-8d51-6f3a45c5ea5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Yes sorry for the inconvenience. Just as a bit of background, the default forms in 6.2 are entirely based on GraphQL, and each object returned by our GraphQL service has a built-in field called "label" which maps to rdfs:label or skos:prefLabel in the user's preferred language. The fields on the forms however rely on those properties declared as SHACL property shapes. Those get mapped to other graphQL fields, based on their local name. rdfs:label does clash with "label" so it was suppressed. the graphql:name property declares the GraphQL field name that it shall use instead of "label" to avoid the clash.
We have since improved this for the next release, so that the graphql:name property no longer is needed for rdfs:label (and rdf:type which has the same problem clashing with "type").
Holger
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/C72A951B-2075-426B-88A0-D803878073FF%40topquadrant.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/66596692-97d2-4b9c-6213-c08fa86788a5%40topquadrant.com.