Property:HasConsequence

From Odp

Jump to: navigation, search

HasConsequence This property is assigned with a description of the benefits and/or possible trade-offs when using the Content Ontology Design Pattern. The value of this property is of type Text.

This property is a subproperty of Property:PatternConsequences.


(previous 25) (next 25)

Pages using the property "HasConsequence"

Showing 25 pages using this property.

A

AOS AGROVOC Concept Server fundation ontology model +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.
ActingFor +An ontology designer is able to express re 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). situation pattern should be used instead).
Action +The pattern allows to represent different types of actions, e.g. implemented actions or suspended actions, but does not enforce any rules such as "if an action is an instance of the class of completed actions it has to have the status 'completed' ".
ActivitySpecification +(-) Requires a temporal representation of (-) Requires a temporal representation of the domain -- specifically using the Logical OP for change -- which results in a larger, more complex representation. (+) However, given that the concepts are preconditions and effects of an activity, they should be subject to change and so the resulting representation is (though larger) more appropriate and more accurate. arger) more appropriate and more accurate.
AffectedBy +A quality cannot exist without the feature A quality cannot exist without the feature of interest to which it belongs. A quality is intrinsic to the feature of interest to which it belongs. For example, the temperature of room X cannot exist without the room X, and it is a different quality to the temperature of a different room Y. A quality can affect another quality, but not necessarily the other way around. For example, a quality Z may affect the quality W, but the quality W does not need to affect quality Z. ality W does not need to affect quality Z.
AgentRole +This CP allows designers to make assertions on roles played by agents without involving the agents that play that roles, and vice versa. It does not allow to express temporariness of roles.
An Ontology Design Pattern for Activity Reasoning +Only two perspectives for activities are included in this pattern. While these two perspectives are commonly observed in existing work, other views toward activities may also need to be supported in future work.
AquaticResourceObservation +We are able to query and reason on the data extracted from the FactSheets XML database, concerning the observation of aquatic resources. There are more data in that database, however.
AquaticResources +Relations between aquatic resources and ei Relations between aquatic resources and either aquatic species or water areas can be represented. In order to infer what species typically live in what water areas however, an application needs to add a SWRL rule, or a SPARQL query that unifies the hasSpecies and hasWaterArea relations. the hasSpecies and hasWaterArea relations.

B

Biological Entities +Classification of biological entities for the fishery domain.
Born Digital Archives +The design pattern is expected to facilitate the creation of domain ontologies related to Born Digital Archives that can be exploited in numerous fields. A well-established, comprehensible pattern will prove to be advantageous.

C

Complaint Design Pattern +Heterogeneous models for complaints can be aligned to this pattern, which then acts as a semantic facade to different complaint management applications (such as complaint handling process, customer complaint management, customer relation management)
CatchRecord +We are able to query time-series data for catches of species in a certain fishing area, by vessels of some country, with anounts and measurement units.
Classification +It is possible to make assertions about e. It is possible to make assertions about e.g., categories, types, roles, which are typically considered at the meta-level of an ontology. Instances of Concept reify such elements, which are therefore put in the ordinary domain of an ontology. It is not possible to parametrize the classification over different dimensions e.g., time, space, etc. fferent dimensions e.g., time, space, etc.
ClimaticZone +This pattern only allows to query what cli This pattern only allows to query what climatic zones are typical of an aquatic resource. Whereas such values can be subject to observation, another pattern based on the generic 'observation' pattern should be used. The climatic zone is intended to have a fixed set of values (to be defined as nominals) but this is not explicit in the pattern. ) but this is not explicit in the pattern.
Co-participation +Any two objects, agents, etc. participatin Any two objects, agents, etc. participating in a same event, even partly or for some limited time, can be related. The pattern provides room for representing participation in that event as well, by importing the [[Submissions:Participation]] pattern. This patterns does not allow to express the complete relation between an event and its participants: this has to be added manually. rticipants: this has to be added manually.
Collection +Collections and their members can be associated. Time-indexed membership cannot be represented though (you need a situation-based pattern).
CollectionEntity +It is possible to put sets in the domain of discourse through the class [[Submissions:CollectionEntity/Collection| Collection]], which reifies them. For temporary membership, the TimeIndexedMembership should be used.
CommunicationEvent +Pattern includes a set of standard communi Pattern includes a set of standard communication mechanisms, but can be extended., The pattern does not take into account time-indexed participation in relationships, nor time-indexed participation in communication events. All parties are assumed to participate during the whole duration of relationships and events. hole duration of relationships and events.
Componency +This Content OP allows designers to repres This Content OP allows designers to represent part-whole relations. It allows to distinguish between parts and proper parts. Relation of proper part ''is not transitive'', and implies a simple [[Submissions:PartOf| part of]] relation, which is ''transitive''. Temporal indexing is not expressible. To solve this issue see the [[Submissions:TimeIndexedPartOf| time indexed part of]] Content OP. PartOf| time indexed part of]] Content OP.
Computer System +The design pattern is expected to facilitate the creation of computer system domain ontologies that can be exploited in numerous fields. A well-established, comprehensible pattern will prove to be advantageous.
ConceptTerms +Compare to labels on a concept class, this solution has a higher data load.
Constituency +A desirable advantage of this CP is that w A desirable advantage of this CP is that we are able to talk e.g. of physical constituents of non-physical objects (e.g. systems), while this is typically impossible in terms of parts. This Content OP has to be distinguished from [[Submissions:PartOf| part of]], [[Submissions:CollectionEntiy| collection entity]], and [[Submissions:Componency| componency]] Content OPs. ions:Componency| componency]] Content OPs.
Course +The Course content ontology design pattern makes ontology engineers to design Academic, University ontology easier and in a more integrated way

D

Description +This CP allows the designer to represent both a (descriptive) context and the elements that characterize and are involved in that context.
(previous 25) (next 25)
Personal tools
Quality Committee
Content OP publishers