Property:HasConsequence

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.

Pages using the property "HasConsequence"

Showing 19 pages using this property.

View (previous 25 | next 25) (20 | 50 | 100 | 250 | 500)

O
Observation +	We are able to represent the parameters of observations made.  +
P
ParticipantRole +	This pattern does not take into account time aspects of the participation, for such aspects see the timeindexedparticipation-pattern.  +
PeriodicInterval +	This content pattern allows designers to represent non-convex intervals where the period between subintervals, that is, the gaps between subintervals, and the duration of the subintervals are constant.  +
PharmaInnova +	Especific models for invoices can be aligned to this pattern, which then acts as a semantic facade to different invoice management applications. This pattern is concreter and simplier, but less flexible than the invoice ODP.  +
Policy +	The Policy ODP is expected to facilitate the representation of the policy notion, which can be exploited in various domains. A well-established, comprehensible pattern will prove to be advantageous.  +
R
Reaction +	This model solution is time-indexing independent. Datatypes for that are not provided and probably it should be avoided. The focus is on the sequence.  +
RecurrentEventSeries +	A series of recurrent events, its unifying factors and the recurrent time period can be modelled.  +
RecurrentSituationSeries +	A series of recurrent situations, its unifying factors and the recurrent time period can be modeled.  +
ReportingEvent +	The pattern is rather complex and should only be used if the circumstances of the events are expected to be uncertain (to differ in different event reports).  +
Role task +	This pattern allows to put roles in the domain of discourse. It does not allow to model time indexed task assignement.  +
S
Sequence +	We can represent and reason over transitive or intransitive sequences of any kind. However, since coreference cannot be expressed in OWL, it is not possible to represent and reason over loops and other sequences involving coreference.  +
SpeciesConditions +	This pattern allows to represent the contextualized features of an aquatic species. For simpler representation of those features (non-contextualized to a water area), use specieshabitat.owl and speciesbathymetry.owl.  +
SpeciesConservation +	The conservation status is simply represented as a string, there are no restrictions on how to express the status, thereby an additional convention on how to express this in natural language could be needed if a uniform naming of status levels is desired.  +
SpeciesNames +	Terminological and conceptual similarity between species can be encoded byusing the three properties in this pattern.  +
T
Tagging +	We are able to represent data about tagging activities from web 2.0 applications, from document annotation projects, or from RDFa documents.  +
TimeIndexedPartOf +	This Content OP allows designers to represent part-whole relations with a temporal index (holding at a certain time).  +
TimePeriod +	The measurement unit and the numerical value of a time period (e.g. 1 year) can be modelled.  +
TransportPattern +	This CP allows data modellers and ontology creators the ability to filter and categorise large geoscience data stores.  +
Types of entities +	The type of any element of the knowledge base is always known.  +