Submissions:VesselSpecies Revision as of 10:46, 23 February 2009 by Admin (Talk | contribs) (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warning!

This is an old revision. Go to current revision

This pattern has been certified.

Related submission, with evaluation history, can be found here

Last modified date is: 2009-02-23

General description

Name:	VesselSpecies
Submitted by:	User: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:	what vessel types can catch what species?
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:

Elements

The VesselSpecies Content OP locally defines the following ontology elements:

AquaticSpecies (owl:Class) Aquatic species are conceptual entities that are characterized together with resources and water areas.

Mappable to fi:Species, fi:SpeciesRef, fi:SpeciesFeature, etc.

It has related axioms from FIGIS Schema that are included in the classes linked to the fi:Species class, such as fi:SpeciesRef (holding association with fi:AqResRef, which holds association with fi:WaterAreaRef).

AquaticSpecies page

VesselType (owl:Class) Vessel types are conceptual entities.

Mappable to fi:VesseltypeRef

VesselType 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 page

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

isCaughtByVesselType (owl:ObjectProperty)

isCaughtByVesselType page

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

(relatedCPs): http://www.ontologydesignpatterns.org/cp/owl/fsdas/gearspecies.owl

(imports): http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl

(versionInfo): Created by Alessandro Adamou

(versionInfo): 1.0

Scenarios

Scenarios about VesselSpecies

No scenario is added to this Content OP.

Reviews

Reviews about VesselSpecies

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 3555) takes in account the reviews: VesselSpecies (AldoGangemi about VesselSpecies)

Other info at evaluation tab