@oimlsmart/primmel-packages 0.1.0

package/oiml-r91/terminology.prl

@@ -0,0 +1,535 @@
+term speed-meter {
+  label "speed meter"
+  definition "instrument that measures and displays the speed of a distant vehicle within specified error limits used for traffic enforcement cases"
+  vocab_ref { register viml-2022 clause "0.10" }
+  vocab_term "measuring instrument"
+  section "R 91-1, 3.1.1"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.1"
+}
+
+term evidence-file {
+  label "evidence file"
+  definition "electronic file containing all relevant data related to a speed measurement"
+  section "R 91-1, 3.1.2"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.2"
+}
+
+term standby-mode {
+  label "standby mode"
+  definition "mode of operation in which no speed measurements will be performed"
+  section "R 91-1, 3.1.3"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.3"
+}
+
+term enforcement-mode {
+  label "enforcement mode"
+  definition "mode of operation in which speed measurements for traffic enforcement cases are carried out"
+  section "R 91-1, 3.1.4"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.4"
+}
+
+term test-mode {
+  label "test mode"
+  definition "mode of operation in which speed measurements for test and examination purposes are carried out"
+  section "R 91-1, 3.1.5"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.5"
+}
+
+term user-interface {
+  label "user interface"
+  definition "interface that enables information to be interchanged between the user/operator and the measuring instrument or its components or modules"
+  section "R 91-1, 3.1.6"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.6"
+}
+
+term test-interface {
+  label "test interface"
+  definition "software or hardware interface from which measurement signals or data can be read or to which measurement signals can be inserted"
+  section "R 91-1, 3.1.7"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.7"
+}
+
+term checking-facility {
+  label "checking facility"
+  definition "facility incorporated in a measuring instrument to detect and react to significant faults or disturbances (OIML V 1, 5.07)"
+  vocab_ref { register viml-2022 clause "5.07" }
+  section "R 91-1, 3.1.8"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.8"
+}
+
+term manual-measurement {
+  label "manual measurement"
+  definition "speed measurement triggered by user interaction"
+  section "R 91-1, 3.1.9"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.9"
+}
+
+term automatic-measurement {
+  label "automatic measurement"
+  definition "speed measurement triggered by the traffic situation without user interaction"
+  section "R 91-1, 3.1.10"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.10"
+}
+
+term trigger-line {
+  label "trigger line"
+  definition "physical or virtual line segment on one or several lanes of the road at which automatic speed measurements are carried out"
+  section "R 91-1, 3.1.11"
+  note "The trigger line is typically perpendicular to the direction of the road. The trigger line is not necessarily in the same position for every measurement."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.11"
+}
+
+term trigger-distance {
+  label "trigger distance"
+  definition "horizontal distance along the road from the speed meter to the trigger line"
+  section "R 91-1, 3.1.12"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.12"
+}
+
+term measurement-section {
+  label "measurement section"
+  definition "straight or curved section of the road, where the measured vehicle was driving during the measurement"
+  section "R 91-1, 3.1.13"
+  note "Its starting and end points are defined such that the measured speed value refers to the average speed on the measurement section. In a manual measurement, the measured vehicle drives on the measurement section after the measurement is triggered; in an automatic measurement, the measured vehicle exits the measurement section at the trigger line."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.1.13"
+}
+
+term ego-speed {
+  label "ego speed"
+  definition "speed (relative to the road surface) of the speed meter during a measurement"
+  section "R 91-1, 3.2.1"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.2.1"
+}
+
+term ego-speed-meter {
+  label "ego speed meter"
+  definition "part of a moving speed meter measuring the speed of the patrol vehicle itself simultaneously with the target vehicle speed (R 91-1, 6.15.3)"
+  section "R 91-1, 6.15.3"
+  source "urn:oiml:pub:r:91-1:2025#clause-6.15.3"
+}
+
+term stationary-measurement {
+  label "stationary measurement"
+  definition "speed measurement at zero ego speed, i.e. the speed meter is not moving during the measurement"
+  section "R 91-1, 3.2.3"
+  note "In other documents, stationary measurements are sometimes called static measurements or measurements from a static point."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.2.3"
+}
+
+term stationary-speed-meter {
+  label "stationary speed meter"
+  definition "speed meter that is not moving during the measurements"
+  section "R 91-1, 5.1"
+  source "urn:oiml:pub:r:91-1:2025#clause-5"
+}
+
+term moving-speed-meter {
+  label "moving speed meter"
+  definition "speed meter installed on a vehicle which is moving during the measurements"
+  section "R 91-1, 5.1"
+  source "urn:oiml:pub:r:91-1:2025#clause-5"
+}
+
+term moving-measurement {
+  label "moving measurement"
+  definition "speed measurement using a moving speed meter with non-zero ego speed"
+  section "R 91-1, 3.2.6"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.2.6"
+}
+
+term mobile-speed-meter {
+  label "mobile speed meter"
+  definition "stationary speed meter which can be moved to different locations between measurements"
+  section "R 91-1, 3.2.7"
+  note "Stationary speed meters installed in a parked vehicle or on a parked trailer are also considered as mobile speed meters. Portable speed meters which are used hand-held or which are (temporarily) installed on a tripod or similar temporary stand to guide the hand of the operator for a limited series of measurements are also considered as mobile speed meters."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.2.7"
+}
+
+term fixed-speed-meter {
+  label "fixed speed meter"
+  definition "stationary speed meter, permanently installed in a cabinet, on a fixed pole or a similar fixed stand"
+  section "R 91-1, 3.2.8"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.2.8"
+}
+
+term doppler-radar-speed-meter {
+  label "Doppler-radar based speed meter"
+  definition "speed meter emitting microwave radiation and detecting the Doppler shift of the radiation reflected by moving objects"
+  section "R 91-1, 3.3.1"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.1"
+}
+
+term range-finding-speed-meter {
+  label "range-finding based speed meter"
+  definition "speed meter emitting pulsed or modulated radiation and detecting the range (distance) from the radiation reflected by objects"
+  section "R 91-1, 3.3.2"
+  note "2D and 3D laser scanners and hand-held LIDAR speed meters are examples belonging to this category. LIDAR (Light Detection and Ranging) is a remote sensing method that determines target range and speed based on the time-of-flight of laser light pulses reflected off a target."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.2"
+}
+
+term fixed-distance-speed-meter {
+  label "fixed-distance speed meter"
+  definition "speed meter incorporating two or more detection points at fixed distances and detecting the transit time of the vehicles between the detection points"
+  section "R 91-1, 3.3.3"
+  note "Laser or light barriers, inductive loop detectors, and pressure-sensitive barriers are examples belonging to this category."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.3"
+}
+
+term average-speed-meter {
+  label "average speed meter"
+  definition "fixed-distance speed meter with closest detection fields separated by more than 50 m"
+  section "R 91-1, 3.3.4"
+  note "Average speed meters are also referred to as section speed meters."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.4"
+}
+
+term image-based-speed-meter {
+  label "image-based speed meter"
+  definition "speed meter incorporating one or more video or photo cameras and determining the speed of the vehicles by image processing"
+  section "R 91-1, 3.3.5"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.5"
+}
+
+term beam-width {
+  label "beam width"
+  definition "angular span of a radiation beam in the horizontal plane"
+  section "R 91-1, 3.3.6"
+  note "The angular span of a radiation beam in the vertical plane is referred to as vertical beam width. The beam width of a Doppler-radar based speed meter is commonly measured between half-maximum-power points (or -3 dB points) on each side of the main lobe. Beam widths can be expressed in angles or metres (at a specified distance); angles are typically given in degrees (e.g. for Doppler-radar based speed meters) or in milliradians (mrad; e.g. for hand-held LIDAR speed meters)."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.6"
+}
+
+term fixed-beam {
+  label "fixed beam"
+  definition "radiation beam emitted in a fixed angle from the speed meter"
+  section "R 91-1, 3.3.7"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.7"
+}
+
+term scanning-beam {
+  label "scanning beam"
+  definition "radiation beam emitted in a periodically changing angle from the speed meter"
+  section "R 91-1, 3.3.8"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.8"
+}
+
+term detection-point {
+  label "detection point"
+  definition "point on the road at which passing vehicles are detected"
+  section "R 91-1, 3.3.9"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.9"
+}
+
+term detection-field {
+  label "detection field"
+  definition "field within which correct vehicle identification is certain (R 91-1, 6.6)"
+  section "R 91-1, 6.6"
+  source "urn:oiml:pub:r:91-1:2025#clause-6.6"
+}
+
+term section-distance {
+  label "section distance"
+  definition "closest driving distance between entry and exit detection fields of fixed-distance speed meters"
+  section "R 91-1, 3.3.11"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.11"
+}
+
+term hash-algorithm {
+  label "hash algorithm"
+  definition "function that converts a data string into a numeric string output of fixed length"
+  section "R 91-1, 3.3.12"
+  note "Hash algorithms are designed to be collision-resistant, meaning that there is a very low probability that the same string would be created for different data. Hash algorithms are used for software identification, authentication of measurements, protection of settings etc. Typical hash algorithms are SHA-2 (256-bit hash) or stronger."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.3.12"
+}
+
+term centre-line {
+  label "centre line"
+  definition "line starting from the speed meter lying in the centre of the region monitored by the speed meter (see Figure 2)"
+  section "R 91-1, 3.4.1"
+  note "For a speed meter with a fixed beam, the centre line is in the centre of the beam. For a speed meter with a scanning beam, the centre line is in the centre of the scanning region."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.1"
+}
+
+term reference-point {
+  label "reference point"
+  definition "point on the housing of the speed meter which serves as a reference for all distance measurements to the speed meter (see Figure 2)"
+  section "R 91-1, 3.4.2"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.2"
+}
+
+term azimuth-angle {
+  label "azimuth angle of speed meter"
+  definition "horizontal angle between the course of the road and the centre line of the speed meter (see Figure 2)"
+  section "R 91-1, 3.4.3"
+  note "In other documents, the azimuth angle of speed meter is sometimes called the horizontal alignment angle."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.3"
+}
+
+term elevation-angle {
+  label "elevation angle of speed meter"
+  definition "vertical angle between the road surface and the centre line of the speed meter (see Figure 2)"
+  section "R 91-1, 3.4.4"
+  note "In other documents, the elevation angle of speed meter is sometimes called the vertical alignment angle."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.4"
+}
+
+term side-distance {
+  label "side distance of speed meter"
+  definition "horizontal distance from the reference point of the speed meter to the closest edge of the closest lane (see Figure 2; inner edge of the lane marking)"
+  section "R 91-1, 3.4.5"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.5"
+}
+
+term height-of-speed-meter {
+  label "height of speed meter"
+  definition "vertical distance from the reference point of the speed meter to the road surface"
+  section "R 91-1, 3.4.6"
+  note "The centre line does not necessarily start from the reference point. The position of the reference point is determined by the manufacturer."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.6"
+}
+
+term measurement-angle {
+  label "measurement angle"
+  definition "angle between the velocity vector and the line connecting the speed meter and the vehicle at the instance of the measurement"
+  section "R 91-1, 3.4.7"
+  note "The measurement angle has a horizontal and a vertical component."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.7"
+}
+
+term angle-measurement {
+  label "angle measurement"
+  definition "measurement of the horizontal component of the measurement angle"
+  section "R 91-1, 3.4.8"
+  note "The measurement of the vertical component of the measurement angle is referred to as vertical angle measurement."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.8"
+}
+
+term cosine-error {
+  label "cosine error"
+  definition "measurement error due to a measurement angle which differs from the configured value, the nominal value or the value measured by the instrument"
+  section "R 91-1, 3.4.9"
+  note "The name of this term comes from the fact that the component of the velocity vector parallel to the line connecting the speed meter and the vehicle is given by v_m = v·cos(α), where the measurement angle α has in general a horizontal and a vertical component."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.9"
+}
+
+term along-the-road-speed-meter {
+  label "along-the-road speed meter"
+  definition "speed meter without compensation for cosine error"
+  section "R 91-1, 3.4.10"
+  note "A variation of measurement angle will always lead to negative cosine errors (i.e. in favour of the accused driver) for this class of speed meters. Typical examples are hand-held LIDAR speed meters and fixed-distance speed meters."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.10"
+}
+
+term across-the-road-speed-meter {
+  label "across-the-road speed meter"
+  definition "speed meter with compensation for cosine error using either a measured value of the measurement angle, a configured value of the expected measurement angle or a combination of the two"
+  section "R 91-1, 3.4.11"
+  note "A variation of measurement angle can lead to negative or positive residual cosine errors for this class of speed meters. A speed meter that is installed above the road and compensates for cosine error is also referred to as across-the-road speed meter, for simplicity. Typical examples are most Doppler-radar based speed meters, 2D and 3D laser scanners and image-based speed meters."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.11"
+}
+
+term aiming-device {
+  label "aiming device"
+  definition "device to orient the speed meter such that the azimuth and/or elevation are correct"
+  section "R 91-1, 3.4.12"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.12"
+}
+
+term vehicle-shape-related-error {
+  label "vehicle shape-related error"
+  definition "measurement error due to changing target area on the measured vehicle during the measurement"
+  section "R 91-1, 3.4.13"
+  note "The change can be manifold, e.g. a single step, multiple steps, or a gradual sliding."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.13"
+}
+
+term target-switching {
+  label "target switching"
+  definition "switching of the target from one vehicle to a different vehicle during the measurement"
+  section "R 91-1, 3.4.14"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.14"
+}
+
+term magnifying-viewfinder {
+  label "magnifying viewfinder"
+  definition "visual aid to magnify a target by a specified factor and to aim the measurement beam at the target"
+  section "R 91-1, 3.4.15"
+  note "It is to be used with handheld speed meters."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.4.15"
+}
+
+term error-of-indication {
+  label "error of indication / measurement error"
+  definition "indication minus a reference quantity value"
+  vocab_ref { register viml-2022 clause "0.04" }
+  vocab_term "error of indication"
+  section "R 91-1, 3.5.1"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.1"
+}
+
+term mpe {
+  label "maximum permissible error (MPE)"
+  definition "extreme value of error of indication, with respect to a known reference quantity value, permitted by specifications or regulations for a given measurement, measuring instrument, or measuring system"
+  vocab_ref { register viml-2022 clause "0.05" }
+  vocab_term "maximum permissible measurement error"
+  section "R 91-1, 3.5.2"
+  note "The unit of the error of indication and of the MPE can be either absolute (e.g. km/h) or relative (e.g. %). Error values in relative units given in this Recommendation are always relative to the absolute value of the reference (not to the value of the device under test or to any other value)."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.2"
+}
+
+term intrinsic-error {
+  label "intrinsic error"
+  definition "error of indication, determined under reference conditions"
+  vocab_ref { register viml-2022 clause "0.06" }
+  section "R 91-1, 3.5.3"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.3"
+}
+
+term initial-intrinsic-error {
+  label "initial intrinsic error"
+  definition "intrinsic error of a measuring instrument as determined prior to performance tests and durability evaluations"
+  vocab_ref { register viml-2022 clause "5.11" }
+  section "R 91-1, 3.5.4"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.4"
+}
+
+term durability-error {
+  label "durability error"
+  definition "difference between the intrinsic error after a period of use and the initial intrinsic error of a measuring instrument"
+  vocab_ref { register viml-2022 clause "5.16" }
+  section "R 91-1, 3.5.5"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.5"
+}
+
+term fault {
+  label "fault"
+  definition "difference between the error of indication and the intrinsic error of a measuring instrument"
+  vocab_ref { register viml-2022 clause "5.12" }
+  section "R 91-1, 3.5.6"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.6"
+}
+
+term influence-quantity {
+  label "influence quantity"
+  definition "quantity that does not affect the measurand itself but affects the relation between indication and measurement result (VIM 2.52)"
+  vocab_ref { register vim-2012 clause "2.52" }
+  section "R 91-1, 6.9"
+  source "urn:oiml:pub:r:91-1:2025#clause-6.9"
+}
+
+term influence-factor {
+  label "influence factor"
+  definition "influence quantity having a value which ranges within the rated operating conditions of a measuring instrument"
+  vocab_ref { register viml-2022 clause "5.18" }
+  section "R 91-1, 3.5.8"
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.8"
+}
+
+term disturbance {
+  label "disturbance"
+  definition "influence quantity having a value within the limits specified in Part 2 of this Recommendation, but outside the specified rated operating conditions of the measuring instrument"
+  vocab_ref { register viml-2022 clause "5.19" }
+  section "R 91-1, 3.5.9"
+  note "An influence quantity is a disturbance if the rated operating conditions for that influence quantity are not specified."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.9"
+}
+
+term significant-fault {
+  label "significant fault"
+  definition "fault exceeding the applicable fault limit value defined in clause 6.18.1"
+  vocab_ref { register viml-2022 clause "5.14" }
+  section "R 91-1, 3.5.10"
+  note "See supplements in clause 6.18.2."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.10"
+}
+
+term linearity-error {
+  label "linearity error"
+  definition "observed error in a measurement where all influence quantities have been minimized"
+  section "R 91-1, 3.5.11"
+  note "Typically, the linearity error is determined using a simulator in the laboratory."
+  source "urn:oiml:pub:r:91-1:2025#clause-3.5.11"
+}
+
+term linearity-error-limit {
+  label "linearity error limit"
+  definition "error limit applying for stationary measurements with influence quantities minimized or one isolated factor examined (R 91-1, 6.5)"
+  section "R 91-1, 6.5"
+  source "urn:oiml:pub:r:91-1:2025#clause-6.5"
+}
+
+term fault-limit {
+  label "fault limit value"
+  definition "limit of fault applying during influence factor and disturbance tests (R 91-1, 6.18.1)"
+  section "R 91-1, 6.18.1"
+  source "urn:oiml:pub:r:91-1:2025#clause-6.18.1"
+}
+
+term traffic-simulator {
+  label "traffic simulator"
+  definition "device simulating vehicle movement for laboratory speed tests (R 91-2, 5.2)"
+  section "R 91-2, 5.2"
+  source "urn:oiml:pub:r:91-2:2025#clause-5.2"
+}
+
+term reference-speed-meter {
+  label "reference speed meter"
+  definition "speed meter or simulator providing the reference measured speed v_ref for metrological controls (R 91-1, 6.3; R 91-2, 4.5)"
+  section "R 91-2, 4.5"
+  source "urn:oiml:pub:r:91-2:2025#clause-4.5"
+}
+
+term verification {
+  label "verification of a measuring instrument"
+  definition "conformity assessment procedure (other than type evaluation) which results in the affixing of a verification mark and/or issuing of a verification certificate"
+  vocab_ref { register viml-2022 clause "2.09" }
+  section "VIML 2.09"
+  source "urn:oiml:pub:v:1:2022#clause-2.09"
+}
+
+term initial-verification {
+  label "initial verification"
+  definition "verification of a measuring instrument which has not been verified previously"
+  vocab_ref { register viml-2022 clause "2.12" }
+  section "VIML 2.12"
+  source "urn:oiml:pub:v:1:2022#clause-2.12"
+}
+
+term subsequent-verification {
+  label "subsequent verification"
+  definition "verification of a measuring instrument after a previous verification"
+  vocab_ref { register viml-2022 clause "2.13" }
+  section "VIML 2.13"
+  source "urn:oiml:pub:v:1:2022#clause-2.13"
+}
+
+term periodic-verification {
+  label "mandatory periodic verification"
+  definition "subsequent verification of a measuring instrument, carried out periodically at specified intervals according to the procedure laid down by the regulations"
+  vocab_ref { register viml-2022 clause "2.14" }
+  section "VIML 2.14"
+  source "urn:oiml:pub:v:1:2022#clause-2.14"
+}
+
+term verification-certificate {
+  label "verification certificate"
+  definition "document certifying that the verification of the measuring instrument was carried out and compliance with statutory requirements was confirmed"
+  vocab_ref { register viml-2022 clause "3.02" }
+  section "VIML 3.02"
+  source "urn:oiml:pub:v:1:2022#clause-3.02"
+}
+
+term verification-mark {
+  label "verification mark"
+  definition "mark applied to a measuring instrument in a conspicuous manner certifying that the verification of the measuring instrument was carried out and compliance with statutory requirements was confirmed"
+  vocab_ref { register viml-2022 clause "3.04" }
+  section "VIML 3.04"
+  source "urn:oiml:pub:v:1:2022#clause-3.04"
+}
+
+term in-service-inspection {
+  label "in-service inspection"
+  definition "metrological control carried out in accordance with the same requirements as for initial verification, except that the in-service MPE according to national regulations applies (R 91-1, 8.4)"
+  section "R 91-1, 8.4"
+  source "urn:oiml:pub:r:91-1:2025#clause-8.4"
+}
+

