'Ontology Design Patterns' - User contributions [en]

Submissions:ActingFor

2011-08-28T20:32:53Z

SayebKhaoula:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation}}
{{Content OP Proposal Template
|SubmittedBy=AldoGangemi,
|Name=ActingFor
|Intent=To represent that some agent is acting in order to forward the action of a social (non-physical) agent.
|CompetencyQuestion=Who is working for which organization? Who is representing the company?
|ContentODPDescription=-
|ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/actingfor.owl
|Consequences=An ontology designer is able to express relations like delegation, working for, etc. It is not possible to express either time indexing (the situation pattern should be specialized to that purpose), nor the role or task, under which the social action is carried out by the physical agent (the descriptionandsituation pattern should be used instead).
|Scenario=Matteo Sanvitale is working as an officer for CEMA s.r.l.
|ReengineeredFrom=http://www.ontologydesignpatterns.org/ont/dul/DUL.owl
}}
{{Element list header}}
{{Has Element Template
|HasElement=actsFor
}}
{{Has Element Template
|HasElement=actsThrough
}}
{{Has Element Template
|HasElement=Agent
}}
{{Has Element Template
|HasElement=SocialAgent
}}
{{Additional information header}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:ActingFor

2011-08-28T20:32:15Z

SayebKhaoula:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation}}
{{Content OP Proposal Template
|SubmittedBy=AldoGangemi,
|Name=ActingFor
|Intent= (non-physical) agent.
|CompetencyQuestion=Who is working for which organization? Who is representing the company?
|ContentODPDescription=-
|ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/actingfor.owl
|Consequences=An ontology designer is able to express relations like delegation, working for, etc. It is not possible to express either time indexing (the situation pattern should be specialized to that purpose), nor the role or task, under which the social action is carried out by the physical agent (the descriptionandsituation pattern should be used instead).
|Scenario=Matteo Sanvitale is working as an officer for CEMA s.r.l.
|ReengineeredFrom=http://www.ontologydesignpatterns.org/ont/dul/DUL.owl
}}
{{Element list header}}
{{Has Element Template
|HasElement=actsFor
}}
{{Has Element Template
|HasElement=actsThrough
}}
{{Has Element Template
|HasElement=Agent
}}
{{Has Element Template
|HasElement=SocialAgent
}}
{{Additional information header}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Classification scheme - adjacency list model - to Taxonomy

2011-08-28T20:30:56Z

SayebKhaoula:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|Name=Classification scheme - adjacency list model - to Taxonomy
|Problem=Re-engineering a classification scheme which follows the adjacency list model to design a taxonomy.

APPLICABILITY

The semantics of the relation between parent and children items are subClassOf.

There is no multi-inheritance nor cyclic relations.
}}
{{Reengineering OP Proposal NOR Template
|Description=A non-ontological resource holds a classification scheme which follows the adjacency list model.
A classification scheme is a rooted tree of concepts, in which each concept groups entities by some particular degree of similarity.
The semantics of the hierarchical relation between parents and children concepts may vary depending of the context.
The adjacency list data model for hierarchical classifications proposes to create an entity which holds a list of items with a linking column associated to their parent items.
|Graphical Representation=AdjacencyList.png
}}
{{Reengineering OP Proposal Ontology Template
|Description=The ontology generated will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are mapped to subClassOf relations.
|Graphical Representation=Ontology.png
}}
{{Reengineering OP Proposal Process Template
|Description=1. Identify the classification scheme items which do not have a parent key value, i.e. classification scheme items without parents.

2. For each one of the above identified classification scheme items cei:

2.1. Create the corresponding ontology class, Ci class.

2.2. Identify the classification scheme items, cej , which are children of cei, by using the parent key values.

2.3. For each one of the above identified classification scheme items cej :

2.3.1. Create the corresponding ontology class, Cj class.

2.3.2. Set up the subClassOf relation between Cj and Ci.

2.3.3. Repeat from step 2.2 for cej as a new cei.

3. If there are more than one classification scheme items without parent cei

3.1. Create an ad-hoc class as the root class of the ontology.

3.2. Set up the subClassOf relation between Ci class and the root class.
|Graphical Representation=Wfcsalsocheck.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=Suppose that someone wants to build an ontology based on the water areas classification published by FAO. This classification scheme follows the adjacency list data model.
}}
{{Reengineering OP Proposal NOR Example Template
|Description=The FAO classification for water areas groups them according to some different criteria as environment, statistics, and jurisdiction, among others.
|Graphical Representation=AdjacencyListWaterAreas.png
|Web Reference=http://www.fao.org/figis/servlet/RefServlet
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The ontology generated will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are mapped to subClassOf relations.
|Graphical Representation=WaterAreaOntology.png
|Web Reference=http://www.fao.org/aims/neon.jsp
}}
{{Reengineering OP Proposal Process Example Template
|Description=1. Create the Water area class.

2. Create the Environmental area class, and set up the subClassOf relation between the Environmental area class and the Water area class.

2.1. Create the Inland/marine class, and set up the subClassOf relation between the Inland/marine class and the Environmental area class.

2.2. Create the Ocean class, and set up the subClassOf relation between the Ocean class and the Environmental area class.

2.3. Create the North/South/Equatorial class, and set up the subClassOf relation between the North a South a Equatorial class and the Environmental area class.

3. Create the Fishing Statistical area class, and set up the subClassOf relation
between the Fishing Statistical area class and the Water area class.

3.1. Create the FAO statistical area class, and set up the subClassOf relation between the FAO statistical area class and the Fishing Statistical area class.

3.2. Create the Areal grid system class, and set up the subClassOf relation between the Areal grid system class and the Fishing Statistical area class.

4. Create the Jurisdiction area class, and set up the subClassOf relation between the Jurisdiction area class and the Water area class.
|Graphical Representation=wfcsalsoexamplecheck.png
}}
{{Reengineering OP Proposal Additional Information Template
|SubmittedBy=BorisVillazón-Terrazas,
|Author=Boris Villazón Terrazas,
|Also known as=Classification scheme to Taxonomy (adjacency list model)
|Related to=Use the Architectural Pattern: TX-AP-01
}}
{{Additional information header}}
[[Category:Review assigned]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2009
}}

