unexpected parsing beavior

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

unexpected parsing beavior

Dietze, Frank
Hi all,
I'm using Protege 4.0 and found the following parsing effect:
 
If I create an annotation, the RDF/XML-rendering shows this:
 
    <!--
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Individuals
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->
 
 
 
 
 
    <owl:Thing rdf:about="#Frank">
        <rdf:type rdf:resource="#Man"/>
    </owl:Thing>
 
 
 
 
    <owl:Thing rdf:about="#Jakob">
        <rdf:type rdf:resource="#Person"/>
        <hasFather rdf:resource="#Frank"/>
    </owl:Thing>
    <rdf:Description>
        <rdf:type rdf:resource="&owl;Axiom"/>
        <owl:object rdf:resource="#Frank"/>
        <owl:subject rdf:resource="#Jakob"/>
        <isStatedBy rdf:resource="#Rolf"/>
        <owl:predicate rdf:resource="#hasFather"/>
    </rdf:Description>
 
 
 
 
    <owl:Thing rdf:about="#Rolf">
        <rdf:type rdf:resource="#Man"/>
        <hasBrother rdf:resource="#Frank"/>
    </owl:Thing>
 
Closing the editor and opening the same file again, the rendering shows in this section:
 
   <!--
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Individuals
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->
 
 
 
 
 
    <owl:Thing rdf:about="#Frank">
        <rdf:type rdf:resource="#Man"/>
    </owl:Thing>
 
 
 
 
    <owl:Thing rdf:about="#Jakob">
        <rdf:type rdf:resource="#Person"/>
        <hasFather rdf:resource="#Frank"/>
    </owl:Thing>
 
 
 
 
    <owl:Thing rdf:about="#Rolf">
        <rdf:type rdf:resource="#Man"/>
        <hasBrother rdf:resource="#Frank"/>
    </owl:Thing>
 
 
 
 
    <rdf:Description>
        <isStatedBy rdf:resource="#Rolf"/>
    </rdf:Description>
 
There is a magic change from an annotation of a property assertion to an annotation of a new generated individual!
This also happens with self-generated .owl-files containing highlighted elements.
What is the reason for that?
 
Best regards.
Frank
 
 
Frank Dietze
Thesis Student   I   SAP Research Dresden
SAP AG   I   Chemnitzer Str. 48   I   01187 Dresden   I   Germany
 
T +49 351 4811-6170   I   F +49 6227 78-56297   I   [hidden email]
 
 
Pflichtangaben/Mandatory Disclosure Statements:
http://www.sap.com/company/legal/impressum.epx
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
 
 
 
 

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Reply | Threaded
Open this post in threaded view
|

Re: unexpected parsing beavior

Matthew Horridge-2
Administrator
Hi Frank,

Is there a reason why you're not using Protege 4.1?  You should really switch to 4.1 if you can and these problems should disappear.  

Cheers,

Matthew


On 30 Sep 2011, at 01:29, Dietze, Frank wrote:

> Hi all,
> I'm using Protege 4.0 and found the following parsing effect:
>  
> If I create an annotation, the RDF/XML-rendering shows this:
>  
>     <!--
>     ///////////////////////////////////////////////////////////////////////////////////////
>     //
>     // Individuals
>     //
>     ///////////////////////////////////////////////////////////////////////////////////////
>      -->
>  
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Frank -->
>  
>     <owl:Thing rdf:about="#Frank">
>         <rdf:type rdf:resource="#Man"/>
>     </owl:Thing>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Jakob -->
>  
>     <owl:Thing rdf:about="#Jakob">
>         <rdf:type rdf:resource="#Person"/>
>         <hasFather rdf:resource="#Frank"/>
>     </owl:Thing>
>     <rdf:Description>
>         <rdf:type rdf:resource="&owl;Axiom"/>
>         <owl:object rdf:resource="#Frank"/>
>         <owl:subject rdf:resource="#Jakob"/>
>         <isStatedBy rdf:resource="#Rolf"/>
>         <owl:predicate rdf:resource="#hasFather"/>
>     </rdf:Description>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Rolf -->
>  
>     <owl:Thing rdf:about="#Rolf">
>         <rdf:type rdf:resource="#Man"/>
>         <hasBrother rdf:resource="#Frank"/>
>     </owl:Thing>
>  
> Closing the editor and opening the same file again, the rendering shows in this section:
>  
>    <!--
>     ///////////////////////////////////////////////////////////////////////////////////////
>     //
>     // Individuals
>     //
>     ///////////////////////////////////////////////////////////////////////////////////////
>      -->
>  
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Frank -->
>  
>     <owl:Thing rdf:about="#Frank">
>         <rdf:type rdf:resource="#Man"/>
>     </owl:Thing>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Jakob -->
>  
>     <owl:Thing rdf:about="#Jakob">
>         <rdf:type rdf:resource="#Person"/>
>         <hasFather rdf:resource="#Frank"/>
>     </owl:Thing>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Rolf -->
>  
>     <owl:Thing rdf:about="#Rolf">
>         <rdf:type rdf:resource="#Man"/>
>         <hasBrother rdf:resource="#Frank"/>
>     </owl:Thing>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#genid6 -->
>  
>     <rdf:Description>
>         <isStatedBy rdf:resource="#Rolf"/>
>     </rdf:Description>
>  
> There is a magic change from an annotation of a property assertion to an annotation of a new generated individual!
> This also happens with self-generated .owl-files containing highlighted elements.
> What is the reason for that?
>  
> Best regards.
> Frank
>  
>  
> Frank Dietze
> Thesis Student   I   SAP Research Dresden
> SAP AG   I   Chemnitzer Str. 48   I   01187 Dresden   I   Germany
>  
> T +49 351 4811-6170   I   F +49 6227 78-56297   I   mailto:[hidden email]
> www.sap.com
>  
>  
> Pflichtangaben/Mandatory Disclosure Statements:
> http://www.sap.com/company/legal/impressum.epx 
> Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.
>
> This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
>  
>  
>  
>  
> _______________________________________________
> protege-owl mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Reply | Threaded
Open this post in threaded view
|