package/oiml-r91/value-types.prl

@@ -0,0 +1,26 @@
+quantity_register r91 {
+  kind length { dimensions { L 1 } si_unit "m" }
+  kind voltage { dimensions { I -1 L 2 M 1 T -3 } si_unit "V" }
+  kind frequency { dimensions { T -1 } si_unit "Hz" }
+  kind power { dimensions { L 2 M 1 T -3 } si_unit "W" }
+  kind electric-field-strength { dimensions { I -1 L 1 M 1 T -3 } si_unit "V/m" }
+  kind acceleration { dimensions { L 1 T -2 } si_unit "m/s²" }
+  kind temperature { dimensions { Θ 1 } si_unit "K" }
+  kind angle { si_unit "rad" }
+  kind speed { dimensions { L 1 T -1 } si_unit "m/s" }
+  kind ratio { si_unit "1" }
+  kind dimensionless { si_unit "1" }
+  unit m { symbol "m" label "metre" kind length }
+  unit nm { symbol "nm" label "nanometre" kind length factor 1e-9 }
+  unit V { symbol "V" label "volt" kind voltage definition "W/A" }
+  unit Hz { symbol "Hz" label "hertz" kind frequency definition "1/s" }
+  unit GHz { symbol "GHz" label "gigahertz" kind frequency factor 1000000000 }
+  unit mW { symbol "mW" label "milliwatt" kind power factor 0.001 }
+  unit V/m { symbol "V/m" label "volt per metre" kind electric-field-strength }
+  unit mps2 { symbol "m/s²" label "metre per second squared" kind acceleration }
+  unit degC { symbol "°C" label "degree Celsius" kind temperature offset 273.15 }
+  unit deg { symbol "°" label "degree" kind angle factor 0.0174533 }
+  unit kmh { symbol "km/h" label "kilometres per hour" kind speed factor 0.277778 }
+  unit % { symbol "%" label "percent" kind ratio factor 0.01 }
+  unit dimensionless { label "dimensionless" kind dimensionless }
+}

