Distinct objects for predicate rdfs:comment in graph dpo sorted by frequency with mapping to SKOS

ResourceCountSKOS mapping
"Quantifiable presence information concerning the agent's sensed absolute and relative altitude."2
""1
"A generic property that assign a quantifiable value to a presence component. Minimum and maximum values are provided as its subproperties. Various subproperties of different types of values are also provided and apply to specific types of presence components."1
"A presence component that can be quantified. In this case, discrete user context properties obtained from sensors can be mapped to their loosely-defined fuzzy counterparts. Thus for example, the actual and dynamic temperature of an agent's environment can be mapped to an existing category that is saved as an instance of a presence component. Each of these categories has a number of attributes that define its valid actual data range, e.g., a presence component representing 'hot' weather conditions around an agent will be enabled (i.e., it becomes part of the agent's presence) only if the actual sensed temperature lies within the ranges defined by the value limits. As most quantifiable presence components posses this restrictions, tree generic properties are applicable: dpo:value, dpo:minValue, dpo:maxValue."1
"A subproperty of dpo:axValue that defines an upperbound on the observed wave height (in metres) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:minWaveHeight to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world wave heights in a body of water. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed altitude height value (in metres) such that it can classify as a dpo:Altitude instance. It can be used in conjunction with dpo:minAltitude, i.e. specific instances of dpo:Altitude have a pre-defined range of observable real-world agent altitude."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed brightness level value (in SI lux units) such that it can classify as a dpo:Brightness instance. It can be used in conjunction with dpo:minBrightnessLevel, i.e. specific instances of dpo:Brightness have a pre-defined range of observable real-world surrounding brightness levels."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed calendar year such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:minYear, i.e. specific instances of dpo:TimePeriod have a pre-defined observable year-based period."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed cloud cover (as a percentage) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:minCloudCover to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world cloud cover levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed day of the month (i.e., between 1 and 31) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:minDayOfMonth, i.e. specific instances of dpo:TimePeriod have a pre-defined observable monthly period."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed day of the week (i.e., between 1 signifying Monday and 7 signifying Sunday) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:minDayOfWeek, i.e. specific instances of dpo:TimePeriod have a pre-defined observable 7-day week-based period."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed humidity value (as a percentage) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:minHumidity to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world humidity levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed loudness level value (in decibels) such that it can classify as a dpo:Noise instance. It can be used in conjunction with dpo:minNoiseLevel, i.e. specific instances of dpo:Noise have a pre-defined range of observable real-world surrounding noise levels."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed month (i.e., between 1 signifying January and 12 signifying December) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:minMonth, i.e. specific instances of dpo:TimePeriod have a pre-defined observable month number-based period."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed precipitation levels (in millimetres per hour) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:minPrecipitation to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world precipitation levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed snowfall (in millimetres per hour) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:minSnowfallDegree to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world snowfall levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed speed value (in metres per second) such that it can classify as a dpo:Movement instance. It can be used in conjunction with dpo:minSpeed, i.e. specific instances of dpo:Movement have a pre-defined range of observable real-world agent speed levels."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed temperature value (in degrees celcius) such that it can classify as a dpo:Temperature or dpo:WeatherCondition instance. It can be used in conjunction with dpo:minTemperature, i.e. specific instances of the former two classes have a pre-defined range of observable real-world temperatures. Since this property has the described dual-domain, the domain is generic. However, it is not meant to be attached to other types of quantifiable component instances."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed time (in hours, i.e., between 0 signifying midnight and 23 signifying 11pm) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:minHour, i.e. specific instances of dpo:TimePeriod have a pre-defined observable 24-hour-based period."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed time value (in xsd:time format) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:minTime, i.e. specific instances of dpo:TimePeriod have a pre-defined range of observable time periods."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed visibility (in kilometres) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:minVisibility to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world visibility levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed week of the year (i.e., between 1 and 52) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:minWeek, i.e. specific instances of dpo:TimePeriod have a pre-defined observable week number-based period."1
"A subproperty of dpo:maxValue that defines an upperbound on the observed windscale (on the Beaufort scale) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:minWindScale to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world wind levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed altitude height value (in metres) such that it can classify as a dpo:Altitude instance. It can be used in conjunction with dpo:maxAltitude, i.e. specific instances of dpo:Altitude have a pre-defined range of observable real-world agent altitude."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed calendar year such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:maxYear, i.e. specific instances of dpo:TimePeriod have a pre-defined observable year-based period."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed cloud cover (as a percentage) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:maxCloudCover to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world cloud cover levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed day of the month (i.e., between 1 and 31) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:maxDayOfMonth, i.e. specific instances of dpo:TimePeriod have a pre-defined observable monthly period."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed day of the week (i.e., between 1 signifying Monday and 7 signifying Sunday) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:maxDayOfWeek, i.e. specific instances of dpo:TimePeriod have a pre-defined observable 7-day week-based period."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed humidity value (as a percentage) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:maxHumidity to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world humidity levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed month (i.e., between 1 signifying January and 12 signifying December) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:maxMonth, i.e. specific instances of dpo:TimePeriod have a pre-defined observable month number-based period."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed precipitation levels (in millimetres per hour) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:maxPrecipitation to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world precipitation levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed snowfall (in millimetres per hour) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:maxSnowfallDegree to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world snowfall levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed temperature value (in degrees celcius) such that it can classify as a dpo:Temperature or dpo:WeatherCondition instance. It can be used in conjunction with dpo:maxTemperature, i.e. specific instances of the former two classes have a pre-defined range of observable real-world temperatures. Since this property has the described dual-domain, the domain is generic. However, it is not meant to be attached to other types of quantifiable component instances."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed time (in hours, i.e., between 0 signifying midnight and 23 signifying 11pm) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:maxHour, i.e. specific instances of dpo:TimePeriod have a pre-defined observable 24-hour-based period."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed time value (in xsd:time format) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:maxTime, i.e. specific instances of dpo:TimePeriod have a pre-defined range of observable real-world time periods."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed uv index levels (linear scale of between 0 and 12 signifying 11+) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:maxUVIndex to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world UV index levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed visibility (in kilometres) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:maxVisibility to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world visibility levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed wave height (in metres) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:maxWaveHeight to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world wave heights in a body of water. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed week of the year (i.e., between 1 and 52) such that it can classify as a dpo:TimePeriod instance. It can be used in conjunction with dpo:maxWeek, i.e. specific instances of dpo:TimePeriod have a pre-defined observable week number-based period."1
"A subproperty of dpo:minValue that defines a lowerbound on the observed windscale (on the Beaufort scale) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:maxWindScale to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world wind levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:minValue that defines an lowerbound on the observed brightness level value (in SI lux units) such that it can classify as a dpo:Brightness instance. It can be used in conjunction with dpo:maxBrightnessLevel, i.e. specific instances of dpo:Brightness have a pre-defined range of observable real-world surrounding brightness levels."1
"A subproperty of dpo:minValue that defines an lowerbound on the observed loudness level value (in decibels) such that it can classify as a dpo:Noise instance. It can be used in conjunction with dpo:maxNoiseLevel, i.e. specific instances of dpo:Noise have a pre-defined range of observable real-world surrounding noise levels."1
"A subproperty of dpo:minValue that defines an lowerbound on the observed speed value (in metres per second) such that it can classify as a dpo:Movement instance. It can be used in conjunction with dpo:maxSpeed, i.e. specific instances of dpo:Movement have a pre-defined range of observable real-world agent speed levels."1
"A subproperty of dpo:minValue that defines an upperbound on the observed uv index levels (linear scale of between 0 and 12 signifying 11+) such that it can classify as a dpo:WeatherCondition instance. It can be used in conjunction with dpo:minUVIndex to state that specific instances of dpo:WeatherCondition have a pre-defined range of observable real-world UV index levels. In addition, they can also be used with various other weather conditions values and ranges to define complex weather condition types."1
"A subproperty of dpo:value defining a lowerbound on the value observed for a real-world entity for it to classify as an instance of a specific quantifiable presence component. Various subproperties are provided and apply to specific types of presence components."1
"A subproperty of dpo:value defining an upperbound on the value observed for a real-world entity for it to classify as an instance of a specific quantifiable presence component. Various subproperties are provided and apply to specific types of presence components."1
"A subproperty of dpo:value that defines an exact date/time value (a day in a month, i.e., between 1 and 31) such that it can classify as a dpo:TimePeriod instance."1
"A subproperty of dpo:value that defines an exact date/time value (a day in a week, i.e., between 1 signifying Monday and 7 signifying Sunday) such that it can classify as a dpo:TimePeriod instance."1
"A subproperty of dpo:value that defines an exact date/time value (a month, i.e., between 1 signifying January and 12 signifying December) such that it can classify as a dpo:TimePeriod instance."1
"A variant subproperty of dpo:maxAltitude that defines an upperbound on the computed absolute altitude (i.e. altitude relative to the level of the terrain in the area), rather the observed true altitude. Can be used in conjunction with dpo:minAbsoulateAltitude."1
"A variant subproperty of dpo:minAltitude that defines a lowerbound on the computed absolute altitude (i.e. altitude relative to the level of the terrain in the area), rather the observed true altitude. Can be in conjunction with dpo:maxAbsoulateAltitude."1
"Defines the owner (pimo:Agent) of the presence component, who is typically also the owner of the PIM instance. In contrast to other presence ontologies, this property is not intended to be used to describe an agent's current presence. The DCON ontology is provided to fulfil this purpose."1
"Links a generic activity to specific tasks and events (pimo:ProcessConcept instances) that are also stored in the PIM and that are known to be of the same type, e.g., a dpo:Activity representing 'sports' to a recurring event representing 'swimming lessons' stored in the agent's calendar."1
"Links a generic place type to specific locations (pimo:Location instances) that are known to be of the same type, e.g., a dpo:Place representing 'restaurants' to actual location instances representing specific restaurants. This property is also used to link generic activities (dpo:Activity instances) to one or more specific locations at which they habitually take place, e.g., an activity representing 'sports' to location instances representing sports grounds, gymnasia, etc. Due to the multiple assocations of locations to places and activities, the domain for this property is bound to dpo:NonQuantifiableComponent instances. However, it is not intended to associate locations to other subclasses of that domain."1
"Links a place to specific activities, both of which are stored in the PIM, e.g., a dpo:Place representing 'SportsCentre' to a dpo:Activity representing 'Sports'."1
"Non-qauntifiable presence components refer to interpreted context properties that can be resolved to a more abstract representations that have the ability to recur. For example, a location in which an agent finds itself in can be resolved to a known place that is known, or saved. Although the location is a temporal property bound to the agent's context (i.e., it is always changing), the place is independent of time (i.e., the agent can return to that place repeatedly)."1
"Non-quantifiable presence information concerning the current activity of the agent."1
"Non-quantifiable presence information concerning the current broadcast virtual availability of the agent."1
"Non-quantifiable presence information concerning the current broadcast virtual mood of the agent."1
"Non-quantifiable presence information concerning the type of location that an agent is currently near to. Multiple distinct locations can correspond to the same place instance."1
"Quantifiable presence components concerning the audible noise levels in the environment surrounding the agent."1
"Quantifiable presence components concerning the brightness levels in the environment surrounding the agent."1
"Quantifiable presence components concerning the detected temperature in the environment surrounding the agent."1
"Quantifiable presence components concerning the environment surrounding the agent are grouped under this abstract class. "1
"Quantifiable presence information concerning pre-established time periods in an agent's days, weeks, months, and years."1
"Quantifiable presence information concerning the agent's sensed speed of movement."1
"Quantifiable presence information concerning the weather (current, forecast) in the agent's surroundings."1
"Represents a wide variety of components relating to a user's presence, which is an ensemble of physical and virtual context properties relating to an agent's circumstances and activities. User context properties obtained from different kinds of sensors can be interpreted, resolved or mapped to loosely-defined or fuzzy presence component counterparts. A characteristic of these components is that they are independent of time, i.e., each component can characterise an agent's presence in multiple and different times. Presence components are subclasses of pimo:Thing, and have two main subclasses: quantifiable and non-quantifiable presence components."1
"Stores the last date and time at which a particular presence component was last observed, by any of an agent's sensors."1