Re: unexpected parsing beavior

Dietze, Frank
Hi Matthew,

this works fine.
I should more frequently look for new versions.

Greetings,
Frank



-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Matthew Horridge
Sent: Freitag, 30. September 2011 18:10
To: User support for the Protege-OWL editor
Subject: Re: [protege-owl] unexpected parsing beavior

Hi Frank,

Is there a reason why you're not using Protege 4.1?  You should really switch to 4.1 if you can and these problems should disappear.  

Cheers,

Matthew


On 30 Sep 2011, at 01:29, Dietze, Frank wrote:

> Hi all,
> I'm using Protege 4.0 and found the following parsing effect:
>  
> If I create an annotation, the RDF/XML-rendering shows this:
>  
>     <!--
>     ///////////////////////////////////////////////////////////////////////////////////////
>     //
>     // Individuals
>     //
>     ///////////////////////////////////////////////////////////////////////////////////////
>      -->
>  
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Frank -->
>  
>     <owl:Thing rdf:about="#Frank">
>         <rdf:type rdf:resource="#Man"/>
>     </owl:Thing>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Jakob -->
>  
>     <owl:Thing rdf:about="#Jakob">
>         <rdf:type rdf:resource="#Person"/>
>         <hasFather rdf:resource="#Frank"/>
>     </owl:Thing>
>     <rdf:Description>
>         <rdf:type rdf:resource="&owl;Axiom"/>
>         <owl:object rdf:resource="#Frank"/>
>         <owl:subject rdf:resource="#Jakob"/>
>         <isStatedBy rdf:resource="#Rolf"/>
>         <owl:predicate rdf:resource="#hasFather"/>
>     </rdf:Description>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Rolf -->
>  
>     <owl:Thing rdf:about="#Rolf">
>         <rdf:type rdf:resource="#Man"/>
>         <hasBrother rdf:resource="#Frank"/>
>     </owl:Thing>
>  
> Closing the editor and opening the same file again, the rendering shows in this section:
>  
>    <!--
>     ///////////////////////////////////////////////////////////////////////////////////////
>     //
>     // Individuals
>     //
>     ///////////////////////////////////////////////////////////////////////////////////////
>      -->
>  
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Frank -->
>  
>     <owl:Thing rdf:about="#Frank">
>         <rdf:type rdf:resource="#Man"/>
>     </owl:Thing>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Jakob -->
>  
>     <owl:Thing rdf:about="#Jakob">
>         <rdf:type rdf:resource="#Person"/>
>         <hasFather rdf:resource="#Frank"/>
>     </owl:Thing>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#Rolf -->
>  
>     <owl:Thing rdf:about="#Rolf">
>         <rdf:type rdf:resource="#Man"/>
>         <hasBrother rdf:resource="#Frank"/>
>     </owl:Thing>
>  
>  
>  
>     <!-- http://www.semanticweb.org/ontologies/2011/Ontology1312206740715.owl#genid6 -->
>  
>     <rdf:Description>
>         <isStatedBy rdf:resource="#Rolf"/>
>     </rdf:Description>
>  
> There is a magic change from an annotation of a property assertion to an annotation of a new generated individual!
> This also happens with self-generated .owl-files containing highlighted elements.
> What is the reason for that?
>  
> Best regards.
> Frank
>  
>  
> Frank Dietze
> Thesis Student   I   SAP Research Dresden
> SAP AG   I   Chemnitzer Str. 48   I   01187 Dresden   I   Germany
>  
> T +49 351 4811-6170   I   F +49 6227 78-56297   I   mailto:[hidden email]
> www.sap.com
>  
>  
> Pflichtangaben/Mandatory Disclosure Statements:
> http://www.sap.com/company/legal/impressum.epx 
> Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.
>
> This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
>  
>  
>  
>  
> _______________________________________________
> protege-owl mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03