Submissions:Classification scheme - adjacency list model - to Taxonomy

2011-08-28T20:30:32Z

SayebKhaoula:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|Name=Taxonomy
|Problem=Re-engineering a classification scheme which follows the adjacency list model to design a taxonomy.

APPLICABILITY

The semantics of the relation between parent and children items are subClassOf.

There is no multi-inheritance nor cyclic relations.
}}
{{Reengineering OP Proposal NOR Template
|Description=A non-ontological resource holds a classification scheme which follows the adjacency list model.
A classification scheme is a rooted tree of concepts, in which each concept groups entities by some particular degree of similarity.
The semantics of the hierarchical relation between parents and children concepts may vary depending of the context.
The adjacency list data model for hierarchical classifications proposes to create an entity which holds a list of items with a linking column associated to their parent items.
|Graphical Representation=AdjacencyList.png
}}
{{Reengineering OP Proposal Ontology Template
|Description=The ontology generated will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are mapped to subClassOf relations.
|Graphical Representation=Ontology.png
}}
{{Reengineering OP Proposal Process Template
|Description=1. Identify the classification scheme items which do not have a parent key value, i.e. classification scheme items without parents.

2. For each one of the above identified classification scheme items cei:

2.1. Create the corresponding ontology class, Ci class.

2.2. Identify the classification scheme items, cej , which are children of cei, by using the parent key values.

2.3. For each one of the above identified classification scheme items cej :

2.3.1. Create the corresponding ontology class, Cj class.

2.3.2. Set up the subClassOf relation between Cj and Ci.

2.3.3. Repeat from step 2.2 for cej as a new cei.

3. If there are more than one classification scheme items without parent cei

3.1. Create an ad-hoc class as the root class of the ontology.

3.2. Set up the subClassOf relation between Ci class and the root class.
|Graphical Representation=Wfcsalsocheck.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=Suppose that someone wants to build an ontology based on the water areas classification published by FAO. This classification scheme follows the adjacency list data model.
}}
{{Reengineering OP Proposal NOR Example Template
|Description=The FAO classification for water areas groups them according to some different criteria as environment, statistics, and jurisdiction, among others.
|Graphical Representation=AdjacencyListWaterAreas.png
|Web Reference=http://www.fao.org/figis/servlet/RefServlet
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The ontology generated will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are mapped to subClassOf relations.
|Graphical Representation=WaterAreaOntology.png
|Web Reference=http://www.fao.org/aims/neon.jsp
}}
{{Reengineering OP Proposal Process Example Template
|Description=1. Create the Water area class.

2. Create the Environmental area class, and set up the subClassOf relation between the Environmental area class and the Water area class.

2.1. Create the Inland/marine class, and set up the subClassOf relation between the Inland/marine class and the Environmental area class.

2.2. Create the Ocean class, and set up the subClassOf relation between the Ocean class and the Environmental area class.

2.3. Create the North/South/Equatorial class, and set up the subClassOf relation between the North a South a Equatorial class and the Environmental area class.

3. Create the Fishing Statistical area class, and set up the subClassOf relation
between the Fishing Statistical area class and the Water area class.

3.1. Create the FAO statistical area class, and set up the subClassOf relation between the FAO statistical area class and the Fishing Statistical area class.

3.2. Create the Areal grid system class, and set up the subClassOf relation between the Areal grid system class and the Fishing Statistical area class.

4. Create the Jurisdiction area class, and set up the subClassOf relation between the Jurisdiction area class and the Water area class.
|Graphical Representation=wfcsalsoexamplecheck.png
}}
{{Reengineering OP Proposal Additional Information Template
|SubmittedBy=BorisVillazón-Terrazas,
|Author=Boris Villazón Terrazas,
|Also known as=Classification scheme to Taxonomy (adjacency list model)
|Related to=Use the Architectural Pattern: TX-AP-01
}}
{{Additional information header}}
[[Category:Review assigned]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2009
}}

