Showing 25 pages using this property.
R | |
---|---|
RecurrentSituationSeries + | The wikipage input value "A recurrent situation series is modelled as an intersection of a collection and a situation. Indeed, a recurrent situation series is seen as a collection, since it contains entities that share one or more common properties and are unified conceptually (unifying factors). These entities are member of the collection, and are all consecutive situations. At the same time, a recurrent situation series is a situation, intended as a relational context in which the contextualised things are based on a frame: a recurrent situation series is similar to a plan that defines how the things involved in that plan (i.e. the specific events) shall be carried out, e.g. where the situations shall be located, in which time of the year, etc." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
RecurrentSituationSeries + | Some subquery has no valid condition. + |
Region + | The wikipage input value "We can represent and reason on *any* kind of attributes, parameters, features, etc., which have a given set of values. With the new OWL2 support for custom and complex datatypes, this pattern should be confronted with possible enrichments, or may be restricted to OWL1. Anyway, since datatypes cannot overlap with classes even in OWL2, it remains useful for the cases where the domain must be kept homogeneous." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
Region + | Some subquery has no valid condition. + |
RelativeRelationship + | Some subquery has no valid condition. + |
ReportingEvent + | The wikipage input value "There are in total 3 different types of events included in the pattern. The most important one is the ActualEvent, which is the physical event -- event that actually happened or is said to have happened. All the circumstances of the event (contexts) are not directly linked to the ActualEvent. They are attached to the ReportedEvent, which constitutes a view of the actual event included in a particular description/report/statement. By making the ReportedEvent an Event, we can use all properties that could be used in case of an ordinary event, like place, time interval, cause and consequences. They are grouped in a class ReportedEventContext and are attached by hasContext property or its specialisations. As ReportedEvent provides an information about the ActualEvent entity, it can be viewed as InformationObject. It is connected to an ActualEvent using the isAbout property. The third event included in our pattern is the act of reporting the actual event -- the ReportingEvent. Its result is an ReportedEvent (linked using property reports). By modelling the act of reporting as an event, we can expose its different circumstances, for example the timestamp at which the particular reporting took place. The ReportingEvent can be also viewed as an activity, performed by a certain agent (person or organisation) -- EventReporter, utilising defined sources." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
ReportingEvent + | The wikipage input value "The intent of the pattern is to allow for modelling situations in which the knowledge about an event cannot be treated as certain. It is particularly useful for cases in which two or more agents provide different, contradictory information about the same event. It can be also used for modelling situation in which a single agent provided contradictory information about the same event in different points in time. In general the pattern allows for stating different circumstances of an act of the information provision." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
ReportingEvent + | Some subquery has no valid condition. + |
ReportingEvent + | The wikipage input value "Two History professors have different opinion about the same actual event. The exemplary actual event is baptism of prince Mieszko I. The baptism exact place is a subject to historical debate. According to professor Hanna Kóčka-Krenz the likely place was Poznań. She bases her claim on Poznań excavations that she conducted. However the late professor Labuda pointed to Lednica Holm. He also based his claims on the local excavations but also on historical annals." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
ReportingNewsEvent + | The wikipage input value "The pattern extends the ReportingEvent pattern by specifying the primary properties of the specialisation of the ReportingEvent class. The specialisation, NewsEventReportingEvent, denotes the act of providing a unit of information (ReportedNewsEvent) to the general public. The act utilises a certain Media (TV station, radio station, newspaper, website). A Media is owned by a certain SocialAgent - NewsProvider. This agent takes partial responsibility for the content provided, but its responsibility differs from the one of the NewsEventReporter -- an Agent that directly reports the ActualEvent. Other properties which are very important for NewsEventReportingEvent are time at which the event is reported and the context of presentation." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
ReportingNewsEvent + | The wikipage input value "The pattern can be used for modelling situations in which we are not certain that a particular actual event has the properties which were described in a news message. We want to define the properties of an actual event which were reported (time, place, actors, subevents, cause, effect etc.), but not to treat them as universal, verified knowledge. The pattern also allows to define who is responsible for a particular description of an event and how this description is dealt with." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
ReportingNewsEvent + | Some subquery has no valid condition. + |
ReportingNewsEvent + | The wikipage input value "The pattern is rather complex and should only be used if the circumstances of the events presented in a media are expected to be uncertain (to differ in different news event reports of different news providers)." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
ResourceAbundanceObservation + | The wikipage input value "The patterns states that for each instance of the resource observation all parameters exist, this does not however mean that they are necessarily present in the knowledge base. Any dependencies between parameters have not been taken intor account, there are no formal restrictions on the combination possible. The parameters are intended to have a fixed set of values (to be defined as nominals) but this is not explicit in the pattern." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
ResourceAbundanceObservation + | Some subquery has no valid condition. + |
ResourceExploitationObservation + | Some subquery has no valid condition. + |
ResourceExploitationObservation + | The wikipage input value "The patterns states that for each instance of the resource observation all parameters exist, this does not however mean that they are necessarily present in the knowledge base. Any dependencies between parameters have not been taken intor account, there are no formal restrictions on the combination possible. The parameters are intended to have a fixed set of values (to be defined as nominals) but this is not explicit in the pattern." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
Role task + | Some subquery has no valid condition. + |
Roles (OWL 2) + | The wikipage input value "Extend theSocial Reality (OWL 2) pattern with classes for roles, functions, agents and actions. Create a new subproperty "plays" for the counts-as relation. We create new property chains to traverse the context and plays relation, that allow us to infer the role-as-relation from the role-as-class description. Imports theSocial Reality (OWL 2) pattern from [1]." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
Roles (OWL 2) + | The wikipage input value "Capture the relational nature of roles using OWL 2 property chains, using theSocial Reality (OWL 2) pattern. Using this pattern the role-as-relation and role-as-class approach can coexist peacefully inside a single ontology." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
Roles (OWL 2) + | Some subquery has no valid condition. + |
S | |
Sequence + | Some subquery has no valid condition. + |
Sequence + | The wikipage input value "To represent sequence schemas. It defines the notion of transitive and intransitive precedence and their inverses. It can then be used between tasks, processes, time intervals, spatially locate objects, situations, etc." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
Sequence + | The wikipage input value "This pattern is a basic one; it represents the 'path' cognitive schema, which underlies many different conceptualizations: spatial paths, time lines, event sequences, organizational hierarchies, graph paths, etc. Sequence pattern reuses the logical pattern Transitive reduction, in order to represent both transitive and non-transitive precedence relations." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
Set + | Some subquery has no valid condition. + |