ADAPT TimeContext Definitions

05 Apr 2016  R. Andres Ferreyra (Unlicensed): Having assembled a long, somewhat arbitrary list of contexts, I think we can more effectively capture semantics with 2-3 attributes instead of a single DateContext attribute. See Valid Compositions table below.

Some challenges:

• Not all possible compositions are "valid".
• Any given "valid" composition (except perhaps for "(Actual)Create" and "(Actual)Modify)" is usable in only a subset of the TimeScope-bearing classes in ADAPT.
• Should we build some kind of knowledge representation system to capture all of this? 
  • The proposed SPADE3 ContextItemDefinition class has the concept of "Properties" that we could use to bring along the multiple attributes of any given DateContext. 
  • Another possibility is to build a separate artifact to manage this, such as an ontology.

Instantaneous

Modifier: Planned, Proposed, Requested, Estimated, Actual

08 Apr 2016  note: ISO's list of type of the recorded time, possible values:

1 = Planned

2 = Preliminary

3 = Preparation

4 = Effective

5 = Ineffective

6 = Repair

7 = Clearing

8 = Powered Down ^c

Context: Approve, Expire, Observe, Start, End, Load, Unload, Resume, Ship, Suspend, Calibrate, Create, Modify

Interval

Modifier: None

Context: CropSeason, Timing Interval, ValidityRange, ActivityRange 

Valid Compositions

	Planned	Proposed	Requested	Estimated	Actual / Effective
Approve
Expire
Observe/ Measure
Start
End
Load
Unload
Suspend
Resume
Ship
Calibrate
Create
Modify
Unspecified

CurrentList