Observation

Perception new in 2.0 since 2.0 aow:Observation

An interpreted fact about a Work Item, Actor, or Action, derived from one or more Signals and carrying a Confidence.

Separates recorded evidence (Signal) from its interpretation (Observation), so an incorrect interpretation can be identified and corrected.

Attributes

Attribute	Type	Required	Description
`observed_property`	string	yes	What was observed, for example "claim_amount" or "handling_time".
`observed_value`	json		The observed value, in any JSON form.
`observed_at`	datetime		When the observation was made.
`method`	string		How the value was derived, for example "document-extraction" or "rule".

Every entity also has an id and a type, and may carry label, description, and the provenance facet: version, created_at, created_by, revision_of.

Relationships

Relationship	Points to	How many	Required	Meaning
`generated_by`	Action	one		The Action that produced this Result, Signal, or Observation.
`derived_from`	Signal	many	yes	The Signals an Observation was interpreted from.
`about`	Work Item, Actor, Action, Task	one		What the Observation describes.
`has_confidence`	Confidence	one		The Confidence attached to this Result, Observation, Action, or Plan.

Pointed to by

From	Relationship	Read backward as
Context	`draws_on`	informs

Notes

"The claim amount is $38,200" is an Observation; the scanned claim form it was extracted from is a Signal.

Alignments

Standard or protocol	Term	Correspondence
W3C SOSA/SSN	`sosa:Observation`	closeMatch
W3C PROV-O	`prov:Entity`	subClassOf

Example

Source: examples/claims-processing.jsonld. The example passes all validation checks.

{
  "id": "obs-claim-amount-84933",
  "type": "Observation",
  "observed_property": "claim_amount",
  "observed_value": 38200,
  "method": "document-extraction",
  "derived_from": [
    "sig-claim-form-84933"
  ],
  "about": "claim-84933",
  "generated_by": "act-extract-84933",
  "has_confidence": "conf-obs-84933"
}

Term reference · JSON Schema · SHACL shape aowsh:ObservationShape