I suggested sh:class because this would include subclasses of classes in the constraint. If the exact match, not included subclasses, is desired, then one could do sh:in constraint on rdf:type.
> On Dec 6, 2018, at 8:25 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > <topbraid-users@googlegroups.com> wrote: > > > Not using sh:in somehow ? > > (I have similar constraints in situations where enumeration datatypes are > modelled as classes but where the actual allowed subset differs per domain > (sub)class; ie a range is not specific enough) > > I also would like to know what the manual shacl code looks like in the end… > > > Dr. ir. H.M. (Michel) Böhms > Senior Data Scientist > > T +31888663107 > M +31630381220 > E michel.bo...@tno.nl <mailto:michel.bo...@tno.nl> > Location > <https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=!3m1!4b1!4m5!3m4!1s0x47c5b58c52869997:0x56681566be3b8c88!8m2!3d52.000788!4d4.376707> > > > <image001.gif> <http://www.tno.nl/> > This message may contain information that is not intended for you. If you are > not the addressee or if this message was sent to you by mistake, you are > requested to inform the sender and delete the message. TNO accepts no > liability for the content of this e-mail, for the manner in which you use it > and for damage of any kind resulting from the risks inherent to the > electronic transmission of messages. > > > > > From: topbraid-users@googlegroups.com > <mailto:topbraid-users@googlegroups.com> <topbraid-users@googlegroups.com > <mailto:topbraid-users@googlegroups.com>> On Behalf Of Irene Polikoff > Sent: donderdag 6 december 2018 08:07 > To: topbraid-users@googlegroups.com <mailto:topbraid-users@googlegroups.com> > Subject: Re: [topbraid-users] Converting owl:allValuesFrom restriction to > SHACL > > Patrick, > > Most likely your guess is correct. > > Conversion is performed using SHACL rules. To see (and modify if needed) > rules, o to the TopBraid project, then open owl2shacl.ttl under SHACL. If I > understand your model correctly, in SHACL you would use sh:class constraint > with an sh:or statement. > > Or, if you do not want to extend the rules, change your OWL model so that you > have and your restriction uses a parent class of identity:IndividualInfo and > OrganizationalInfo. > > > On Dec 6, 2018, at 1:55 AM, Paul Patrick <paul.patrick...@gmail.com > <mailto:paul.patrick...@gmail.com>> wrote: > > I've been working with the new capability to convert OWL/RDFS to SHACL on > some of my ontology files but ran into something that I thought would be > converted. When I run the converter, it states the following: > > The conversation has been completed although 1 anonymous superclasses were > not converted (these will be shown in a References view). > > when I investigate the references view, I see its a class level > owl:allValuesFrom restriction on an object property similar to what is > described in the blog post "From OWL to SHACL in an Automated Way". The post > states that: > > owl:allValuesFrom statements are converted to property shapes with either > sh:class (for object properties) or sh:datatype constraint components > > The difference I see is that my class is defined as > > identity:Identity > rdf:type owl:Class ; > rdfs:subClassOf ctiDomain:DomainBase > rdfs:subClassOf [ > rdf:type owl:Restriction ; > owl:allValuesFrom [ > rdf:type owl:Class ; > owl:oneOf ( > identity:IndividualInfo > identity:OrganizationalInfo > ) ; > ] ; > owl:onProperty cti:extensions ; > ] . > > I'm wondering if it the anonymous class for the owl:oneOf that is creating > the issue and stops the conversation process from adding the values in the > oneOf to the sh:class property of the identity:Identity-extensions constraint. > > Any suggestions as I'd like to see if I can generate the SHACL without the > need to hand-modify the shapes file > > Thanks in advance > > > > -- > 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-users+unsubscr...@googlegroups.com > <mailto:topbraid-users+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > 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-users+unsubscr...@googlegroups.com > <mailto:topbraid-users+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > 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-users+unsubscr...@googlegroups.com > <mailto:topbraid-users+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
