The TimeScope object encapsulates information regarding a moment (or range) in time (and, optionally, space) along with its meaning. It contains two TimeStamps (DateTime) and two Locations.
TimeScopes contain information regarding the timing of an event. They can either document a single moment in time, or a range (as specified by a start and end); for that purpose TImeSciopes contain two stamps..
TimeScopes are used by value. They contain a CompoundIdentifier, however, for when it is necessary to share the TimeScope across multiple objects; a good example is the case of a crop season, as shown in pseudo-code below:
| Attribute | Type | Multiplicity | Description |
|---|---|---|---|
| Id | CompoundIdentifier | 1 | |
| TimeStamp1 | DateTime | 0..1 | |
| TimeStamp2 | DateTime | 0..1 | |
| Description | String | 0..1 | |
| Location1 | Location | 0..1 | |
| Location2 | Location | 0..1 | |
| Duration | TimeSpan | 0..1 |
| Attribute | Type | Multiplicity | Description |
|---|---|---|---|
| TimeStamp | DateTime | 1 | |
| DateContext | DateContextEnum | 1 | Will eventually be an EnumeratedRepresentationValue |
| Location | Location | 0..1 | Optional space stamp, for compatibility with ISO's ASP |
| DateContextEnum | Type |
|---|---|
| Approval | Instant |
| ProposedStart | Instant |
| ProposedEnd | Instant |
| CropSeason | Interval |
| TimingEvent | Interval |
| Validity | Interval |
| ActualStart | Instant |
| ActualEnd | Instant |
| RequestedStart | Instant |
| RequestedEnd | Instant |
| Expiration | Instant |
| Creation | Instant |
| Modification | Instant |
| Unspecified | Instant |
| RequestedShippingDate | Instant |
| ActualShippingDate | Instant |
| Calibration | Instant |
| Class | Approval | ProposedStart | ProposedEnd | RequestedStart | RequestedEnd | ActualStart | ActualEnd | CropSeason | TimingEvent | Validity | Expiration | RequestedShippingDate | ActualShippingDate | Creation | Modification | Unspecified |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ADAPT has