package/oiml-smart-core/entities/comments.prl

@@ -0,0 +1,101 @@
+class ReportCommentThread#data {
+  store { reportCommentThreads }
+  description { "The review-period comment thread on one report — a TestReport or the EvaluationReport (the demo-flows program's flow 04, step 4: at every report's finalization the Evaluation Project's participants may comment; the IA owns the project, the applicant views per the viewing cone, the TL joins on the accepted assignment). A thread anchors on the report as a whole or on one section/row, carries the OPEN/RESOLVED state, and resolves before the report's finalization completes — the report machines gate the final decision on consultation_resolved (evaluation/state-machines.prl), and the completion gate refuses while any thread stays OPEN (specification/constraints.prl, the settling doctrine). Who may read and post is the project cones' call, realized by the platform (the server-side cone enforcement), never restated here." }
+  indexes { report_kind test_report_id evaluation_report_id application_id status }
+  id: string {
+    modality SHALL
+  }
+  report_kind: enum {
+    modality SHALL
+    definition "Which report the thread rides: a TestReport or the EvaluationReport — exactly the matching reference field is set"
+    enum_values { test_report evaluation_report }
+  }
+  test_report_id: reference(TestReport) [0..1] {
+    modality MAY
+    definition "The TestReport under consultation (set when report_kind = test_report)"
+    on_delete cascade
+    required false
+  }
+  evaluation_report_id: reference(EvaluationReport) [0..1] {
+    modality MAY
+    definition "The EvaluationReport under consultation (set when report_kind = evaluation_report)"
+    on_delete cascade
+    required false
+  }
+  application_id: reference(Application) [0..1] {
+    modality MAY
+    definition "The Evaluation Project the thread belongs to (denormalized from the subject report for the project's thread listing)"
+    on_delete cascade
+    required false
+  }
+  anchor: string [0..1] {
+    modality MAY
+    definition "The report section or row the thread anchors on (a form id, a report-format clause, a field path); absent anchors the report as a whole"
+  }
+  status: enum {
+    modality SHALL
+    definition "OPEN while the discussion stands; RESOLVED when the parties settle it (the resolution-before-finalization gate keys on this state). The thread's rows are never edited — a resolved thread stays on the record"
+    enum_values { OPEN RESOLVED }
+  }
+  opened_by: string {
+    modality SHALL
+    definition "The account name of the participant who opened the thread (audit provenance)"
+  }
+  opened_by_org: string [0..1] {
+    modality MAY
+    definition "The participant organization the opener acted for (the project cone's org id — applicant, IA or TL)"
+  }
+  opened_at: datetime {
+    modality SHALL
+  }
+  resolved_by: string [0..1] {
+    modality MAY
+  }
+  resolved_at: datetime [0..1] {
+    modality MAY
+  }
+  resolution_note: text [0..1] {
+    modality MAY
+    definition "How the thread settled (the resolver's one-line record — e.g. the report row corrected, the question answered)"
+  }
+  created: datetime {
+    modality SHALL
+  }
+  modified: datetime {
+    modality SHALL
+  }
+}
+
+class ReportComment#data {
+  store { reportComments }
+  description { "One comment row inside a ReportCommentThread (the review period, the demo-flows program's flow 04): the author, the author's participant organization, the body and the timestamps. Rows append and never rewrite (the evidence-accrues doctrine); the thread carries the resolved state. The participants who may post are the Evaluation Project's parties per the project's cones (the IA, the applicant viewing, the joined TL — the scheme's oversight per the cone machinery), realized by the platform's server-side enforcement." }
+  indexes { thread_id author_org }
+  id: string {
+    modality SHALL
+  }
+  thread_id: reference(ReportCommentThread) {
+    modality SHALL
+    definition "The thread this row appends to"
+    on_delete cascade
+    required true
+  }
+  author: string {
+    modality SHALL
+    definition "The account name of the comment's author (audit provenance)"
+  }
+  author_org: string [0..1] {
+    modality MAY
+    definition "The participant organization the author acted for (the project cone's org id), stamped at posting"
+  }
+  body: text {
+    modality SHALL
+    definition "The comment text"
+  }
+  created: datetime {
+    modality SHALL
+  }
+  modified: datetime {
+    modality SHALL
+  }
+}
+