m (Text replace - 'SubmittedBy=User:' to 'SubmittedBy=') |
EnricoDaga (Talk | contribs) m |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
| − | {{ | + | {{Graphical representation header}} |
| − | |ImageName= | + | {{Graphical representation |
| + | |ImageName=Vesselspecies2.jpg | ||
}} | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
| Line 7: | Line 8: | ||
|Name=VesselSpecies | |Name=VesselSpecies | ||
|Intent=to provide a direct relation between aquatic species and vessels that are able to catch them, regardless of the fishing gear used. | |Intent=to provide a direct relation between aquatic species and vessels that are able to catch them, regardless of the fishing gear used. | ||
| − | |CompetencyQuestion=what vessel types can catch what species? | + | |Domain=Fishery |
| + | |CompetencyQuestion=what vessel types can catch what species? (provided that species are caught by geartypes are used by vessel types) | ||
| + | |ContentODPDescription=--- | ||
|ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/fsdas/vesselspecies.owl | |ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/fsdas/vesselspecies.owl | ||
|Consequences=This pattern should be used in scenarios where a VesselType can be deemed suitable for catching some AquaticSpecies for reasons other than mounting some fishing gear of a suitable GearType. It is strictly related to the gearspecies pattern, in that it uses the catchesSpecies and isCaught property pair to define this behaviour. For the sake of reuse, no domain is declared for catchesSpecies, appropriate restrictions having beed applied instead. | |Consequences=This pattern should be used in scenarios where a VesselType can be deemed suitable for catching some AquaticSpecies for reasons other than mounting some fishing gear of a suitable GearType. It is strictly related to the gearspecies pattern, in that it uses the catchesSpecies and isCaught property pair to define this behaviour. For the sake of reuse, no domain is declared for catchesSpecies, appropriate restrictions having beed applied instead. | ||
|Scenario=give me the species caught using 'gillneters' | |Scenario=give me the species caught using 'gillneters' | ||
| + | |HasComponent=GearSpecies,GearVessel | ||
| + | |RelatedCP=GearSpecies | ||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
{{Has Element Template | {{Has Element Template | ||
| − | |HasElement= | + | |HasElement=isCaughtBy |
| − | + | ||
| − | + | ||
| − | + | ||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
|HasElement=catchesSpecies | |HasElement=catchesSpecies | ||
| − | |||
| − | |||
| − | |||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
|HasElement=isCaughtByVesselType | |HasElement=isCaughtByVesselType | ||
}} | }} | ||
| + | {{Takes in account review | ||
| + | |TakesInAccountReview=AldoGangemi about VesselSpecies | ||
| + | }} | ||
| + | {{Additional information header}} | ||
| + | This pattern composes gearvessel.owl and gearspecies.owl. | ||
| + | This must be inferred compositionally, and requires either more sophisticated logical pattern, like 'property chain', available in OWL2 (but not in OWL1), or a complex reasoning pattern, like 'DL classifier+SPARQL', or 'DL classifier+SWRL rule firing'. | ||
| + | |||
(type): http://www.w3.org/2002/07/owl#Ontology | (type): http://www.w3.org/2002/07/owl#Ontology | ||
| + | |||
| + | (versionInfo): Created by Alessandro Adamou | ||
| + | |||
| + | (comment): This pattern composes gearvessel.owl and gearspecies.owl. | ||
| + | This must be inferred compositionally, and requires either more sophisticated logical pattern, like 'property chain', available in OWL2 (but not in OWL1), or a complex reasoning pattern, like 'DL classifier+SPARQL', or 'DL classifier+SWRL rule firing'. | ||
(relatedCPs): http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearspecies.owl | (relatedCPs): http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearspecies.owl | ||
| + | |||
| + | (hasComponent): <http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearspecies.owl> | ||
(imports): http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl | (imports): http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl | ||
| − | ( | + | (imports): http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearspecies.owl |
| + | |||
| + | (hasComponent): <http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearvessel.owl> | ||
| + | |||
| + | (imports): http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearvessel.owl | ||
| − | (versionInfo): 1. | + | (versionInfo): 1.1 |
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
| + | {{Modeling issues about me}} | ||
| + | {{My references}} | ||
|
Last modified date is: 2010-03-08 |
Diagram
| Name: | VesselSpecies |
|---|---|
| Submitted by: | AlessandroAdamou |
| Also Known As: | |
| Intent: | to provide a direct relation between aquatic species and vessels that are able to catch them, regardless of the fishing gear used. |
| Domains: | |
| Competency Questions: | |
| Solution description: | --- |
| Reusable OWL Building Block: | 1 (455) |
| Consequences: | This pattern should be used in scenarios where a VesselType can be deemed suitable for catching some AquaticSpecies for reasons other than mounting some fishing gear of a suitable GearType. It is strictly related to the gearspecies pattern, in that it uses the catchesSpecies and isCaught property pair to define this behaviour. For the sake of reuse, no domain is declared for catchesSpecies, appropriate restrictions having beed applied instead. |
| Scenarios: | give me the species caught using 'gillneters' |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The VesselSpecies Content OP locally defines the following ontology elements:
isCaughtBy (owl:ObjectProperty) Actually a composed property: this needs either a property chain, a SPARQL query, or a SWRL rule to gather a value. E.g. in SPARQL:
CONSTRUCT {?x :catchesSpecies ?y . ?y isCaughtBy ?x}
WHERE {
?x gearvessel:usesGearType ?z .
?z gearspecies:catchesSpecies ?y
}
isCaughtBy page catchesSpecies (owl:ObjectProperty) Actually a composed property: this needs either a property chain, a SPARQL query, or a SWRL rule to gather a value. E.g. in SPARQL:
CONSTRUCT {?x :catchesSpecies ?y . ?y isCaughtBy ?x}
WHERE {
?x gearvessel:usesGearType ?z .
?z gearspecies:catchesSpecies ?y
}
catchesSpecies pageThis pattern composes gearvessel.owl and gearspecies.owl. This must be inferred compositionally, and requires either more sophisticated logical pattern, like 'property chain', available in OWL2 (but not in OWL1), or a complex reasoning pattern, like 'DL classifier+SPARQL', or 'DL classifier+SWRL rule firing'.
(type): http://www.w3.org/2002/07/owl#Ontology
(versionInfo): Created by Alessandro Adamou
(comment): This pattern composes gearvessel.owl and gearspecies.owl. This must be inferred compositionally, and requires either more sophisticated logical pattern, like 'property chain', available in OWL2 (but not in OWL1), or a complex reasoning pattern, like 'DL classifier+SPARQL', or 'DL classifier+SWRL rule firing'.
(relatedCPs): http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearspecies.owl
(hasComponent): <http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearspecies.owl>
(imports): http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl
(imports): http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearspecies.owl
(hasComponent): <http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearvessel.owl>
(imports): http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearvessel.owl
(versionInfo): 1.1
No scenario is added to this Content OP.
This revision (revision ID 9141) takes in account the reviews: VesselSpecies (AldoGangemi about VesselSpecies)
Other info at evaluation tab
'Ontology Design Patterns'
