There have been some other changes to the converter, in Java code. We could revert the process however - if someone wants to send me their OWL files (off or on list), I could use them to test the converter and send the outcome back.

Holger


On 30/08/2017 23:45, Irene Polikoff wrote:
I wonder if we could just send you the files with updated conversion rules from 5.4, so you could test it. Holger, what do you think?

On Aug 30, 2017, at 2:56 AM, Bohms, H.M. (Michel) <[email protected] <mailto:[email protected]>> wrote:

Ok, clear
I note that it doesn’t help here when the better subClassOf iso equivalentClass is used. Wrt to the simple restriction: it does not seem to convert either in 5.3.2. So I’ll wait for the release of 5.4 for that. Below you see the result after conversion (this time without deleting the original owl/rdfs restrictions):
:BigSpace
  rdf:type owl:Class ;
  rdf:type sh:NodeShape ;
  rdfs:subClassOf :Space ;
  rdfs:subClassOf [
      rdf:type owl:Restriction ;
owl:allValuesFrom :BigPump ;
      owl:onProperty :hasPump ;
    ] ;
  owl:disjointWith :SmallSpace ;
  owl:equivalentClass [
      rdf:type owl:Restriction ;
owl:allValuesFrom [
          rdf:type rdfs:Datatype ;
owl:onDatatype xsd:float ;
owl:withRestrictions (
              [
     xsd:minExclusive "150.0"^^xsd:float ;
              ]
            ) ;
        ] ;
      owl:onProperty :area ;
    ] ;
.
As you can see only
  rdf:type sh:NodeShape ;
has been added.
Greetings Michel
        
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist

        
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
        
Location <https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.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:*[email protected] <mailto:[email protected]>[mailto:[email protected]]*On Behalf Of*Holger Knublauch
*Sent:*woensdag 30 augustus 2017 00:43
*To:*[email protected] <mailto:[email protected]>
*Subject:*Re: [topbraid-users] my first shacl try
On 30/08/2017 3:15, Irene Polikoff wrote:

    Michel,
    I have not tried the OWL to SHACL converter in 5.3, only in the
    5.4 which is not yet generally available.
    The converter is “work in progress” and I know that it was
    extended for 5.4. However, it will not convert all possible
    combinations of OWL axioms. Only the most common ones. To decide
    what constitute a common pattern, we looked at several well known
    ontologies such as FIBO and picked patterns that cover 80-90% of
    the modeling axioms.
    Based on my 5.4 experience:

          rdfs:subClassOf [
              rdf:type owl:Restriction ;
              owl:allValuesFrom :BigPump ;
              owl:onProperty :hasPump ;
            ] ;

    Should be converted
    You should see something like

        :BigSpace

    sh:property [
    sh:path :hasPump ;
    sh:class :BigPump ;
    ]

          owl:equivalentClass [
              rdf:type owl:Restriction ;
              owl:allValuesFrom [
                  rdf:type rdfs:Datatype ;
                  owl:onDatatype xsd:float ;
                  owl:withRestrictions (
                      [
                        xsd:minExclusive "150.0"^^xsd:float ;
                      ]
                    ) ;
                ] ;
              owl:onProperty :area ;
        ] ;

    Will not be converted. It is not one of the patterns we currently
    support in the conversion.


Yes, this is because owl:equivalentClass axioms really do carry different meaning, and we don't want to pretend that they can be converted automatically. Some manual post-processing will be needed in these cases, e.g. converting them to SHACL-AF rules.

Holger



        On Aug 29, 2017, at 10:45 AM, Bohms, H.M. (Michel)
        <[email protected] <mailto:[email protected]>> wrote:
        Hi Irene,
        When converting the owl restrictions to SHACL within tbc, the
        2 restrictions from:
        :BigSpace
          rdf:type owl:Class ;
          rdfs:subClassOf :Space ;
          rdfs:subClassOf [
              rdf:type owl:Restriction ;
              owl:allValuesFrom :BigPump ;
              owl:onProperty :hasPump ;
            ] ;
          owl:disjointWith :SmallSpace ;
          owl:equivalentClass [
              rdf:type owl:Restriction ;
              owl:allValuesFrom [
                  rdf:type rdfs:Datatype ;
                  owl:onDatatype xsd:float ;
        owl:withRestrictions (
                      [
        xsd:minExclusive "150.0"^^xsd:float ;
                      ]
                    ) ;
                ] ;
              owl:onProperty :area ;
        ] ;
        .
        Seem not converted.
        Was this to be expected?
        What IS generated, I do not understand:
        [
          rdf:type rdfs:Datatype ;
          owl:onDatatype :area ;
        ].
        [
          rdf:type rdfs:Datatype ;
          owl:onDatatype :area ;
        ].
        [
          sh:class :BigPump ;
        ].
        [
          sh:class :SmallPump ;
        ].
        Thx Michel
                
        Dr. ir. H.M. (Michel) Böhms
        Senior Data Scientist


                
        T +31888663107
        M +31630381220
        E [email protected] <mailto:[email protected]>
                
        Location
        
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.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.

        --
        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
        [email protected]
        <mailto:[email protected]>.
        For more options, visithttps://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 [email protected]
    <mailto:[email protected]>.
    For more options, visithttps://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 [email protected] <mailto:[email protected]>.
For more options, visithttps://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 [email protected] <mailto:[email protected]>.
For more options, visithttps://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 [email protected] <mailto:[email protected]>.
For more options, visit 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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to