Submissions:Classification scheme - adjacency list model - to Taxonomy

2011-08-28T20:29:28Z

SayebKhaoula:

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|Name=Classification scheme - adjacency list model - to Taxonomy
|Problem= scheme which follows the adjacency list model to design a taxonomy.

APPLICABILITY

The semantics of the relation between parent and children items are subClassOf.

There is no multi-inheritance nor cyclic relations.
}}
{{Reengineering OP Proposal NOR Template
|Description=A non-ontological resource holds a classification scheme which follows the adjacency list model.
A classification scheme is a rooted tree of concepts, in which each concept groups entities by some particular degree of similarity.
The semantics of the hierarchical relation between parents and children concepts may vary depending of the context.
The adjacency list data model for hierarchical classifications proposes to create an entity which holds a list of items with a linking column associated to their parent items.
|Graphical Representation=AdjacencyList.png
}}
{{Reengineering OP Proposal Ontology Template
|Description=The ontology generated will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are mapped to subClassOf relations.
|Graphical Representation=Ontology.png
}}
{{Reengineering OP Proposal Process Template
|Description=1. Identify the classification scheme items which do not have a parent key value, i.e. classification scheme items without parents.

2. For each one of the above identified classification scheme items cei:

2.1. Create the corresponding ontology class, Ci class.

2.2. Identify the classification scheme items, cej , which are children of cei, by using the parent key values.

2.3. For each one of the above identified classification scheme items cej :

2.3.1. Create the corresponding ontology class, Cj class.

2.3.2. Set up the subClassOf relation between Cj and Ci.

2.3.3. Repeat from step 2.2 for cej as a new cei.

3. If there are more than one classification scheme items without parent cei

3.1. Create an ad-hoc class as the root class of the ontology.

3.2. Set up the subClassOf relation between Ci class and the root class.
|Graphical Representation=Wfcsalsocheck.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=Suppose that someone wants to build an ontology based on the water areas classification published by FAO. This classification scheme follows the adjacency list data model.
}}
{{Reengineering OP Proposal NOR Example Template
|Description=The FAO classification for water areas groups them according to some different criteria as environment, statistics, and jurisdiction, among others.
|Graphical Representation=AdjacencyListWaterAreas.png
|Web Reference=http://www.fao.org/figis/servlet/RefServlet
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The ontology generated will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are mapped to subClassOf relations.
|Graphical Representation=WaterAreaOntology.png
|Web Reference=http://www.fao.org/aims/neon.jsp
}}
{{Reengineering OP Proposal Process Example Template
|Description=1. Create the Water area class.

2. Create the Environmental area class, and set up the subClassOf relation between the Environmental area class and the Water area class.

2.1. Create the Inland/marine class, and set up the subClassOf relation between the Inland/marine class and the Environmental area class.

2.2. Create the Ocean class, and set up the subClassOf relation between the Ocean class and the Environmental area class.

2.3. Create the North/South/Equatorial class, and set up the subClassOf relation between the North a South a Equatorial class and the Environmental area class.

3. Create the Fishing Statistical area class, and set up the subClassOf relation
between the Fishing Statistical area class and the Water area class.

3.1. Create the FAO statistical area class, and set up the subClassOf relation between the FAO statistical area class and the Fishing Statistical area class.

3.2. Create the Areal grid system class, and set up the subClassOf relation between the Areal grid system class and the Fishing Statistical area class.

4. Create the Jurisdiction area class, and set up the subClassOf relation between the Jurisdiction area class and the Water area class.
|Graphical Representation=wfcsalsoexamplecheck.png
}}
{{Reengineering OP Proposal Additional Information Template
|SubmittedBy=BorisVillazón-Terrazas,
|Author=Boris Villazón Terrazas,
|Also known as=Classification scheme to Taxonomy (adjacency list model)
|Related to=Use the Architectural Pattern: TX-AP-01
}}
{{Additional information header}}
[[Category:Review assigned]]
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2009
}}

