Resourceabundanceobservation Pattern¶

Source: ODP portal · Published by: ontologydesignpatterns.org · Category: conceptual · Domain: biology

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.

What it answers¶

What resource is observed? For what year and at what abundance level?

The pattern¶

The graph is the axioms the pattern asserts; nothing here is inferred. Drag to rearrange, scroll to zoom, and use the graph's own search box to find a term inside it.

Opens at level of detail 3: classes, individuals, properties and restrictions, without the literals. Raise it with the LOD control in the graph's own toolbar to see annotation values and anything a reasoner adds.

Download the pattern

Should you use this one?¶


Size	2 classes, 5 properties, 40 axioms
Brings in	3 imported ontologies, so adopting it adopts those too
Reasoning	HermiT finds this pattern consistent, with no unsatisfiable class, and its worked example consistent with the pattern.

A situation it was written for. Give me the resource observations for the year 2004 Give me the resource observations where the abundance level is 'Low abundance'

Check it yourself: the published pattern · an archived copy · the ontology itself.

If a link does not open

ontologydesignpatterns.org, which publishes most of this library, does not currently answer over HTTPS, and its wiki redirects submission pages to its front page. The archived copy is there for exactly that reason. The ontology files themselves are still served over plain HTTP.

Terms it declares¶

The 24 classes and properties this pattern models, as the recommender scores them. Annotation properties and built-ins are excluded, because an annotation property is not modelling.

http://www.ontologydesignpatterns.org/cp/owl/fsdas/aquaticresources.owl#AquaticResource
http://www.ontologydesignpatterns.org/cp/owl/fsdas/aquaticresources.owl#AquaticSpecies
http://www.ontologydesignpatterns.org/cp/owl/fsdas/aquaticresources.owl#WaterArea
http://www.ontologydesignpatterns.org/cp/owl/fsdas/aquaticresources.owl#canOccurIn
http://www.ontologydesignpatterns.org/cp/owl/fsdas/aquaticresources.owl#hasSpecies
http://www.ontologydesignpatterns.org/cp/owl/fsdas/aquaticresources.owl#isAreaOfOccurrenceOf
http://www.ontologydesignpatterns.org/cp/owl/fsdas/aquaticresources.owl#isSpeciesPresentIn
http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceabundanceobservation.owl#AbundanceLevel
http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceabundanceobservation.owl#ResourceAbundanceObservation
http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceabundanceobservation.owl#hasAbundanceLevel
http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceabundanceobservation.owl#hasReferenceYear
http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceabundanceobservation.owl#hasResource
http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceabundanceobservation.owl#isAbundanceLevelOf
http://www.ontologydesignpatterns.org/cp/owl/fsdas/resourceabundanceobservation.owl#isResourceOf
http://www.ontologydesignpatterns.org/cp/owl/observation.owl#Observation
http://www.ontologydesignpatterns.org/cp/owl/observation.owl#Parameter
http://www.ontologydesignpatterns.org/cp/owl/observation.owl#hasObservation
http://www.ontologydesignpatterns.org/cp/owl/observation.owl#hasParameter
http://www.ontologydesignpatterns.org/cp/owl/observation.owl#inDate
http://www.ontologydesignpatterns.org/cp/owl/observation.owl#isObservationOf
http://www.ontologydesignpatterns.org/cp/owl/observation.owl#isParameterOf
http://www.ontologydesignpatterns.org/cp/owl/situation.owl#Situation
http://www.ontologydesignpatterns.org/cp/owl/situation.owl#hasSetting
http://www.ontologydesignpatterns.org/cp/owl/situation.owl#isSettingFor

An example of it in use¶

The pattern says what may be asserted; this says it. The graph below is a small set of individuals that instantiate the classes above and are connected by its properties, so the shape the pattern describes is visible as data rather than as a schema.

Download the example

Import this pattern into your own ontology from inside Protégé: OntoBoard → Reuse → Pattern library…, which hands it to Import terms… and writes the term list, the module, the import and the catalog entry the way ODK expects. See Working with ODK.

Something wrong with this pattern, its example or this page? Report a problem with this pattern - the form opens with the pattern filled in, and a title and a sentence are all it needs.