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 brought in automatically if needed.

The only exception is a summer student working on the standards project who is using the TBC Free edition (which seems to have moved backwards to 6.0.1). It seems to choke when validating because it isn't finding some tosh objects. (Caused by: java.lang.IllegalArgumentException: Shapes graph does not include tosh:http://datashapes.org/dash#DefaultValueTypeRule <http://datashapes.org/dash#DefaultValueTypeRule>)

The workaround for the student is just to have him explicitly import dash.ttl whenever he wants to run the validator, but remove it before doing his git push. I know that you all aren't supporting TBC Free any more, but I just wanted to confirm that this is expected behavior.

Yes this sounds plausible. The SHACL engine in that version was different.

Holger



Steve




On Sun, Jun 20, 2021 at 3:58 PM Holger Knublauch <hol...@topquadrant.com <mailto:hol...@topquadrant.com>> wrote:

    In addition to the extra constraint components

    http://datashapes.org/constraints.html
    <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 outside of
    TopBraid is of course your own decision. I assume all
    standards-compliant SHACL validation engines will support at least
    SHACL Core without any mandatory owl:imports. In the SHACL API
    that I wrote, the code uses dash and tosh internally to identify
    the constraint components, so they are internally added in case
    they don't exist in the provided shapes graph. But this happens
    automatically.

    Holger


    On 2021-06-20 7:48 am, 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 lose
    by directly importing
    owl:imports<http://www.w3.org/ns/shacl#
    <http://www.w3.org/ns/shacl#>>;
    instead of
    owl:imports<http://datashapes.org/dash <http://datashapes.org/dash>>;
    Steve




    On Sat, Jun 19, 2021 at 3:36 AM David Price
    <dpr...@topquadrant.com <mailto:dpr...@topquadrant.com>> wrote:

        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 <topbraid-users@googlegroups.com
        <mailto:topbraid-users@googlegroups.com>> wrote:

        

        I have exactly the same issue in CEN TC442/WG4/TG3 ….

        I now have:

        # baseURI: https://w3id.org/sml/shacl/def
        <https://w3id.org/sml/shacl/def>

        # imports: https://w3id.org/sml/rdfs/def
        <https://w3id.org/sml/rdfs/def>

        # imports: http://datashapes.org/dash
        <http://datashapes.org/dash>

        # imports: http://qudt.org/schema/qudt
        <http://qudt.org/schema/qudt>

        # imports: http://qudt.org/vocab/quantitykind
        <http://qudt.org/vocab/quantitykind>

        # imports: http://qudt.org/vocab/unit
        <http://qudt.org/vocab/unit>

        # imports: http://www.w3.org/2004/02/skos/core
        <http://www.w3.org/2004/02/skos/core>

        # imports: https://www.w3.org/2006/time
        <https://www.w3.org/2006/time>

        # prefix: sml

        @prefix dash: <http://datashapes.org/dash#
        <http://datashapes.org/dash#>> .

        @prefix sml: <https://w3id.org/sml/def#
        <https://w3id.org/sml/def#>> .

        @prefix owl: <http://www.w3.org/2002/07/owl#
        <http://www.w3.org/2002/07/owl#>> .

        @prefix quantitykind: <http://qudt.org/vocab/quantitykind/
        <http://qudt.org/vocab/quantitykind/>> .

        @prefix qudt: <http://qudt.org/schema/qudt/
        <http://qudt.org/schema/qudt/>> .

        @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#
        <http://www.w3.org/1999/02/22-rdf-syntax-ns#>> .

        @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#
        <http://www.w3.org/2000/01/rdf-schema#>> .

        @prefix sh: <http://www.w3.org/ns/shacl#
        <http://www.w3.org/ns/shacl#>> .

        @prefix skos: <http://www.w3.org/2004/02/skos/core#
        <http://www.w3.org/2004/02/skos/core#>> .

        @prefix time: <http://www.w3.org/2006/time#
        <http://www.w3.org/2006/time#>> .

        @prefix unit: <http://qudt.org/vocab/unit/
        <http://qudt.org/vocab/unit/>> .

        @prefix xsd: <http://www.w3.org/2001/XMLSchema#
        <http://www.w3.org/2001/XMLSchema#>> .

        <https://w3id.org/sml/shacl/def
        <https://w3id.org/sml/shacl/def>>

          a owl:Ontology ;

        owl:imports <https://w3id.org/sml/rdfs/def
        <https://w3id.org/sml/rdfs/def>> ;

          owl:imports <http://datashapes.org/dash
        <http://datashapes.org/dash>> ;

        owl:imports <http://qudt.org/schema/qudt
        <http://qudt.org/schema/qudt>> ;

        owl:imports <http://qudt.org/vocab/quantitykind
        <http://qudt.org/vocab/quantitykind>> ;

        owl:imports <http://qudt.org/vocab/unit
        <http://qudt.org/vocab/unit>> ;

        owl:imports <https://www.w3.org/2006/time
        <https://www.w3.org/2006/time>> ;

        .

        Etc.

        But people question the red.

        Thx michel

                

        Dr. ir. H.M. (Michel) Bohms
        Scientist Specialist
        Structural Reliability

                

        T +31 (0)88 866 31 07
        M +31 (0)63 038 12 20
        E michel.bo...@tno.nl <mailto:michel.bo...@tno.nl>

                

        Location <http://www.tno.nl/locations/DTS>

        <http://www.tno.nl/>

        <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.


        *Van:* topbraid-users@googlegroups.com
        <mailto:topbraid-users@googlegroups.com>
        <topbraid-users@googlegroups.com
        <mailto:topbraid-users@googlegroups.com>> *Namens *Steve Ray
        *Verzonden:* vrijdag 18 juni 2021 21:58
        *Aan:* TopBraid Suite Users <topbraid-users@googlegroups.com
        <mailto:topbraid-users@googlegroups.com>>
        *Onderwerp:* [topbraid-users] Staying with official SHACL

        Hi, I'm working with a standards committee that would rather
        avoid straying outside the official W3C SHACL standard. My
        question is, if I removed the import of datashapes.org/dash
        <http://datashapes.org/dash> from the files I'm working
        with, does this bring the TopQuadrant tools to a crashing
        halt as far as running the SHACL reasoner?

        I suppose another way of asking this is whether SHACL is
        built in to TBC under the hood, or is the dash import part
        of that?


        Steve

