1 / 10

New Zoo Ontology Diagram for OWL Representation

Explore the new Owl diagram with extended classes and properties for zoo management and knowledge on the internet.

joelle-harmon
Download Presentation

New Zoo Ontology Diagram for OWL Representation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ΗΥ-566ΔΙΑΧΕΙΡΙΣΗ ΓΝΩΣΗΣ ΣΤΟ ΔΙΑΔΙΚΤΥΟΑσκηση 2 Πεδρο, Κατη και Μπεριτ Ελενη

  2. The zoo ontology II • New diagram for OWL. • Differences with the old diagram and new classes. • Some classes and properties.

  3. New diagram for OWL • .dia2.pdf

  4. Differences and new classes (1 of 4) • We have extended the class Cage with three subclasses, so now we can restrict the relation livesIn (Animal-Cage) and hasIn (Cage-Animal). For example, a water animal needs a pool. • We have also added disjoints between Member/Employee, and Vet/Administrator/Cleaner/AnimalWorker. We didn't make the Cage class to be disjoint because a Pool can be Open-Air or Covered, and an Open-Air Cage can have a Covered part. The Animal class isn't disjoint neither because, e.g. the penguin lives in water and in land.

  5. Differences and new classes (2 of 4) • We have added cardinalities to the previous diagram. • For each relation between two classes we have made them both ways, except between Employee-Zoo and Animal-Animal. We did this because it's easy to find in which zoo an employee works, but it takes more time to go the opposite way (zoo -> employee). For the other relation (Animal-Animal) we think that it's enough with one way because the information would be the same in both directions.

  6. Differences and new classes (3 of 4) • New attributes: Cage trees: boolean rocks: boolean • New classes: (sub classes of Cage) Pool poolDepth: float poolWidth: float poolLength: float saltPercentage: float type: lake/sea/artificial

  7. Differences and new classes (4 of 4) Open Air (without roof) wallsHigh: float wallsLength: float wallsWidth: float Covered (with roof) roomLength: float roomWidth: float roomHigh: float

  8. Some classes and properties (1 of 3) <owl:Class rdf:ID="Zoo"> <rdfs:comment> This is the class of zoo. The zoo has to have at least one animal, one emp and one dept. </rdfs:comment> <owl:Restriction> <owl:onProperty rdf:resource="#includes"/> <owl:minCardinality> <xsd:nonNegativeInteger>1</xsd:nonNegativeInteger> </owl:minCardinality> </owl:Restriction> <owl:Restriction> <owl:onProperty rdf:resource="#consistsOf"/> <owl:minCardinality> <xsd:nonNegativeInteger>1</xsd:nonNegativeInteger> </owl:minCardinality> </owl:Restriction> <owl:Restriction> <owl:onProperty rdf:resource="#hasEmployees"/> <owl:minCardinality> <xsd:nonNegativeInteger>1</xsd:nonNegativeInteger> </owl:minCardinality> </owl:Restriction> </owl:Class>

  9. Some classes and properties (2 of 3) <owl:ObjectProperty rdf:ID="includes"> <rdfs:comment> This is the relationship that says that a zoo has animals </rdfs:comment> <owl:domain rdf:resource="#Zoo"/> <owl:range rdf:resource="#Animal"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="sells"> <owl:domain rdf:resource="#Zoo"/> <owl:range rdf:resource="#Ticket"/> <owl:inverseOf rdf:resource="#isSoldBy"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="hasEmployees"> <owl:domain rdf:resource="#Zoo"/> <owl:range rdf:resource="#Employee"/> </owl:ObjectProperty>

  10. Some classes and properties (3 of 3) <owl:Class rdf:ID="Ticket"> <rdfs:comment>The class of all the the Tickets</rdfs:comment> <owl:Restriction> <owl:onProperty rdf:resource="#isSoldBy"/> <owl:cardinality> <xsd:nonNegativeInteger>1</xsd:nonNegativeInteger> </owl:cardinality> </owl:Restriction> </owl:Class> <owl:DataTypeProperty rdf:ID="type"> <rdfs:comment>Property with the type of a Ticket</rdfs:comment> <owl:domain rdf:resource="#Ticket"/> <rdfs:range> <owl:oneOf rdf:parseType="Collection"> <owl:Thing rdf:about="#Student"/> <owl:Thing rdf:about="#Adult"/> <owl:Thing rdf:about="#Reduced"/> <owl:Thing rdf:about="#Member"/> </owl:oneOf> </rdfs:range> </owl:DataTypeProperty>

More Related