Submissions:Classification scheme - adjacency list model - to Taxonomy

2011-07-08T16:30:51Z

SayebKhaoula:

Community talk:Patronkh

2011-07-08T13:40:59Z

SayebKhaoula:

Hi,
Does this space enable the collaborative creation of patterns.
Can I invite other members to modify my pattern.
Thanks

Community talk:Patronkh

2011-07-08T13:38:07Z

SayebKhaoula: New page: Hi, Can this space enable the collaborative creation of patterns. Can I invite other members to modify my pattern. Thanks

Hi,
Can this space enable the collaborative creation of patterns.
Can I invite other members to modify my pattern.
Thanks

Community:References/A Media Value Chain Ontology for MPEG-21 2

2011-07-08T13:35:45Z

SayebKhaoula: New page: {{Reference |Subject=Community:Patronkh |Label=A Media Value Chain Ontology for MPEG-21 |Description=A Media Value Chain Ontology for MPEG-21 |Type=Project Home Page |TypeOther=Paper |URL=...

{{Reference
|Subject=Community:Patronkh
|Label=A Media Value Chain Ontology for MPEG-21
|Description=A Media Value Chain Ontology for MPEG-21
|Type=Project Home Page
|TypeOther=Paper
|URL=http://portal.acm.org/citation.cfm?id=1685140.1685158&coll=portal&dl=ACM
}}

Community:Patronkh

2011-07-08T13:30:02Z

SayebKhaoula: New page: {{TitleDescription Template |Title=patronkh |Description=mon patron de test }} {{Graphical representation}} {{Modeling Issue Template}} {{Additional information header}} {{My references}}...

{{TitleDescription Template
|Title=patronkh
|Description=mon patron de test
}}
{{Graphical representation}}
{{Modeling Issue Template}}
{{Additional information header}}

{{My references}}
{{Modeling Issue toolbar}}

Submissions:AOS AGROVOC Concept Server fundation ontology model

2011-05-30T10:52:15Z

SayebKhaoula:

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=http://ontologydesignpatterns.org/wiki/Image:Aos.jpg
}}
{{Content OP Proposal Template
|SubmittedBy=MargheritaSini
|Name=AOS AGROVOC Concept Server foundation ontology model
|ContentODPAlsoKnownAs=AGROVOC Concept Server OWL Model, ASC, AOS
|Intent=Act as a basic model for Agricultural Related Ontologies, in particular for the AGROVOC Concept Server. The model clearly identify concepts (domain concepts) from terms (which are represented as instances). Both concepts and terms have specific relationships connecting them.
|Domain=Agriculture,
|CompetencyQuestion=What is the structure i should use if i want to distinguish between domain concepts and their terminology?
|ContentODPDescription=-
|ReusableOWLBuildingBlock=http://www.fao.org/aims/aos/aos.owl
|Consequences=This model can be compared to the LIR model. A mapping between the two model exists. Therefore, using the AOS will make your ontology compatible with the LIR and therefore the NeOn Toolkit.
|ReengineeredFrom=AGROVOC Thesaurus
|RelatedCP=HasPest,
}}
{{Element list header}}
{{Has Element Template
|HasElement=c_geographic_concept_above_country_level
}}
{{Has Element Template
|HasElement=c_geographic_concept
}}
{{Has Element Template
|HasElement=c_geographic_concept_below_country_level
}}
{{Has Element Template
|HasElement=c_taxonomic_term_animals
}}
{{Has Element Template
|HasElement=c_taxonomic_term
}}
{{Has Element Template
|HasElement=c_geographic_concept_country_level
}}
{{Has Element Template
|HasElement=c_domain_concept
}}
{{Has Element Template
|HasElement=c_category
}}
{{Has Element Template
|HasElement=c_scientific_term
}}
{{Has Element Template
|HasElement=c_noun
}}
{{Has Element Template
|HasElement=c_taxonomic_term_viruses
}}
{{Has Element Template
|HasElement=c_definition
}}
{{Has Element Template
|HasElement=c_entity_annotation
}}
{{Has Element Template
|HasElement=c_taxonomic_term_bacteria
}}
{{Has Element Template
|HasElement=c_lexicalization
}}
{{Has Element Template
|HasElement=c_image
}}
{{Has Element Template
|HasElement=c_taxonomic_term_fungi
}}
{{Has Element Template
|HasElement=c_chemical_term
}}
{{Has Element Template
|HasElement=c_taxonomic_term_plant
}}
{{Has Element Template
|HasElement=c_chemical_concept
}}
{{Has Element Template
|HasElement=c_classification_scheme
}}
{{Has Element Template
|HasElement=isUsedToMake
}}
{{Has Element Template
|HasElement=essiveRelationship
}}
{{Has Element Template
|HasElement=isMadeFrom
}}
{{Has Element Template
|HasElement=domainSpecificRelationship
}}
{{Has Element Template
|HasElement=objectProperty
}}
{{Has Element Template
|HasElement=hasRelatedType
}}
{{Has Element Template
|HasElement=isRelatedTypeOf
}}
{{Has Element Template
|HasElement=hasRelatedConcept
}}
{{Has Element Template
|HasElement=hasTransliteration
}}
{{Has Element Template
|HasElement=hasRelatedTerm
}}
{{Has Element Template
|HasElement=isAGrowthEnvironmentFor
}}
{{Has Element Template
|HasElement=growsIn
}}
{{Has Element Template
|HasElement=instrumentalRelationship
}}
{{Has Element Template
|HasElement=isAchievedByMeansOf
}}
{{Has Element Template
|HasElement=hasGoalOrProcess
}}
{{Has Element Template
|HasElement=isMeansFor
}}
{{Has Element Template
|HasElement=isPerformedByMeansOf
}}
{{Has Element Template
|HasElement=isReferencedInAnnotationOf
}}
{{Has Element Template
|HasElement=annotationRefersTo
}}
{{Has Element Template
|HasElement=isMemberOf
}}
{{Has Element Template
|HasElement=partitiveRelationship
}}
{{Has Element Template
|HasElement=hasMember
}}
{{Has Element Template
|HasElement=hasImage
}}
{{Has Element Template
|HasElement=isImageOf
}}
{{Has Element Template
|HasElement=isControlledBy
}}
{{Has Element Template
|HasElement=causativeRelationship
}}
{{Has Element Template
|HasElement=controls
}}
{{Has Element Template
|HasElement=isProcessFor
}}
{{Has Element Template
|HasElement=usesProcess
}}
{{Has Element Template
|HasElement=hasAbbreviation
}}
{{Has Element Template
|HasElement=isAbbreviationOf
}}
{{Has Element Template
|HasElement=precedes
}}
{{Has Element Template
|HasElement=temporalRelationship
}}
{{Has Element Template
|HasElement=follows
}}
{{Has Element Template
|HasElement=developsInto
}}
{{Has Element Template
|HasElement=developsFrom
}}
{{Has Element Template
|HasElement=performs
}}
{{Has Element Template
|HasElement=isPerformedBy
}}
{{Has Element Template
|HasElement=use
}}
{{Has Element Template
|HasElement=usedForPlus
}}
{{Has Element Template
|HasElement=thesaurusRelationship
}}
{{Has Element Template
|HasElement=prevents
}}
{{Has Element Template
|HasElement=isPreventedBy
}}
{{Has Element Template
|HasElement=hasBroaderSynonym
}}
{{Has Element Template
|HasElement=hasNarrowerSynonym
}}
{{Has Element Template
|HasElement=hasSynonym
}}
{{Has Element Template
|HasElement=hasSymptom
}}
{{Has Element Template
|HasElement=indicates
}}
{{Has Element Template
|HasElement=isUseOf
}}
{{Has Element Template
|HasElement=isUsedAs
}}
{{Has Element Template
|HasElement=afflicts
}}
{{Has Element Template
|HasElement=isAfflictedBy
}}
{{Has Element Template
|HasElement=affects
}}
{{Has Element Template
|HasElement=belongsToScheme
}}
{{Has Element Template
|HasElement=hasCategory
}}
{{Has Element Template
|HasElement=hasPest
}}
{{Has Element Template
|HasElement=isPestOf
}}
{{Has Element Template
|HasElement=isOutputFrom
}}
{{Has Element Template
|HasElement=isInputFor
}}
{{Has Element Template
|HasElement=cropWildRelativeRelationship
}}
{{Has Element Template
|HasElement=hasAuthor
}}
{{Has Element Template
|HasElement=isAuthorOf
}}
{{Has Element Template
|HasElement=isScientificNameOf
}}
{{Has Element Template
|HasElement=hasScientificName
}}
{{Has Element Template
|HasElement=isCausedBy
}}
{{Has Element Template
|HasElement=causes
}}
{{Has Element Template
|HasElement=isBeneficialFor
}}
{{Has Element Template
|HasElement=benefitsFrom
}}
{{Has Element Template
|HasElement=hasTheme
}}
{{Has Element Template
|HasElement=isThemeOf
}}
{{Has Element Template
|HasElement=isSourceOf
}}
{{Has Element Template
|HasElement=isDerivedFrom
}}
{{Has Element Template
|HasElement=hasAcronym
}}
{{Has Element Template
|HasElement=isAcronymOf
}}
{{Has Element Template
|HasElement=isPropertyOf
}}
{{Has Element Template
|HasElement=hasProperty
}}
{{Has Element Template
|HasElement=hasMappedDomainConcept
}}
{{Has Element Template
|HasElement=belongsToCategory
}}
{{Has Element Template
|HasElement=isProducedBy
}}
{{Has Element Template
|HasElement=produces
}}
{{Has Element Template
|HasElement=isAffectedBy
}}
{{Has Element Template
|HasElement=portion
}}
{{Has Element Template
|HasElement=portionOf
}}
{{Has Element Template
|HasElement=hasDefinition
}}
{{Has Element Template
|HasElement=isDefinitionOf
}}
{{Has Element Template
|HasElement=hasObjectOfActivity
}}
{{Has Element Template
|HasElement=isObjectOfActivity
}}
{{Has Element Template
|HasElement=isActedUponBy
}}
{{Has Element Template
|HasElement=actsUpon
}}
{{Has Element Template
|HasElement=isSubprocessOf
}}
{{Has Element Template
|HasElement=includesSubprocess
}}
{{Has Element Template
|HasElement=hasTermVariant
}}
{{Has Element Template
|HasElement=datatypeProperty
}}
{{Has Element Template
|HasElement=hasChemicalFormula
}}
{{Has Element Template
|HasElement=hasScopeNote
}}
{{Has Element Template
|HasElement=hasStemmedForm
}}
{{Has Element Template
|HasElement=hasPlural
}}
{{Has Element Template
|HasElement=hasImageDescription
}}
{{Has Element Template
|HasElement=hasSpellingVariant
}}
{{Has Element Template
|HasElement=hasImageName
}}
{{Has Element Template
|HasElement=hasChangeHistory
}}
{{Has Element Template
|HasElement=hasCode
}}
{{Has Element Template
|HasElement=hasSingular
}}
{{Has Element Template
|HasElement=hasComponent
}}
{{Has Element Template
|HasElement=isComponentOf
}}
{{Has Element Template
|HasElement=hasPart
}}
{{Has Element Template
|HasElement=spatiallyIncludes
}}
{{Has Element Template
|HasElement=isSpatiallyIncludedIn
}}
{{Has Element Template
|HasElement=compose
}}
{{Has Element Template
|HasElement=isComposedOf
}}
{{Has Element Template
|HasElement=isPartOf
}}
{{Has Element Template
|HasElement=hasPortion
}}
{{Has Element Template
|HasElement=isPortionOf
}}
{{Has Element Template
|HasElement=isSubCategoryOf
}}
{{Has Element Template
|HasElement=hasSubCategory
}}
{{Has Element Template
|HasElement=isFaoPaSubCategoryOf
}}
{{Has Element Template
|HasElement=hasFaoPaSubCategory
}}
{{Has Element Template
|HasElement=hasAscSubCategory
}}
{{Has Element Template
|HasElement=isAscSubCategoryOf
}}
{{Has Element Template
|HasElement=hasTranslation
}}
{{Has Element Template
|HasElement=takenFromSource
}}
{{Has Element Template
|HasElement=hasFishery3AlphaCode
}}
{{Has Element Template
|HasElement=hasImageSource
}}
{{Has Element Template
|HasElement=hasTaxonomicCode
}}
{{Has Element Template
|HasElement=hasCodeFaoPa
}}
{{Has Element Template
|HasElement=hasDateCreated
}}
{{Has Element Template
|HasElement=isMainLabel
}}
{{Has Element Template
|HasElement=hasSourceLink
}}
{{Has Element Template
|HasElement=hasImageLink
}}
{{Has Element Template
|HasElement=isLexicalizationOf
}}
{{Has Element Template
|HasElement=hasLexicalization
}}
{{Has Element Template
|HasElement=hasCodeAgrovoc
}}
{{Has Element Template
|HasElement=hasStatus
}}
{{Has Element Template
|HasElement=hasCodeFaoterm
}}
{{Has Element Template
|HasElement=hasDateLastUpdated
}}
{{Has Element Template
|HasElement=hasCodeAsfa
}}
{{Has Element Template
|HasElement=hasCodeAsc
}}
{{Additional information header}}
Last revised by KCEW: set the correct namespaces for xmlns, xml:base, and owl:Ontology.
Last revised by KCEW: removed all remaining instances.

(type): http://www.w3.org/2002/07/owl#Ontology

(versionInfo): 20080508

(comment): Last revised by KCEW: set the correct namespaces for xmlns, xml:base, and owl:Ontology.

(comment): Last revised by KCEW: removed all remaining instances.
{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}