Re: ObjectProprerty Restrictions not generating in RDFXML

Posted by MartyStache on
URL: http://owlready.306.s1.nabble.com/ObjectProprerty-Restrictions-not-generating-in-RDFXML-tp2124p2140.html

Maybe safest bet is to only enter a min?
Then there is a restriction on min, but none on max?


From: cknoll [via Owlready] <[hidden email]>
Sent: Tuesday, December 1, 2020 5:42:55 AM
To: Tim Duval <[hidden email]>
Subject: Re: ObjectProprerty Restrictions not generating in RDFXML
 
I am not sure but using `None` leads to

    <owl:Restriction>
      <owl:onProperty rdf:resource="#has_Equipments"/>
      <owl:onClass rdf:resource="#Equipment"/>
    </owl:Restriction>

which seems to "disable" the max-restriction.

On the other hand you could pass any string e.g. "inf" or "foobar" or "*". This string value ends up in the XML (without the quotes). So it depends what the program with which you will open the xml expects. (I do not know what the standard is for such case.)

Example: `EquipmentContainer.is_a.append(has_Equipments.max("*", Equipment))` leads to

<owl:Restriction>
      <owl:onProperty rdf:resource="#has_Equipments"/>
      <owl:onClass rdf:resource="#Equipment"/>
      <owl:maxQualifiedCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">*</owl:maxQualifiedCardinality>
</owl:Restriction>

Best,
Carsten


If you reply to this email, your message will be added to the discussion below:
http://owlready.8326.n8.nabble.com/ObjectProprerty-Restrictions-not-generating-in-RDFXML-tp2124p2132.html
To unsubscribe from ObjectProprerty Restrictions not generating in RDFXML, click here.
NAML