Re: [topbraid-users] oneOf in shacl

2018-10-31 Thread Irene Polikoff
Holger is correct. But additionally, this example calls for some reflection on the goal of this modeling pattern - having owl:oneOf in the first place. OWL is open world. This means that if you say the following: ex2:Category rdf:type owl:Class ; rdf:type sh:NodeShape ; rdfs:subClassOf

Re: [topbraid-users] sh:nodeKind questions

2018-10-31 Thread Irene Polikoff
Correct > On Oct 31, 2018, at 2:24 PM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > wrote: > > Ok thx > So if my owl properties always have range...my shacl always has a datatype or > class...so then no need to use nodeshape at all..right? > The simpler the better > > Verzonden van

Re: [topbraid-users] Issue when using parameters on SWP service

2018-10-31 Thread William Ramos
Sorry for the confusion, this time it is outside of the SERVICE block, but now the service gives me an error: > An internal error has been reported by SWP engine of TopBraid Live > > Could not find registered ui:Element for > http://example.org/getTaxonomies#taxonomies >

Re: [topbraid-users] Issue when using parameters on SWP service

2018-10-31 Thread William Ramos
Hi, Holger; I tried that resulting in the following code: http://company.com:80/edg/tbl/sparql ; { rdf:nil teamwork:graphsUnderTeamControl (

Re: [topbraid-users] sh:nodeKind questions

2018-10-31 Thread Holger Knublauch
The default value of sh:nodeKind (and any other constraint such as sh:maxCount) is that no constraint exists. So, values could have any node kind by default. If sh:datatype exists then sh:nodeKind sh:Literal is implicit and would be redundant. If sh:class exists then sh:nodeKind

Re: [topbraid-users] oneOf in shacl

2018-10-31 Thread Holger Knublauch
Yes, sh:in at a node shape states that all target nodes (here: the instances of ex2:Category) must be one of the enumerated values. Holger On 1/11/2018 2:29 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote: ex2:Category   rdf:type owl:Class ;   rdf:type sh:NodeShape ;

RE: [topbraid-users] sh:nodeKind questions

2018-10-31 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Ok thx So if my owl properties always have range...my shacl always has a datatype or class...so then no need to use nodeshape at all..right? The simpler the better Verzonden van mijn Android-telefoon via TouchDown (www.symantec.com) -Original Message- From: Irene Polikoff

Re: [topbraid-users] sh:nodeKind questions

2018-10-31 Thread Irene Polikoff
Typically, you only need to specify sh:nodeKind if you can’t specify the sh:datatype or sh:class. For example, if you can’t say whether the value is a string or an integer, you could use sh:nodeKind to say that it is a literal. > On Oct 31, 2018, at 11:23 AM, 'Bohms, H.M. (Michel)' via

RE: [topbraid-users] sh:nodeKind questions

2018-10-31 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Hi David That is my point. The spec is not clear on when to use, nor specifies a default. Tbc is not generating. I was thinking it could be relevant to translate the fact that property is an owl datatype property or object property in shacl. (kind of implicit constraint). But then when the

[topbraid-users] oneOf in shacl

2018-10-31 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
ex2:Category rdf:type owl:Class ; rdf:type sh:NodeShape ; rdfs:subClassOf owl:Thing ; owl:oneOf ( ex2:Pub ex2:Adult ex2:Senior ) ; . What would the shacl look like for the yellow part? sh:in (ex2:Pub ex2:Adult ex2:Senior) ; Somehowbut it is not in a property

Re: [topbraid-users] sh:nodeKind questions

2018-10-31 Thread dprice
> On 31 Oct 2018, at 15:23, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > wrote: > > You once explained but I cant refind. > What are the rules for sh:nodeKind? Here’s the official W3C spec: https://www.w3.org/TR/shacl/#NodeKindConstraintComponent