Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- Property comment "An observable Quality of an Event or Object. That is, not a quality of an abstract entity as is also allowed by DUL's Quality, but rather an aspect of an entity that is intrinsic to and cannot exist without the entity and is observable by a sensor.".
- Sensing comment "Sensing is a process that results in the estimation, or calculation, of the value of a phenomenon.".
- SensingDevice comment "A sensing device is a device that implements sensing.".
- Sensor comment "A sensor can do (implements) sensing: that is, a sensor is any entity that can follow a sensing method and thus observe some Property of a FeatureOfInterest. Sensors may be physical devices, computational methods, a laboratory setup with a person following a method, or any other thing that can follow a Sensing Method to observe a Property.".
- SensorOutput comment "A sensor outputs a piece of information (an observed value), the value itself being represented by an ObservationValue.".
- Stimulus comment "An Event in the real world that 'triggers' the sensor. The properties associated to the stimulus may be different to eventual observed property. It is the event, not the object that triggers the sensor.".
- SurvivalProperty comment "An identifiable characteristic that represents the extent of the sensors useful life. Might include for example total battery life or number of recharges, or, for sensors that are used only a fixed number of times, the number of observations that can be made before the sensing capability is depleted.".
- SurvivalRange comment "The conditions a sensor can be exposed to without damage: i.e., the sensor continues to operate as defined using MeasurementCapability. If, however, the SurvivalRange is exceeded, the sensor is 'damaged' and MeasurementCapability specifications may no longer hold.".
- System comment "System is a unit of abstraction for pieces of infrastructure (and we largely care that they are) for sensing. A system has components, its subsystems, which are other systems.".
- attachedSystem comment "Relation between a Platform and any Systems (e.g., Sensors) that are attached to the Platform.".
- deployedOnPlatform comment "Relation between a deployment and the platform on which the system was deployed.".
- deployedSystem comment "Relation between a deployment and the deployed system.".
- deploymentProcessPart comment "Has part relation between a deployment process and its constituent processes.".
- detects comment "A relation from a sensor to the Stimulus that the sensor can detect. \nThe Stimulus itself will be serving as a proxy for (see isProxyOf) some observable property.".
- featureOfInterest comment "A relation between an observation and the entity whose quality was observed. For example, in an observation of the weight of a person, the feature of interest is the person and the quality is weight.".
- forProperty comment "A relation between some aspect of a sensing entity and a property. For example, from a sensor to the properties it can observe, or from a deployment to the properties it was installed to observe. Also from a measurement capability to the property the capability is described for. (Used in conjunction with ofFeature).".
- hasDeployment comment "Relation between a System and a Deployment, recording that the System/Sensor was deployed in that Deployment.".
- hasMeasurementCapability comment "Relation from a Sensor to a MeasurementCapability describing the measurement properties of the sensor.".
- hasMeasurementProperty comment "Relation from a MeasurementCapability to a MeasurementProperty. For example, to an accuracy (see notes at MeasurementCapability).".
- hasOperatingProperty comment "Relation from an OperatingRange to a Property. For example, to a battery lifetime.".
- hasOperatingRange comment "Relation from a System to an OperatingRange describing the normal operating environment of the System.".
- hasProperty comment "A relation between a FeatureOfInterest and a Property of that feature.".
- hasSubSystem comment "Haspart relation between a system and its parts.".
- hasSurvivalProperty comment "Relation from a SurvivalRange to a Property describing the survial range of a system. For example, to the temperature extreme that a system can withstand before being considered damaged.".
- hasSurvivalRange comment "A Relation from a System to a SurvivalRange.".
- implementedBy comment "A relation between the description of an algorithm, procedure or method and an entity that implements that method in some executable way. For example, between a scientific measuring method and a sensor the senses via that method.".
- implements comment "A relation between an entity that implements a method in some executable way and the description of an algorithm, procedure or method. For example, between a Sensor and the scientific measuring method that the Sensor uses to observe a Property.".
- inCondition comment "Describes the prevailing environmental conditions for MeasurementCapabilites, OperatingConditions and SurvivalRanges. Used for example to say that a sensor has a particular accuracy in particular conditions. (see also MeasurementCapability)".
- inDeployment comment "Relation between a Platform and a Deployment, recording that the object was used as a platform for a system/sensor for a particular deployment: as in this PhysicalObject is acting as a Platform inDeployment Deployment.".
- isProducedBy comment "Relation between a producer and a produced entity: for example, between a sensor and the produced output.".
- isPropertyOf comment "Relation between a FeatureOfInterest and a Property (a Quality observable by a sensor) of that feature.".
- isProxyFor comment "A relation from a Stimulus to the Property that the Stimulus is serving as a proxy for. For example, the expansion of the quicksilver is a stimulus that serves as a proxy for temperature, or an increase or decrease in the spinning of cups on a wind sensor is serving as a proxy for wind speed.".
- madeObservation comment "Relation between a Sensor and Observations it has made.".
- observationResult comment "Relation linking an Observation (i.e., a description of the context, the Situation, in which the observatioin was made) and a Result, which contains a value representing the value associated with the observed Property.".
- observationResultTime comment "The result time is the time when the procedure associated with the observation act was applied.".
- observationResultTime comment "The result time shall describe the time when the result became available, typically when the procedure associated with the observation was completed For some observations this is identical to the phenomenonTime. However, there are important cases where they differ.[O&M]".
- observationSamplingTime comment "Rebadged as phenomenon time in [O&M]. The phenomenon time shall describe the time that the result applies to the property of the feature-of-interest. This is often the time of interaction by a sampling procedure or observation procedure with a real-world feature.".
- observationSamplingTime comment "The sampling time is the time that the result applies to the feature-of-interest. This is the time usually required for geospatial analysis of the result.".
- observedProperty comment "Relation linking an Observation to the Property that was observed. The observedProperty should be a Property (hasProperty) of the FeatureOfInterest (linked by featureOfInterest) of this observation.".
- observes comment "Relation between a Sensor and a Property that the sensor can observe.\n\nNote that, given the DUL modelling of Qualities, a sensor defined with 'observes only Windspeed' technically links the sensor to particular instances of Windspeed, not to the concept itself - OWL can't express concept-concept relations, only individual-individual. The property composition ensures that if an observation is made of a particular quality then one can infer that the sensor observes that quality.".
- ofFeature comment "A relation between some aspect of a sensing entity and a feature. For example, from a sensor to the features it can observe properties of, or from a deployment to the features it was installed to observe. Also from a measurement capability to the feature the capability is described for. (Used in conjunction with forProperty).".
- onPlatform comment "Relation between a System (e.g., a Sensor) and a Platform. The relation locates the sensor relative to other described entities entities: i.e., the Sensor s1's location is Platform p1. More precise locations for sensors in space (relative to other entities, where attached to another entity, or in 3D space) are made using DOLCE's Regions (SpaceRegion).".
- qualityOfObservation comment "Relation linking an Observation to the adjudged quality of the result. This is of course complimentary to the MeasurementCapability information recorded for the Sensor that made the Observation.".
- sensingMethodUsed comment "A (measurement) procedure is a detailed description of a measurement according to one or more measurement principles and to a given measurement method, based on a measurement model and including any calculation to obtain a measurement result [VIM 2.6]".
- Taxonomy comment "...".
- commonName comment "...".
- name comment "...".
- Event comment "An arbitrary classification of a space/time region, by a \n\t\tcognitive agent. An event may have actively participating agents,\n\t\tpassive factors, products, and a location in space/time.".
- Event comment "An arbitrary classification of a space/time region, by a cognitive agent. An event may have actively participating agents, passive factors, products, and a location in space/time.".
- Event comment "\n\t\tAn arbitrary classification of a space/time region, by a \n\t\tcognitive agent. An event may have actively participating agents,\n\t\tpassive factors, products, and a location in space/time.\n\t\t".
- Factor comment "\n\t\tEverything used as a factor in an event\n\t\t".
- Product comment "\n\t\tEverything produced by an event\n\t\t".
- agent comment "\n\t\tRelates an event to an active agent (a person, a computer, ... :-) )\n\t\t".
- factor comment "\n\t\tRelates an event to a passive factor (a tool, an instrument, an abstract cause...)\n\t\t".
- literal_factor comment "\n\t\tRelates an event to a factor which can be described as a literal. This property\n\t\tshould not be used as-is, but should be subsumed by other, more specific, properties\n\t\t(like an hypothetic :weatherCelsius, linking an event to a temperature).\n\t\t".
- place comment "Entité spatiale concernée par un événement".
- place comment "\n\t\tRelates an event to a spatial object.\n\t\t".
- product comment "\n\t\tRelates an event to something produced during the event---a sound, a pie, whatever...\n\t\t".
- sub_event comment "\n\t\tThis property provides a way to split a complex event (for example, a performance involving several \n\t\tmusicians) into simpler ones (one event per musician).\n\t\t".
- time comment "\n\t\tRelates an event to a time object, classifying a time region (either instantaneous or having an extent).\n\t\tBy using the Timeline ontology here, you can define event happening on a recorded track or on any \n\t\tmedia with a temporal extent.\n\t\t".
- timeline.owl comment "\n \tExtends owl-time ontology (http://www.w3.org/2006/time) with \n\tsupport for several timelines, acting as a backbone to adress \n\ttime interval/instants. \n\n\tMainly designed with a multimedia use-case in mind.\n\n\tCopyright (c) Yves Raimond, Samer Abdallah, Centre for Digital Music, Queen Mary, University of London\n\t".
- AbstractTimeLine comment "\n \tAbstract time lines may be used as a backbone for Score, Works, ... \n\tThis allows for TimeLine maps to relate works to a given \n\tperformance (this part was played at this time).".
- ContinuousTimeLine comment "A continuous timeline, like the universal one, or the one backing an analog signal".
- DiscreteTimeLine comment "A discrete time line (like the time line backing a digital signal".
- Instant comment "An instant (same as in OWL-Time)".
- Interval comment "An interval (same as in OWL-Time). Allen's relationships are defined in OWL-Time.".
- OriginMap comment "A timeline map linking a physical timeline to a relative one (originating at some point on the physical timeline)".
- PhysicalTimeLine comment "A \"physical\" time-line (the universal time line (UTC)) is an instance of this class. Other time zones consists in instances of this class as well, with a \"shifting\" time line map relating them to the universal time line map.".
- RelativeTimeLine comment "Semi infinite time line...canonical coordinate system --> adressed through xsd:duration since the instant 0.".
- ShiftMap comment "a map just shifting one timeline to another".
- TimeLine comment "Represents a linear and coherent piece of time -- can be either abstract (such as the one behind a score) or concrete (such as the universal time line).\nTwo timelines can be mapped using timeline maps.".
- TimeLineMap comment "Allows to map two time lines together".
- UniformSamplingMap comment "Describe the relation between a continuous time-line and its sampled equivalent".
- UniformSamplingWindowingMap comment "Describes the relation between a continuous time-line, and a time-line that corresponds to its sampled and windowed equivalent".
- UniformWindowingMap comment "Describes the relation between a discrete time line and its windowed equivalent".
- at comment "refers to a point or an interval on the time line, through an explicit datatype".
- atDate comment "A subproperty of :at, allowing to address a date (beginning of it for an instant, all of it for an interval)".
- atDateTime comment "This property links an instant defined on the universal time line to an XSD date/time value".
- atDuration comment "A property enabling to adress a time point P through the duration of the interval [0,P] on a continuous timeline".
- atInt comment "A subproperty of :at, having as a specific range xsd:int".
- atYear comment "A subproperty of :at, allowing to address a year (beginning of it for an instant, all of it for an interval)".
- atYearMonth comment "A subproperty of :at, allowing to address a year/month (beginning of it for an instant, all of it for an interval)".
- beginsAtDateTime comment "A subproperty of :beginsAt, allowing to address the beginning of an interval as a date/time".
- beginsAtDuration comment "A property enabling to adress a start time point P of an interval [P,E] through the duration of the interval [0,P] on a continuous timeline".
- beginsAtInt comment "A subproperty of :beginsAt, having xsd:int as a range".
- domainTimeLine comment "associates a timeline map to its domain timeline".
- duration comment "the duration of a time interval".
- durationInt comment "A subproperty of :duration, having xsd:int as a range".
- durationXSD comment "A subproperty of :duration, having xsd:duration as a range".
- end comment "refers to the end of a time interval, through an explicit datatype. time:hasEnd can be used as well, if you want to associate the end of the interval to an explicit time point resource".
- endsAtDateTime comment "A subproperty of :endsAt, allowing to address the end of an interval as a date/time".
- endsAtDuration comment "A property enabling to adress an end time point P of an interval [S,P] through the duration of the interval [0,P] on a continuous timeline".
- endsAtInt comment "A subproperty of :endsAt, having xsd:int as a range".
- hopSize comment "hop size, associated to a uniform windowing map".
- rangeTimeLine comment "associates a timeline map to its range timeline".
- sampleRate comment "associates a sample rate value to a uniform sampling map".
- start comment "refers to the beginning of a time interval, through an explicit datatype. time:hasBeginning can be used as well, if you want to associate the beginning of the interval to an explicit time point resource".
- timeline comment "\n\tRelates an interval or an instant to the timeline on which it is defined.\n\n\tThe 29th of August, 2007 would be linked through this property to the universal timeline, whereas\n\t\"from 2s to 5s on this particular signal\" would be defined on the signal' timeline.\n\n ".
- universaltimeline comment "this is the `universal' time line -- can adress time intervals on it using date/dateTime -- UTC".
- windowLength comment "window length, associated to a uniform windowing map".