In EDG, shapes can only be defined in Ontology asset collections (or files in the workspace). Any EDG Ontology will automatically import dash and tosh. Therefore, once you import a file into an EDG ontology, the ontolgy will already use dash and tosh automatically, so that the forms etc work as they should.

Holger


On 2021-06-21 4:44 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:

Ahh, ok, these were the dependencies I was looking for! I guess Steve too.

So we have to remember to add in case of EDG-usage. Right?

(or is the use by EDG always via the shacl api so that is automatic?)

        

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 [email protected] <mailto:[email protected]>

        

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

<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:* [email protected] <[email protected]> *Namens *Holger Knublauch
*Verzonden:* maandag 21 juni 2021 00:58
*Aan:* [email protected]
*Onderwerp:* Re: [topbraid-users] Staying with official SHACL

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
    <[email protected] <mailto:[email protected]>> 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 <[email protected]
            <mailto:[email protected]>> 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 [email protected] <mailto:[email protected]>

                

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

            <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:* [email protected]
            <mailto:[email protected]>
            <[email protected]
            <mailto:[email protected]>> *Namens *Steve Ray
            *Verzonden:* vrijdag 18 juni 2021 21:58
            *Aan:* TopBraid Suite Users
            <[email protected]
            <mailto:[email protected]>>
            *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
            [email protected]
            <mailto:[email protected]>.
            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
            [email protected]
            <mailto:[email protected]>.
            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
        [email protected]
        <mailto:[email protected]>.
        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 [email protected]
    <mailto:[email protected]>.
    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 [email protected] <mailto:[email protected]>. 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 [email protected] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/fb33c36fd56a4f98b6da690fa45be981%40tno.nl <https://groups.google.com/d/msgid/topbraid-users/fb33c36fd56a4f98b6da690fa45be981%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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/92287562-a7d3-dbe9-cf91-3d9e97a4ddd8%40topquadrant.com.

Reply via email to