Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-owl] While importing OWLs with unions, protege 3 produces invalid owl files.

Pallinger Péter pallinger at dsd.sztaki.hu
Tue Mar 10 06:37:27 PDT 2009


The error is as follows:

If you include an ontology (ptest.owl) that has a class definition like this:
-----
<owl:Class rdf:ID="Process">
  <owl:unionOf rdf:parseType="Collection">
    <owl:Class rdf:about="#AtomicProcess"/>
    <owl:Class rdf:about="#SimpleProcess"/>
    <owl:Class rdf:about="#CompositeProcess"/>
  </owl:unionOf>
</owl:Class>
-----

Into a file (test.owl) that has a reference to the above class like this:
-----
<owl:Class rdf:about="http://www.daml.org/services/owl-s/1.1/Process.owl#Process"/>
-----

Loading and saving the file (test.owl) in protege produces the following construct:
-----
  <owl:Class rdf:about="http://www.daml.org/services/owl-s/1.1/Process.owl#Process">
    <owl:equivalentClass>
      <owl:Class>
        <owl:unionOf rdf:parseType="Resource">
        </owl:unionOf>
      </owl:Class>
    </owl:equivalentClass>
  </owl:Class>
-----

The above is not valid OWL (unionOf should get a List, instead it gets a single blank node).


On the other hand, if the included file (include34.owl) contains a class definition like
this (This is generated, if you load include.owl into protege 3.4 and save it back):
-----
  <owl:Class rdf:ID="Process">
    <owl:equivalentClass>
      <owl:Class>
        <owl:unionOf rdf:parseType="Collection">
          <owl:Class rdf:ID="AtomicProcess"/>
          <owl:Class rdf:ID="SimpleProcess"/>
          <owl:Class rdf:ID="CompositeProcess"/>
        </owl:unionOf>
      </owl:Class>
    </owl:equivalentClass>
  </owl:Class>
-----

Then it produces a valid file, containing:
-----
<owl:Class rdf:about="http://www.daml.org/services/owl-s/1.1/Process.owl#Process"/>
-----

This concludes that the error would not manifest itself for ontologies where all files
are edited by protégé 3.4. However, external ontologies like
http://www.daml.org/services/owl-s/1.1/ do produce problems due to this error.

This error is produced by Protégé 3.4 rc, but not by Protégé 4.0 beta.

I have attached the three mentioned owl files. If you want to test them, please change
the import paths in test.owl.

Best regards,
	PP
-------------- next part --------------
A non-text attachment was scrubbed...
Name: include.owl
Type: text/rdf
Size: 801 bytes
Desc: not available
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20090310/7edf7760/attachment.owl>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: include34.owl
Type: text/rdf
Size: 751 bytes
Desc: not available
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20090310/7edf7760/attachment-0001.owl>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.owl
Type: text/rdf
Size: 943 bytes
Desc: not available
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20090310/7edf7760/attachment-0002.owl>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20090310/7edf7760/attachment.asc>


More information about the protege-owl mailing list