Re: [topbraid-users] small shacl example question

2021-07-28 Thread Holger Knublauch
Oops, yes. I need to record this for the errata. This is a W3C doc that I cannot simply change. Thankfully it is just an informal example. Holger On 28/07/2021 5:46 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote: Wrt to following fragment in https://www.w3.org/TR/shacl/

Re: [topbraid-users] shacl for range only (in case of implicit targets)

2021-07-28 Thread Holger Knublauch
No. Holger On 28/07/2021 5:24 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote: Thx Holger So there is no implicit variant here without  a target? Like: ex:*hasUnit*     a sh:NodeShape ;     sh:class qudt:Unit . (where ex:hasUnit is also an rdfs:Property somewhere

[topbraid-users] small shacl example question

2021-07-28 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Wrt to following fragment in https://www.w3.org/TR/shacl/ (or later: https://w3c.github.io/data-shapes/shacl/) * At most 5 values of ex:property? * Shouldn't that be ex:digit? The following example illustrates the use of sh:qualifiedValueShapesDisjoint to express that a hand must have

RE: [topbraid-users] shacl for range only (in case of implicit targets)

2021-07-28 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Thx Holger So there is no implicit variant here without a target? Like: ex:hasUnit a sh:NodeShape ; sh:class qudt:Unit . (where ex:hasUnit is also an rdfs:Property somewhere else/imported). To establish a global range-like property constraint, you could do ex:hasUnitShape a