Showing 25 pages using this property.
S | |
|---|---|
| SpeciesEat + | Some subquery has no valid condition. + |
| SpeciesHabitat + | Some subquery has no valid condition. + |
| SpeciesHabitat + | The wikipage input value "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." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| SpeciesNames + | Some subquery has no valid condition. + |
| Standard Enforcer Pattern + | The wikipage input value "The remit of the SEP content pattern is to represent the relation between standards and the processes, operations, activities and services that enforce them, the domains they cater to and the scope of that specific process, operation, activity, service within the context of the domain." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Standard Enforcer Pattern + | The wikipage input value "SEP provides a mechanism to ontologically declare the conformance of a process with one or more standards. The pattern is flexible and compositional. It can be exploited to include few or more guidelines from multiple standards and can be easily combined with other patterns." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Standard Enforcer Pattern + | The wikipage input value "we present a use case from the domain of algal biomass production which depicts the application of SEP to an ontology that models algal biomass production. The Minimum Descriptive Language (MDL) standard proposed by the Algal Biomass Association is enforced by the production operation. MDL recommends a set of descriptive metrics to uniformly characterise the analysis of large scale algal operations. In this use case" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Standard Enforcer Pattern + | Some subquery has no valid condition. + |
| Standard Enforcer Pattern + | The wikipage input value "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." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Stub Metapattern + | Some subquery has no valid condition. + |
| Stub Metapattern + | The wikipage input value "When modeling an ontology, one of the issues to be addressed is that of granularity: To what detail should the ontology represent the notions it captures? Traditionally, this issue is resolved by looking at a concise definition of the use cases, e.g. by means of competency questions. As a result of this, some parts of the ontology may be modeled in a rather fine-grained manner, while other parts remain relatively coarse. A straightforward handling of differing granularity requirements in different parts of an ontology can make it more difficult to repurpose or extend the ontology, or to use it in an ontology-driven data integration setting. The reason is that because one is often faced with a situation where (s)he has to decide whether to represent a notion as a string literal value or an ontology entity such as a class. Choosing one over the other introduces a commitment that one may regret later on. For example, when modeling a location, one could use the location name as a string or model it as a possibly full-blown pattern for the notion of Place. Choosing the former may prevent future use case of data enrichment, e.g., for expressing co-location (as one cannot use owl:sameAs relation between two strings). Choosing the latter means committing to a particular way of modeling Place, which may not necessarily be desirable in the future. This pattern provides a way to solve this problem is to essentially keep both in the model, i.e., by including the literal value in the model, while employing a very minimalistic pattern for the notion. The latter is realized only as a single class." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Stub Metapattern + | The wikipage input value "One wishes to instantiate the Stub Metapattern for representing the notion of Place. To do it, the following steps need to be done in all of the axiom patterns.
|
| Stub Metapattern + | The wikipage input value "The solution is a metapattern. That is, it uses one "variable" class and two "variable" properties. The intention here is that when one wishes to use this metapattern, (s)he needs to instantiate the "variable" class and properties into actual class and properties. See Example section for a more concrete example." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Stub Metapattern + | The wikipage input value "Entities and variable entities:
Axiom patterns (in Manchester Syntax):
|
| Summarization of an inverse n-ary relation + | The wikipage input value "The main advantage of this pattern is that allows asking for those services that are provided by a service provider and vice-versa without a complex query (this complex query would involve the class created to support the n-ary relation between service providers and services)." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Summarization of an inverse n-ary relation + | The wikipage input value "The aim of this pattern is to allow asking for n-ary relationships and their inverse relations between two distinguished participants without a complex query (Such a comples query would involve the class created to support the n-ary relation between the origin and destination classes of the n-ary relationship)." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Summarization of an inverse n-ary relation + | The wikipage input value "We might want to represent that a service provider provides a service at a place in a given period of time with a particular price. The model should also represent that a service is offered by a provider. We have also observed that the queries executed by our applications often ask for the relationship between providers and their services and rarely ask for the relationships about the services and where they are provided.
|
| Summarization of an inverse n-ary relation + | Some subquery has no valid condition. + |
| Summarization of an inverse n-ary relation + | The wikipage input value "An n-ary relationship should be used to address any of the following situations: (a) a binary relationship that really needs a further argument. For example, to represent the distance between two places. (b) two binary relationships that always go together and should be represented as one n-ary relation. For example, to represent the value of an observation (e.g. temperature in a patient) and its trend. (c) a relationship that is really amongst several things. For example, to represent the spatial location of a person in a given point of time. On the one hand, the motivation of this pattern is to express the inverse relationship of an n-ary relation where there are distinguished participants. This means that the relationship exists mainly between two entities and the rest of entities involved in the relationship can be considered as additional arguments. This situation can also mean that there is a single individual standing out as the subject or the "owner" of the relation. On the other hand, the motivation is to provide a shorcut for queries that involve the distinguished participants in the n-ary relationship. This pattern is inspired on the third consideration shown in http://www.w3.org/TR/swbp-n-aryRelations/#choosingPattern1or2. The difference in our case is that there are at least two distinguished participants in the relationship. Therefore, this pattern could be considered as an extension of the third consideration shown in http://www.w3.org/TR/swbp-n-aryRelations./#choosingPattern1or2 applied to the use case of n-ary relationships described in http://www.w3.org/TR/swbp-n-aryRelations/#useCase1." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Symmetric n-ary relationship + | The wikipage input value "The symmetric n-ary relationship pattern emerged from the need of modelling distances among two points. This problem is a clear case of an n-ary relationship where the relation between two points needs a further argument to represent the distance between such points. Once we have applied the n-ary pattern for this use case (http://www.w3.org/TR/swbp-n-aryRelations/#useCase1), we can realize that the origin and the destination of the n-ary relation belong to the same class. In addition, the value for the relationship is the same to represent the distance from A to B and vice-versa. Then, if we want to represent both distances we should instanciate the pattern twice, from A to B and vice-versa, resulting in a redundant representation." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Symmetric n-ary relationship + | The wikipage input value "Class, Relationship, Attribute Axioms: cardinality and equivalentClass" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Symmetric n-ary relationship + | Some subquery has no valid condition. + |
| Symmetric n-ary relationship + | The wikipage input value "A class to represent the n-ary relationship together with the value for the further needed argument (Relationship or Attribute) has been created. A relationship between the abovementioned class and the classes involved in the symmetric n-ary relationship is created." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Symmetric n-ary relationship + | The wikipage input value "This pattern allows representing symmetric n-ary relationships, i.e. binary relationships between two elements that need a further argument that has the same value for both directions of the relationship. If SNAry is the symmetric n-ary relationship and z is its value for the elements x and y, then: SNAry(x,y)=z iff SNAry(y,x)=z" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| SynonymOrEquivalence (SOE) + | The wikipage input value "The ontology developer wants to express that two classes C1 and C2 are identical. This is not very useful in a single ontology that does not import others. Indeed, what the ontology developer generally wants to represent is a terminological synonymy relation: the class C1 has two labels: C1 and C2. Usually one of the classes is not used anywhere else in the axioms defined in the ontology." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
'Ontology Design Patterns'
