Observable: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Observable definition here... What characterizes... ==List of Observables== Identifier") |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Observable | Observable are a list of (mostly) distinct concepts that may be used in a data model to build [[entities|entity]] and [[association]]s. | ||
An Observable is characterized by three things: | |||
# GUID - the Globally Unique IDentifier is a critical part of the definition. Although this is the true identity of the Observable, this form of information is not terribly useful to a human user. | |||
# Name - this is the label that helps a user understand what the observable is intended to represent | |||
# Description - the name is not always sufficient so the description provides amplifying information to further clarify what the observable is intended to represent. | |||
==Single Observable Modeling== | |||
<blockquote> | |||
Single Observable Modeling is when the SDM, a DSDM, or a USM is developed to follow the Single Observable Constraint in Section J.7.1. The Single Observable Constraint limits Conceptual Entities to composing at most one element of a single Observable type. Models that follow the Single Observable Constraint provide a clearer understanding of Entities by reducing the likelihood of semantic information being embedded in the multiple composition of Observables. This is considered a data modeling best practice. | |||
</blockquote> | |||
==List of Observables== | ==List of Observables== | ||
[[AbsorbedDoseRate]] | |||
[[AbsorbedDose]] | |||
[[Acceleration]] | |||
[[AmountOfSubstance]] | |||
[[Angle]] | |||
[[AngularAcceleration]] | |||
[[AngularJerk]] | |||
[[AngularVelocity]] | |||
[[Audio]] | |||
[[Bias]] | |||
[[CalendarTime]] | |||
[[ChemicalConcentration]] | |||
[[Color]] | |||
[[ConfigurationState]] | |||
[[Count]] | |||
[[CountRate]] | |||
[[DataRate]] | |||
[[Density]] | |||
[[Description]] | |||
[[Distance]] | |||
[[DoseEquivalent]] | |||
[[Duration]] | |||
[[DynamicViscosity]] | |||
[[Efficiency]] | |||
[[ElectricCapacitance]] | |||
[[ElectricChargeDensity]] | |||
[[ElectricCharge]] | |||
[[ElectricCurrentDensity]] | |||
[[ElectricCurrent]] | |||
[[ElectricField]] | |||
[[ElectricPotential]] | |||
[[ElectricResistance]] | |||
[[Energy]] | |||
[[Extent]] | |||
[[Force]] | |||
[[Gain]] | |||
[[GraphicsState]] | |||
[[HealthState]] | |||
[[Humidity]] | |||
[[Identifier]] | [[Identifier]] | ||
[[Illuminance]] | |||
[[Image]] | |||
[[IndexOfRefraction]] | |||
[[Irradiance]] | |||
[[Jerk]] | |||
[[Kind]] | |||
[[KinematicViscosity]] | |||
[[LuminousIntensity]] | |||
[[MassFlowRate]] | |||
[[Mass]] | |||
[[Metric]] | |||
[[Mode]] | |||
[[Name]] | |||
[[NonPhysicalAddress]] | |||
[[OperationalState]] | |||
[[Order]] | |||
[[OrientationAcceleration]] | |||
[[OrientationJerk]] | |||
[[OrientationVelocity]] | |||
[[Orientation]] | |||
[[Polarization]] | |||
[[Position]] | |||
[[Power]] | |||
[[Pressure]] | |||
[[Probability]] | |||
[[RadiantIntensity]] | |||
[[Ratio]] | |||
[[Resolution]] | |||
[[ScalarAcceleration]] | |||
[[ScalarArea]] | |||
[[ScalarJerk]] | |||
[[ScalarVolume]] | |||
[[Sensitivity]] | |||
[[Size]] | |||
[[Speed]] | |||
[[TemperatureDelta]] | |||
[[Temperature]] | |||
[[TemporalFrequency]] | |||
[[TimeOfDay]] | |||
[[Torque]] | |||
[[Uncertainty]] | |||
[[UniqueIdentifier]] | |||
[[ValidityState]] | |||
[[Velocity]] | |||
[[Video]] | |||
Latest revision as of 07:25, 12 August 2022
Observable are a list of (mostly) distinct concepts that may be used in a data model to build entity and associations.
An Observable is characterized by three things:
- GUID - the Globally Unique IDentifier is a critical part of the definition. Although this is the true identity of the Observable, this form of information is not terribly useful to a human user.
- Name - this is the label that helps a user understand what the observable is intended to represent
- Description - the name is not always sufficient so the description provides amplifying information to further clarify what the observable is intended to represent.
Single Observable Modeling
Single Observable Modeling is when the SDM, a DSDM, or a USM is developed to follow the Single Observable Constraint in Section J.7.1. The Single Observable Constraint limits Conceptual Entities to composing at most one element of a single Observable type. Models that follow the Single Observable Constraint provide a clearer understanding of Entities by reducing the likelihood of semantic information being embedded in the multiple composition of Observables. This is considered a data modeling best practice.