-- 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>.
        To view this discussion on the web visit
        
https://groups.google.com/d/msgid/topbraid-users/CAGUep84C6i_88CtyP2ySiMBO-%2B2S_4p94Qxvt3N3Q%3DBipW2h1A%40mail.gmail.com
        
<https://groups.google.com/d/msgid/topbraid-users/CAGUep84C6i_88CtyP2ySiMBO-%2B2S_4p94Qxvt3N3Q%3DBipW2h1A%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 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>.
        To view this discussion on the web visit
        
https://groups.google.com/d/msgid/topbraid-users/45ec57df22fb4a5f8a637eae87ed79f9%40tno.nl
        
<https://groups.google.com/d/msgid/topbraid-users/45ec57df22fb4a5f8a637eae87ed79f9%40tno.nl?utm_medium=email&utm_source=footer>.
-- 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>.
        To view this discussion on the web visit
        
https://groups.google.com/d/msgid/topbraid-users/38AE1500-E4BB-4DA2-AD81-D623A9221906%40topquadrant.com
        
<https://groups.google.com/d/msgid/topbraid-users/38AE1500-E4BB-4DA2-AD81-D623A9221906%40topquadrant.com?utm_medium=email&utm_source=footer>.

-- 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>.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/topbraid-users/CAGUep86D%3DFKTtW4dck9o6T2e9j95-Ho8fuZ9VdMU8wkwpheYHQ%40mail.gmail.com
    
<https://groups.google.com/d/msgid/topbraid-users/CAGUep86D%3DFKTtW4dck9o6T2e9j95-Ho8fuZ9VdMU8wkwpheYHQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
-- 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>.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/topbraid-users/54aaaf01-6fd3-1d54-d115-2fb9e58e988f%40topquadrant.com
    
<https://groups.google.com/d/msgid/topbraid-users/54aaaf01-6fd3-1d54-d115-2fb9e58e988f%40topquadrant.com?utm_medium=email&utm_source=footer>.

--
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>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAGUep85wTqzokE_69F3E1DiJY%3DfuA26TmVPvXvBbhVRpSDokyg%40mail.gmail.com <https://groups.google.com/d/msgid/topbraid-users/CAGUep85wTqzokE_69F3E1DiJY%3DfuA26TmVPvXvBbhVRpSDokyg%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/2fa4528c-877a-6e9b-364c-64b53496824b%40topquadrant.com.

Reply via email to