Property:ContentODPDescription

From Odp

Jump to: navigation, search

This property is of type Text.

This property is a subproperty of PatternSolution.


(previous 25) (next 25)

Pages using the property "ContentODPDescription"

Showing 25 pages using this property.

C

CollectionEntity +This pattern is a basic one: it catches the idea of a collection and its members.
CommunicationEvent +The pattern introduces a specialization of the participation pattern, where parties hold different roles when participating in communication events.
Communities +-
Componency +-
ComputationalEnvironment +The Computational Environment ontology design pattern models the environment in which a computational analysis was conducted down to the hardware level.
Computer System +The pattern represents a computer system, along with the involved software and hardware components. It also includes significant properties between these main entities.
ConceptGroup +How a group entity stands alone?, How to represent either a vocabulary subset, a cross vocabulary subset or a whole vocabulary?, How to represent group concept members?
ConceptTerms +A concept is named in a particular languag A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties. This list of properties may be extended depending on vocabulary specific needs. This pattern suits for various vocabularies (thesaurus, terminology, taxonomy…) and has been applied to GEMET, Eurovoc, CIM10 among other. Modeling takes into account: -the possibility to extend the current pattern in order to add some more precise linguistic information (for instance represent translation relation between two terms since term is a class) -minimal linguistic artifacts necessary for vocabulary resource access by providing a preferred Term to name a concept and some synonyms which are Simple non preferred terms. nyms which are Simple non preferred terms.
Constituency +-
ContextualizedWinstonPartWhole +To provide a contextualized version of the WinstonPartWhole pattern.
Controlflow +-
CountingAs +-
Course +This pattern represents the basic attributes of a given course. It allows us to know the name, number, and level of the course. Also, we can know the instructor who teaches the course and the student who take the course.
Criterion +The criterion is defined as a subclass of description. The owl file linked below contains a simple example of how this pattern could be implemented for modeling a requirement (see 'Examples').
CriterionSetter +This is a specialization of criterion patt This is a specialization of criterion pattern. The criterion setter can be used as an abstract container for requirements, recommendations, constraints etc. The owl file linked below contains a simple example of how this pattern could be implemented for modeling a requirement (see 'Examples'). r modeling a requirement (see 'Examples').

D

Description +-
Description in Range +The Description In Range (DIR) ontology design patterns is a specialization of the Description ODP, that allows one to range the conceptualization of a descriptive context within specific borders defined by means of literal values.
DetectorFinalState +This pattern represent schematic model for This pattern represent schematic model for data obtained from results of high-energy physics experiments, such as ones ran in the CERN's Large Hadron Collider. Specifically, this pattern models the notion of Detector Final State, a composition obatined by a selection of some target characteristics concerning physics measurements and parameters of experiments. easurements and parameters of experiments.
DigitalVideo +The pattern’s main entity is a digital vid The pattern’s main entity is a digital video file (DigitalVideo). Appropriate object properties connect the video file with codecs, streams, containers, etc. Additionally, the model includes the most significant descriptors for all the previous notions, such as bitrate, aspect ratio, compression type, etc. rate, aspect ratio, compression type, etc.
Disposition +Relations are being defined between dispos Relations are being defined between dispositions, their realizations processes and their triggering processes. The pattern is easily compatible with many top-level ontologies. In this description, we use classes from BFO and BioTop. References: - Roehl/Jansen: "Representing Dispositions", Journal of Biomedical Semantics 2011, 2(Suppl 4):S4 (9 August 2011). - BioTop, http://www.imbi.uni-freiburg.de/ontology/biotop/. www.imbi.uni-freiburg.de/ontology/biotop/.

E

EEP +The Execution-Executor-Procedure (EEP) ODP The Execution-Executor-Procedure (EEP) ODP imports the AffectedBy ODP (https://w3id.org/affectedBy), that involves classes for Features of Interest and their intrinsic Properties/Qualities. The EEP ODP is an adaptation of the Procedure Execution Ontology (PEP) (https://w3id.org/pep/pep-1.1) from the SEAS ontology which, in turn, is a generalization of the Observation-Sensor-Procedure and Actuation-Actuator-Procedure patterns used in the SOSA (http://www.w3.org/ns/sosa/) and SSN (http://www.w3.org/ns/ssn/) ontologies. From the AffectedBy ODP, the EEP ODP imports the notion that a property/quality is intrinsic to the feature of interest that it belongs to (i.e., according to the definition of the class Quality in the DUL ontology http://www.ontologydesignpatterns.org/ont/dul/DUL.owl). Apart from the two classes imported from the AffectedBy ODP (aff:FeatureOfIntetest and aff:Quality), the EEP ODP consists of three more classes: Execution, Executor, and Procedure. The class Execution and their three functional object properties eep:madeBy, eep:usedProcedure, and eep:onQuality, form the backbone of the ODP. The property eep:madeBy links an execution to its executor, the property eep:usedProcedure links an execution to its procedure, and the property eep:onQuality links an execution to the quality/property concerned by the execution. Therefore, an execution jointly with their three object values of the three aforementioned properties can be considered as a n-ary relationship. Note that every quality belongs to unique feature of interest. Therefore, a feature of interest is involved in the n-ary relationship. The remaining object properties: eep:implements, that links executors to procedures, eep:hasFeatureOfInteres, that links executions to features of interest, eep:forQuality, that links executors to qualities, and eep:forFeatureOfInterest, that links executors to features of interest, are defined in terms of the functional object properties using property chain axioms. ct properties using property chain axioms.
EventCore +See Adila Krisnadhi; Pascal Hitzler : A Core Pattern for Events. Under review at WOP 2016
EventProcessing +See WOP2013 pattern abstract, and full paper.
ExplanationODP +Explanation

G

GO Top +-
(previous 25) (next 25)
Personal tools
Quality Committee
Content OP publishers