RE: [topbraid-users] Staying with official SHACL

oups.com Onderwerp: Re: [topbraid-users] Staying with official SHACL On 22/06/2021 9:10 am, Steve Ray wrote: Hi Holger, Things are looking good on my end using TBC 7.0.1 and only importing the SHACL URI and not dash or tosh. Running SHACL reasoning and SHACL validation both seem to work reli

Re: [topbraid-users] Staying with official SHACL

On 22/06/2021 9:10 am, Steve Ray wrote: Hi Holger, Things are looking good on my end using TBC 7.0.1 and only importing the SHACL URI and not dash or tosh. Running SHACL reasoning and SHACL validation both seem to work reliably. I'm assuming that, as you mentioned, dash and/or tosh are

Re: [topbraid-users] Staying with official SHACL

Hi Holger, Things are looking good on my end using TBC 7.0.1 and only importing the SHACL URI and not dash or tosh. Running SHACL reasoning and SHACL validation both seem to work reliably. I'm assuming that, as you mentioned, dash and/or tosh are brought in automatically if needed. The only

RE: [topbraid-users] Staying with official SHACL

Knublauch Verzonden: maandag 21 juni 2021 00:58 Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> Onderwerp: Re: [topbraid-users] Staying with official SHACL In addition to the extra constraint components http://datashapes.org/constraints.html the dash nam

Re: [topbraid-users] Staying with official SHACL

it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. *Van:* topbraid-users@googlegroups.com *Namens *Holger Knublauch *Verzonden:* maandag 21 juni 2021 00:58 *Aan:* topbraid-users@googlegroups.com *Onderwerp:* Re: [topbraid-users] Staying w

RE: [topbraid-users] Staying with official SHACL

messages. Van: topbraid-users@googlegroups.com Namens Holger Knublauch Verzonden: maandag 21 juni 2021 00:58 Aan: topbraid-users@googlegroups.com Onderwerp: Re: [topbraid-users] Staying with official SHACL In addition to the extra constraint components http://datashapes.org/constrai

Re: [topbraid-users] Staying with official SHACL

In addition to the extra constraint components     http://datashapes.org/constraints.html the dash namespace also imports the tosh namespace, which contains constraints on the SHACL metamodel and therefore is used to drive the forms in EDG. What you do with the files generated with TopBraid

Re: [topbraid-users] Staying with official SHACL

If you have no need for it, you don’t have to use it, just like you don’t have to use every single feature of SHACL. > On Jun 20, 2021, at 12:12 PM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > wrote: > >  > Ok butthat stuff is not used internally, like when checking shacl? > Ie if

Re: [topbraid-users] Staying with official SHACL

Ok butthat stuff is not used internally, like when checking shacl? Ie if we do not use it...no issue? Thx Op 20 jun. 2021 04:59 schreef Irene Polikoff : This is very easy to find out. Just go to http://datashapes.org/dash. All functionality is explained in detail. On Jun 19, 2021, at 5:48

Re: [topbraid-users] Staying with official SHACL

This is very easy to find out. Just go to http://datashapes.org/dash. All functionality is explained in detail. > On Jun 19, 2021, at 5:48 PM, Steve Ray wrote: > > Very cool! With bated breath, I tried it, and nothing blew up! > > It would be good to know at some point what functionality I

Re: [topbraid-users] Staying with official SHACL

Very cool! With bated breath, I tried it, and nothing blew up! It would be good to know at some point what functionality I lose by directly importing owl:imports ; instead of owl:imports ; Steve On Sat, Jun 19, 2021 at 3:36 AM

Re: [topbraid-users] Staying with official SHACL

Hi Steve and Michel I’m not near my computer so cannot do it for you, but suggest replacing dash import with SHACL import and trying it. I think that’s ok. Cheers, David > On 19 Jun 2021, at 08:44, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > wrote: > >  > I have exactly the same

RE: [topbraid-users] Staying with official SHACL

I have exactly the same issue in CEN TC442/WG4/TG3 …. I now have: # baseURI: https://w3id.org/sml/shacl/def # imports: https://w3id.org/sml/rdfs/def # imports: http://datashapes.org/dash # imports: http://qudt.org/schema/qudt # imports: http://qudt.org/vocab/quantitykind # imports: