Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- Question_for_indicating comment "A question demanding indication of some concept, thing or its property in order to be anwsered.\n\nExamples: What's your date of birth? What is the name of the Director of the W3C?".
- basic comment "An OWL representation of (some of) the basic types described in ISO 19103:2005, required as primitives in other ontologies based on ISO 19100 series standards. \n\nThis vocabulary is provisional, pending finalization of ISO 19150-2.\n\nThe URI stem http://def.seegrid.csiro.au/isotc211/ is temporary. The vocabulary is expected to be ultimately published in the domain http://def.isotc211.org/".
- Acceleration comment "Measure of rate of change of velocity".
- Angle comment "measure of arc length or rotation".
- AngularVelocity comment "Measure of rate of change of angular position".
- Area comment "Measure of 2-D extent".
- Boolean comment "Truth value. Most valuable in the predicate calculus, where items are either True or False, unless they are ill formed.".
- CharacterString comment "sequence of characters".
- Currency comment "Measure of exchange value".
- Date comment "Temporal position expressed with precision of days".
- DateTime comment "Temporal position expressed as a time and date".
- Decimal comment "The usually finite representation of a decimal number. It differs from the common binary Real implementation in that it can represent 1/10 (one-tenth) without error, while binary real representation can only represent powers of 1/2 (one-half) exactly. Since many currencies are decimal, these representations are preferred in dealing with such moneys. This is also true for mile markers, which are often given in decimals.\n\nCan be thought of as an integer part followed by a fractional part given in multiples of powers of 1/10 (tenths).".
- Distance comment "Measure of spatial separation along some 1-D manifold".
- Integer comment "An exact integer value, with no fractional part. ".
- Length comment "Measure of 1-D extent".
- LocalName comment "Name in some local context".
- Mass comment "Measure of amount of substance".
- Measure comment "Scaled number".
- Number comment "Note: integer is a specialization of decimal".
- Number comment "The set of numbers".
- Real comment "The common binary Real finite implementation using base 2. Since such reals can approximate any measure where absolute accuracy is not possible, this form of numeric is most often used for measures. In cases were absolute accuracy is needed, such as currencies, then a decimal representation may be preferred (assuming the currency is decimal, such as the US dollar, British pound, etc.). Where there are no subunits possible, Integer numbers may be preferred. \n\nCan be thought of as an integer part followed by a fractional part given in multiples of powers of 1/2 (halves).".
- Scale comment "Factor by which a representation should be magnified to match the geomstric size of the thing it represents.".
- Time comment "Measure of temporal extent".
- UnitOfMeasure comment "Scale for a number describing size or extent".
- Vector comment "A vector is a sequence of a fixed length of Numbers. Normally, the numbers represent some measures, and thus vectors are often used where records of Numbers would be more appropriate. In geometry for example, direct positions are given by undistinguished coordinate vectors, which can be interpreted through the use of coordinate reference systems.".
- Velocity comment "Measure of rate of change of position".
- Volume comment "Measure of 3-D extent".
- Weight comment "Measure of force due to a mass in a specific gravitational field".
- dimension comment "Number of components in the vector".
- measure comment "The value of this property is a scaled number".
- ordinates comment "Numerical values of the vector components".
- uom comment "The value of this property designates the units of measure or scale for the quantity".
- value comment "The value of this property is a number".
- geometry comment "An OWL representation of part of the model for geometry and space from ISO 19107:2003 Geographic Information - Spatial Schema. \n\nThis vocabulary is provisional, pending finalization of ISO 19150-2.\n\nThe URI stem http://def.seegrid.csiro.au/isotc211/ is temporary. The vocabulary is expected to be ultimately published in the domain http://def.isotc211.org/. ".
- Complex comment "geometric complex\nset of disjoint geometric primitives such that the boundary of each primitive can be represented as the union of other geometric primitives within the complex\n\nNOTE: The geometric primitives in the set are mutually exclusive in the sense that no point is interior to more than one primitive. The set is closed under boundary operations, meaning that for each element in the complex, there is a collection (also a complex) of geometric primitives that represents the boundary of that element.".
- Envelope comment "GM_Envelope is often referred to as a minimum bounding box or rectangle. Regardless of dimension, a GM_Envelope can be represented without ambiguity as two direct positions (coordinate points). To encode a GM_Envelope, it is sufficient to encode these two points. This is consistent with all of the data types in this standard, their state is represented by their publicly accessible attributes. ".
- Object comment "GM_Object (Figure 6) is the root class of the geometric object taxonomy and supports interfaces common to all geographically referenced geometric objects. GM_Object instances are sets of direct positions in a particular coordinate reference system. A GM_Object can be regarded as an infinite set of points that satisfies the set operation interfaces for a set of direct positions, TransfiniteSet<DirectPosition>. Since an infinite collection class cannot be implemented directly, a Boolean test for inclusion shall be provided by the GM_Object interface. This international standard concentrates on vector geometry classes, but future work may use GM_Object as a root class without modification.\nNOTE As a type, GM_Object does not have a well-defined default state or value representation as a data type. Instantiated subclasses of GM_Object will.".
- Position comment "DirectPosition object data types (Figure 14) hold the coordinates for a position within some coordinate reference system. The coordinate reference system is described in ISO 19111. Since DirectPositions, as data types, will often be included in larger objects (such as GM_Objects) that have references to ISO19111::SC_CRS, the DirectPosition::cordinateReferenceSystem may be left NULL if this particular DirectPosition is included in a larger object with such a reference to a SC_CRS. In this case, the DirectPosition::coordinateReferenceSystem is implicitly assumed to take on the value of the containing object's SC_CRS. ".
- Primitive comment "GM_Primitive (Figure 8) is the abstract root class of the geometric primitives. Its main purpose is to define the basic \"boundary\" operation that ties the primitives in each dimension together. A geometric primitive (GM_Primitive) is a geometric object that is not decomposed further into other primitives in the system. This includes curves and surfaces, even though they are composed of curve segments and surface patches, respectively. This composition is a strong aggregation: curve segments and surface patches cannot exist outside the context of a primitive.\nNOTE Most geometric primitives are decomposable infinitely many times. Adding a centre point to a line may split that line into two separate lines. A new curve drawn across a surface may divide that surface into two parts, each of which is a surface. This is the reason that the normal definition of primitive as \"non-decomposable\" is not plausible in a geometry model - the only non-decomposable object in geometry is a point.\nAny geometric object that is used to describe a feature is a collection of geometric primitives. A collection of geometric primitives may or may not be a geometric complex. Geometric complexes have additional properties such as closure by boundary operations and mutually exclusive component parts.\nGM_Primitive and GM_Complex share most semantics, in the meaning of operations, attributes and associations. There is an exception in that a GM_Primitive shall not contain its boundary (except in the trivial case of GM_Point where the boundary is empty), while a GM_Complex shall contain its boundary in all cases. This means that if an instantiated object implements GM_Object operations both as GM_Primitive and as a GM_Complex, the semantics of each set theoretic operation is determined by the its name resolution. Specifically, for a particular object such as GM_CompositeCurve, GM_Primitive::contains (returns FALSE for end points) is different from GM_Complex::contains (returns TRUE for end points). Further, if that object is cast as a GM_Primitive value and as a GM_Complex value, then the two values need not be equal as GM_Objects.".
- temporal comment "An OWL representation of part of the model for Temporal objects and reference systems from ISO 19108:2002 Geographic Information - Temporal Schema\n\nThis vocabulary is provisional, pending finalization of ISO 19150-2.\n\nThe URI stem http://def.seegrid.csiro.au/isotc211/ is temporary. The vocabulary is expected to be ultimately published in the domain http://def.isotc211.org/".
- begin comment "The value of this property defines the beginning of a time period".
- dateTimePosition comment "The value of this property is a time encoded as an xsd:dateTime".
- end comment "The value of this property defines the end of a time period".
- frame comment "The value of this property indicates the temporal reference system for a time position".
- feature comment "An OWL representation of part of the General Feature Model described in ISO 19109 and the General Feature Instance model described in Annex C of ISO 19156:2011. \n\nThis vocabulary is provisional, pending finalization of ISO 19150-2.\n\nThe URI stem http://def.seegrid.csiro.au/isotc211/ is temporary. The vocabulary is expected to be ultimately published in the domain http://def.isotc211.org/".
- AnyFeature comment "In ISO 19156 the class GFI_Feature is defined as an instance of GF_FeatureType. In this OWL representation we do not have a specific class for GF_FeatureType because this would imply subclassing owl:Class which is inconsistent with OWL-DL restrictions.".
- dataquality comment "This version of the ontology uses # and /code/ patterns as agreed in ISO 19150-2 meeting in Toulouse, June 2012.".
- metadata comment "An OWL representation of parts of the Geographic Metadata model described in ISO 19115:2003 with Corrigendum 2006 - MD Package.\n\nThis vocabulary is provisional, pending finalization of ISO 19150-2.\n\nNOTE: The URI stem http://def.seegrid.csiro.au/isotc211/ is temporary. The vocabulary is expected to be ultimately published in the domain http://def.isotc211.org/".
- accessConstraints comment "Value should be chosen from <http://def.seegrid.csiro.au/isotc211/iso19115/2003/metadata/RestrictionCode>".
- axisDimensionProperties comment "Sequence members are md:Dimension".
- centerPoint comment "Sequence members are gm:Point".
- cornerPoints comment "Sequence members are GM_Point".
- initiativeType comment "Value should be chosen from <http://def.seegrid.csiro.au/isotc211/iso19115/2003/dataset/InitiativeTypeCode>".
- maintenanceAndUpdateFrequency comment "Value should be chosen from <http://def.seegrid.csiro.au/isotc211/iso19115/2003/metadata/MaintenanceFrequenceCode>".
- updateScope comment "Value should be chosen from <http://def.seegrid.csiro.au/isotc211/iso19115/2003/metadata/ScopeCode>".
- basic comment "This ontology establishes classes corresponding to stereotypes used in ISO-conformant models, as used in the rules for conversion of the ISO TC 211 Harmonized Model from the UML to OWL representations. \n\nThis vocabulary is provisional, pending finalization of ISO 19150-2.\n\nThe URI stem http://def.seegrid.csiro.au/isotc211/ is temporary. The vocabulary is expected to be ultimately published in the domain http://def.isotc211.org/ .".
- ISOClassName comment "A datatype for skos:notation annotations, used to indicate the original UML class name".
- TaggedValue comment "Class for UML tagged values".
- isAbstract comment "This property indicates whether the class was flagged 'abstract' in the UML model. Abstract classes cannot be instantiated directly. Concrete subclasses may be instantiated.".
- isStereotype comment "This property indicates if the class corresponds to a UML stereotype ".
- tag comment "OWL property that links to a tagged value".
- observation comment "An OWL representation of the Observation Schema described in clause 6 of ISO 19156:2011 Geographic Information - Observations and Measurements. \n\nThe rationale for design decisions made in this implementation, and a comparison with the SSN ontology, was presented in a paper at the 6th International Semantic Sensor Web workshop, Sydney, 2013-10-21.\n\nThis vocabulary is provisional, pending finalization of ISO 19150-2.\n\nNOTE: The URI stem http://def.seegrid.csiro.au/isotc211/ is temporary. The vocabulary is expected to be ultimately published in the domain http://def.isotc211.org/".
- CategoryObservation comment "Observation whose result is a classification from some vocabulary or taxonomy".
- ComplexObservation comment "Observation whose result is a vector, record, tuple or other complex value".
- CountObservation comment "Observation whose result is an integer".
- DiscreteCoverageObservation comment "Observation whose result is a discrete representation of a spatio-temporal field, including images and time-series".
- GeometryObservation comment "Observation whose result is a spatial object or geometry".
- Measurement comment "Observation whose result is a scaled number".
- NamedValue comment "Typed value".
- Observation comment "An observation is an act associated with a discrete time instant or period through which a number, term or other symbol is assigned to a phenomenon [2]. It involves application of a specified procedure, such as a sensor, instrument, algorithm or process chain. The procedure may be applied in-situ, remotely, or ex-situ with respect to the sampling location. The result of an observation is an estimate of the value of a property of some feature. Use of a common model allows observation data using different procedures to be combined unambiguously.\n\nThe observation itself is also a feature, since it has properties and identity.\n\nObservation details are important for data discovery and for data quality estimation.\n\nThe observation could be considered to carry “property-level” instance metadata, which complements the dataset-level and feature-level metadata that have been conventionally considered (e.g. ISO 19115).".
- Observation comment "Generic observation".
- ObservationContext comment "Context linking two or more observations".
- ObservationContext comment "Some observations depend on other observations to provide context which is important, sometimes essential, in understanding the result. These dependencies are stronger than mere spatio-temporal coincidences, requiring explicit representation. If present, the association class class ObservationContext (Figure 2) shall link a OM_Observation to another OM_Observation, with the role name relatedObservation for the target. It shall support one attribute.\n\nEXAMPLES\tSome examples include the conditions associated with experimental replicates (e.g., experimental plots and treatments used), biotic factors (e.g., ecological community), interactions among features (e.g., predator-prey), or other temporary relationships occurring at the time of observation that are are not inherent to the observed features themselves (i.e., they change over time), or the related observation may provide input to a process that generates a new result.\nThis association complements the Intention association which describes relationships between a sampling feature and domain features.".
- PointCoverageObservation comment "Observation whose result is a spatio-temporal field sampled at discete points".
- Process comment "Process used in an observation, including sensors, algorithms, computation methods".
- Process comment "The class OM_Process (Figure 2) is an instance of the «metaclass» GF_FeatureType (ISO 19109:2005), which therefore represents a feature type. OM_Process is abstract, and has no attributes, operations or associations. It serves as the base class for observation processes. The purpose of an observation process is to generate an observation result. An instance of OM_Process is often an instrument or sensor, but may be a human observer, a simulator, or a process or algorithm applied to more primitive results used as inputs. \n\nNOTE\tISO 19115-2:2008 provides MI_Instrument, LE_Processing and LE_Algorithm, which could all be modelled as specializations of OM_Process. OGC SensorML [10] provides a model which is suitable for many observation procedures.".
- TemporalObservation comment "Observation whose result is a temporal object, such as a time instant or period".
- TimeSeriesObservation comment "Observation whose result is a time-series".
- TruthObservation comment "Observation whose result is either true or false".
- featureOfInterest comment "feature of interest of an observation".
- metadata comment "generic metadata about an observation".
- name comment "key indicating the type of a named value".
- observationContext comment "This property is named 'relatedObservation' in the XML implementation. The rule for association classes needs clarification.".
- observationContext comment "link to related observation".
- observedProperty comment "property whose value is the result of the observation".
- parameter comment "observation-specific parameter not accommodated by the standard observation properties. Often used to record environmental parameters".
- phenomenonTime comment "time at which the estimate of the property that is the result of the observation is associated with the feature of interest".
- procedure comment "procedure used in making observation. Typically a sensor or sensor-system, algorithm, computational procedure.".
- relatedObservation comment "related observation".
- result comment "estimate of the value of the observed property".
- resultQuality comment "assessment of the quality of the observation result. The value should be specific to this observation instance, in addition to any quality that is inferred from the observation procedure used".
- resultTime comment "time at which the result became available, after all processing steps were completed".
- role comment "role of related observation with respect to the observation of interest".
- validTime comment "time during which the observation result is recommended for use. Most often used in relation to forecasts, but may be used any time the observation procedure (including inputs) is liable to modification. ".
- value comment "value of named value".
- sampling comment "An OWL representation of the Sampling Features Schema described in clauses 8-10 of ISO 19156:2011 Geographic Information - Observations and Measurements. \n\nThis vocabulary is provisional, pending finalization of ISO 19150-2.\n\nNOTE: The URI stem http://def.seegrid.csiro.au/isotc211/ is temporary. The vocabulary is expected to be ultimately published in the domain http://def.isotc211.org/".
- Location comment "Location, expressed as either a spatial object or geographic identifier".
- NotSamplingFeature comment "Complement of SamplingFeature".
- PreparationStep comment "Discrete stage in specimen-preparation process".
- PreparationStep comment "In many applications, specimen preparation procedures are applied to the material prior to its use in an observation. The class PreparationStep (Figure 13) shall link an SF_Specimen to an SF_Process that describes a phase of the specimen preparation.".