1 / 13

OBOE Model Changes

OBOE Model Changes. SONet Meeting June 7-9, 2010. Motivation for Changes. Remove redundancy in the model Mainly in Dimension (characteristics) Make it more “reasonable” Make better use of OWL constraints for inference Simplify How measured values are handled Context and relationships

fahim
Download Presentation

OBOE Model Changes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OBOE Model Changes SONet Meeting June 7-9, 2010

  2. Motivation for Changes Remove redundancy in the model • Mainly in Dimension (characteristics) Make it more “reasonable” • Make better use of OWL constraints for inference Simplify • How measured values are handled • Context and relationships More modeling flexibility • Allow observed relationships between entities

  3. Overview of OBOE 1.0 Beta hasContextRelationship Context Relationship 1..1 * * * * * hasContextObservation hasObservationContext hasRelationshipEntity hasEntityRelationship 1..1 1..1 1..1 1..1 ofEntity Observation Entity 1..1 * measurementFor 1..1 1..1 characteristicOf hasMeasurement * Measurement + hasPrecision : decimal + hasValue : anySimpleType CharacteristicValue ofCharacteristic 1..1 * * * usesProtocol hasCharacteristic 1..1 * 1..1 * Protocol Characteristic hasCharacteristicValue usesStandard 1..1 MeasurementStandard

  4. Proposed Changes (OBOE 1.1 Beta) contextFor hasContext * ofEntity observedBy * Observation Entity 1..1 * 1..1 measurementFor 1..1 hasValue hasMeasurement valueFor * Measurement * measuredBy ofCharacteristic + hasPrecision : decimal + hasMethod : anyType Characteristic * 1..1 protocolFor * standardFor * usesStandard usesProtocol 1..1 1..1 Protocol Standard

  5. Overview of OBOE 1.0 Beta Entity 1..1 (e.g., Shell) characteristicOf (e.g., DamagedValue) CharacteristicValue + hasCode : anySimpleType hasCharacteristic 1..1 * * Characteristic hasCharacteristicValue (e.g., Condition) • Entities can have (simple) characteristics • Similar to OWL data type properties • Length, Height, Mass, ... • Values have “valuecodes” • Implicit connection to data

  6. Proposed Changes (OBOE 1.1 Beta) • Remove Characteristic Value • Treat primitives as special entities (like in “pure” OOP) • Values as primitives, asserted types (punning), entities • Allow complex Characteristics • Data and object properties • Improved reasoning power • Characteristics and entities constrained through measurements

  7. Overview of OBOE 1.0 Beta hasContextRelationship Context Relationship 1..1 * * * * * hasEntityRelationship hasObservationContext hasRelationshipEntity hasContextObservation * 1..1 1..1 1..1 ofEntity Observation Entity 1..1 • Observations are made within a context • The “environment” or “state” assumed to be present during an observation • Observations related via a Relationship (like part-of, within, etc.)

  8. Proposed Changes (OBOE 1.1 Beta) • Removed context relationships • Replaced by more powerful characteristics (entity-entity) • But, retains same meaning of context • Simplified context representation • Now just an object property (hasContext)

  9. Other Proposed Changes (OBOE 1.1 Beta) • Added inverse properties • This gives many “access paths” through the ontology … which is useful for reasoning (constraints) • For example, can fully constrain a WingCount characteristic to have integer values and be of Birds within a Measurement: WingCountmeasuredBy only (Measurement and (hasValue only int) and (measurementFor only Bird)) • Removed dimension structure from characteristic • Now just a plain-old hierarchy • Units still retain the structure (with small changes) • Characteristic constrained through measurements (like above)

  10. Overview of OBOE 1.0 Beta Characteristic MeasurementStandard Dimension Unit forCharacteristic BaseDimension BaseUnit + hasPower = 1 + hasPower = 1 1..1 1..1 hasBaseDimension hasBaseUnit * * forCharacteristic SimpleDerivedDimension SimpleDerivedUnit + hasPower = int U + hasPower = int U 2..* 2..* hasUnit hasDimension forCharacteristic ComplexDerivedDimension ComplexDerivedUnit * * Note: Implicit constraints that must be enforced by the application (i.e., not by a reasoner)

  11. Proposed Changes (OBOE 1.1 Beta) Characteristic MeasurementStandard standardForohasCharacteristic PhysicalCharacteristic Unit Characteristics can be used over a variety of units and standards … no restriction on structuring Enables many “surrogates” for a characteristic (like density …) BaseUnit 1..1 hasUnit * DerivedUnit + hasPower = int U 2..* hasUnit CompositeUnit *

  12. Proposed Changes for 1.1 Beta • Modularization oboe-core … the basic structures • Entity, Observation, Characteristic, Protocol, Standard, Measurement oboe … the next level of detail • Entity (Primitive) Values • Characteristics: PhysicalCharacteristic, QualifiedCharacteristic, Name, Type • Unit structure: BaseUnit, DerivedUnit, CompositeUnit, UnitConversion oboe-unit … common units & characteristics • Physical characteristics (dimensions), conversions, etc.

  13. Comparison of OBOE to O&M Characteristic Context* ObservationCollection ObservationContext Time Context memberOf + role samplingTime member observationLocation relatedObservation Location Observation Observation + Measurement Context* result procedure featureOfInterest observedProperty Feature PropertyType ResultData Process Protocol Entity Characteristic Measurement Value Highly overlapping models …

More Related