Property:HasConsequence
From Odp
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 22 pages using this property.
S | |
|---|---|
| Spatial Graph Adapter (SGA) + | [[Image:USOcore3.jpg|700px|thumb|center|SG … [[Image:USOcore3.jpg|700px|thumb|center|SGA Pattern]] With the capabilities the SGA pattern provides, it has been found to be useful and as been implemented for IFC, GBXML, and CityGML is currently in progress. Once this mapping was produced and captured via this pattern, further work was possible and completed in the form of View helper files and all of this is being worked into an operational Linked Data Platform to further enhance open data exchange. Our work was inspired by ideas from Spatial Information Theory, biomedical research for the Semanticscience Integrated Ontology (SIO), Mereotopology, and geospatial data efforts via the Open Geospatial Consortium (OGC), although these are not the only works regarding spatial descriptions. only works regarding spatial descriptions. |
| SpeciesBathymetry + | The pattern allows to represent species wi … The pattern allows to represent species with a typical bathymetric range and a typical water area where the exemplars (from an AquaticResource) can be found. However, there is no direct relation between the bathymetric range and the water area; in principle, it is possible that there are no places in the water area that provide the conditions for that bathymetric range. In order to represent a condition on the bathymetric range to be realized in the water area, the situation pattern should be reused and specialized, as in the speciesconditions.owl pattern. , as in the speciesconditions.owl pattern. |
| 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. |
| SpeciesHabitat + | The pattern allows to represent species wi … The pattern allows to represent species with a typical habitat and a typical water area where the exemplars can be found. However, there is no direct relation between the habitat (type) and the water area; in principle, it is possible that there are no places in the water area that provide the conditions for that habitat. In order to represent that a species has a habitat within a given water area, the situation pattern should be reused and specialized, as in the speciesconditions.owl pattern. , as in the speciesconditions.owl pattern. |
| SpeciesNames + | Terminological and conceptual similarity between species can be encoded byusing the three properties in this pattern. |
| Standard Enforcer Pattern + | The pattern can be applied to use cases in … The pattern can be applied to use cases in all those domains where a standard is enforced to regulate processes. The main advantage of this pattern is that it provides the capability to link processes, operations, activities and services to their governing standards in a generic and compositional manner. In some scenarios it is possible that a process or an operation does not enforce all prescribed guidelines but enforces atleast some. The pattern accounts for that through the definition of the process enforcing the standard. ion of the process enforcing the standard. |
T | |
| Tagging + | We are able to represent data about tagging activities from web 2.0 applications, from document annotation projects, or from RDFa documents. |
| TaskExecution + | This CP allows designers to make assertion … This CP allows designers to make assertions on roles played by agents without involving the agents that play that roles, and vice versa. It allows to express neither the context type in which tasks are defined, not the particular context in which the action is carried out. Moreover, it does not allow to express the time at which the task is executed through the action (for actions that do not solely execute that certain task). do not solely execute that certain task). |
| Time indexed participation + | We can represent participation relations w … We can represent participation relations with time. This enables participations at different times as well as partial participations in events. However, this pattern focuses on participation of one entity in one event. If complex events need to be represented (with subevents, more participants and times, etc.), a partonomic structure must be introduced, e.g. by creating a new pattern that composes TimeIndexedParticipation with PartOf. oses TimeIndexedParticipation with PartOf. |
| TimeIndexedPartOf + | This Content OP allows designers to represent part-whole relations with a temporal index (holding at a certain time). |
| TimeIndexedSituation + | We can represent situations that have an explicit time parameter. In principle, this can be done already with the Situation pattern, but this provides a handy composition with the TimeInterval pattern. |
| TimeInterval + | The dates of the time interval are not part of the domain of discourse, they are datatype values. If there is the need of reasoning about dates this Content OP should be used in composition with the [[Submissions:Region| region]] Content OP. |
| TimePeriod + | The measurement unit and the numerical value of a time period (e.g. 1 year) can be modelled. |
| Topic + | We are able to represent topics, subjects, … We are able to represent topics, subjects, or themes of something, and to organize topics into partonomic and topological structures. In order to represent more sophisticated relations between topics, concepts, terms, etc., refer to the full ontopic.owl ontology. ., refer to the full ontopic.owl ontology. |
| Trajectory + | Unlike the original version of Semantic Tr … Unlike the original version of Semantic Trajectory, this pattern omits the hook to the data source for fixes (which was a subclass of ssn:Device) because instead of location/geo-coordinate, the notion of place is employed to capture the spatial extent. Nevertheless, it should be relatively straightforward to extend this version if the user wishes to attach data source information to the fixes. tach data source information to the fixes. |
| Transition + | We are able to represent part of the seman … We are able to represent part of the semantics involved in transitions (e.g. what is implied by Petri Nets): initial and final states, causal events, underlying processes, affected objects, and sequences of time intervals for situations and events. However, it is not possible to define axioms for automatically infer initial and final states from time sequences, because coreference is not allowed in OWL (not even in OWL2). is not allowed in OWL (not even in OWL2). |
| 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. |
V | |
| VerticalDistribution + | This pattern only allows to query what ver … This pattern only allows to query what vertical distribution is 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 vertical distribution 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. |
| VesselSpecies + | This pattern should be used in scenarios w … 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. restrictions having beed applied instead. |
| VesselWaterArea + | The pattern can be used to represent a wat … The pattern can be used to represent a water area setting and the vessels that can be used there, no matter whether these constraints are legal or logistic. The hasWaterArea object property is used as in the gearwaterarea pattern. Usage of this property as applied to VesselTypes is related to, but not strictly dependent on the hasWaterArea property as applied to GearTypes. aterArea property as applied to GearTypes. |
