Submissions:ResourceExploitationObservation

From Odp

(Difference between revisions)
Jump to: navigation, search
Current revision (13:45, 8 March 2010) (view source)
 
(3 intermediate revisions not shown.)
Line 1: Line 1:
{{Content_OP_Proposal_toolbar}}
{{Content_OP_Proposal_toolbar}}
-
{{Include Image
+
{{Graphical representation header}}
 +
{{Graphical representation
|ImageName=Resourceexploitation.jpg
|ImageName=Resourceexploitation.jpg
}}
}}
{{Content OP Proposal Template
{{Content OP Proposal Template
-
|SubmittedBy=AldoGangemi
+
|SubmittedBy=AldoGangemi, EvaBlomqvist
|Name=ResourceExploitationObservation
|Name=ResourceExploitationObservation
|Intent=The intent of the pattern is to be able to represent observations of aquatic resources, where the observations have been made a certain year and has certain other parameters.
|Intent=The intent of the pattern is to be able to represent observations of aquatic resources, where the observations have been made a certain year and has certain other parameters.
|Domain=Fishery
|Domain=Fishery
|CompetencyQuestion=What resource is observed? For what year and at what exploitation rate and exploitation state?
|CompetencyQuestion=What resource is observed? For what year and at what exploitation rate and exploitation state?
 +
|ContentODPDescription=...
|ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceexploitationobservation.owl,
|ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceexploitationobservation.owl,
|Consequences=The patterns states that for each instance of the resource observation all parameters exist, this does not however mean that they are necessarily present in the knowledge base. Any dependencies between parameters have not been taken intor account, there are no formal restrictions on the combination possible. The parameters are intended to have a fixed set of values (to be defined as nominals) but this is not explicit in the pattern.
|Consequences=The patterns states that for each instance of the resource observation all parameters exist, this does not however mean that they are necessarily present in the knowledge base. Any dependencies between parameters have not been taken intor account, there are no formal restrictions on the combination possible. The parameters are intended to have a fixed set of values (to be defined as nominals) but this is not explicit in the pattern.
Line 45: Line 47:
|HasElement=isExploitationRateOf
|HasElement=isExploitationRateOf
}}
}}
 +
{{Additional information header}}
(type): http://www.w3.org/2002/07/owl#Ontology
(type): http://www.w3.org/2002/07/owl#Ontology
Line 52: Line 55:
{{Scenarios about me}}
{{Scenarios about me}}
{{Reviews about me}}
{{Reviews about me}}
 +
{{Modeling issues about me}}
 +
{{My references}}

Current revision


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 9118

Graphical representation

Diagram

Image:Resourceexploitation.jpg

General description

Name: ResourceExploitationObservation
Submitted by: AldoGangemi, EvaBlomqvist
Also Known As:
Intent: The intent of the pattern is to be able to represent observations of aquatic resources, where the observations have been made a certain year and has certain other parameters.
Domains:

Fishery

Competency Questions:
  • What resource is observed? For what year and at what exploitation rate and exploitation state?
Solution description: ...
Reusable OWL Building Block: http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceexploitationobservation.owl (707)
Consequences: The patterns states that for each instance of the resource observation all parameters exist, this does not however mean that they are necessarily present in the knowledge base. Any dependencies between parameters have not been taken intor account, there are no formal restrictions on the combination possible. The parameters are intended to have a fixed set of values (to be defined as nominals) but this is not explicit in the pattern.
Scenarios: Give me the resource observations for the year 2004 Give me the resource observations where the exploitation rate is 'Moderate fishing mortality' Give me the resource observations where the state is 'fully exploited'
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:


Elements

The ResourceExploitationObservation Content OP locally defines the following ontology elements:

Class ResourceExploitationObservation (owl:Class) An observation of a resource characterised by different parameters.
ResourceExploitationObservation page
DatatypeProperty hasReferenceYear (owl:DatatypeProperty)
hasReferenceYear page
ObjectProperty hasResource (owl:ObjectProperty)
hasResource page
ObjectProperty hasExploitationRate (owl:ObjectProperty)
hasExploitationRate page
Class ExploitationRate (owl:Class)
ExploitationRate page
Class ExploitationState (owl:Class)
ExploitationState page
ObjectProperty hasExploitationState (owl:ObjectProperty)
hasExploitationState page
ObjectProperty isExploitationStateOf (owl:ObjectProperty)
isExploitationStateOf page
ObjectProperty isResourceOf (owl:ObjectProperty)
isResourceOf page
ObjectProperty isExploitationRateOf (owl:ObjectProperty)
isExploitationRateOf page

Additional information

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

(imports): http://www.ontologydesignpatterns.org/cp/owl/observation.owl

(hasUnitTest): SELECT ?x WHERE {?x a :AquaticResourceObservation.  ?x :hasReferenceYear

Scenarios

Scenarios about ResourceExploitationObservation

No scenario is added to this Content OP.

Reviews

Reviews about ResourceExploitationObservation

There is no review about this proposal. This revision (revision ID 9118) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about ResourceExploitationObservation

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers