The TimeScope object encapsulates information regarding a moment (or range) in time (and, optionally, space) along with its meaning. It contains two "stamps" that can hold a DateTime along with a location.
contains information regarding the timing of an event. It can either document a single moment in time, or a range (as specified by a start and end); for that purpose it contains two stamps..
TimeScopes can be used by reference or by value. They are used by reference 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:
<Timescope>
<Stamp1>
<TimeStamp>1/1/2016 00:00:00</TimeStamp>
<DateContext>CropSeason</DateContext>
</Stamp1>
<Stamp2>
<TimeStamp>12/31/2016 00:00:00</TimeStamp>
<DateContext>CropSeason</DateContext>
</Stamp2>
<Description>2016 Crop Season</Description>
<ID>
<ReferenceID>200</ReferenceID>
<UniqueID>
<Id>14a069c4-4ae7-4c07-92a6-ecb58ed10c3a</Id>
<CIType>UUID</CIType>
<IsFirstSource>True</sFirstSource>
</UniqueID>
</ID>
</TimeScope>
Attribute | Type | Multiplicity | Description |
---|---|---|---|
Id | CompoundIdentifier | 1 | |
Stamp1 | DateWithContext | 1 | |
Stamp2 | DateWithContext | 0..1 | |
Description | String | 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 |
---|
Approval |
ProposedStart |
ProposedEnd |
CropSeason |
TimingEvent |
ActualStart |
ActualEnd |
RequestedStart |
RequestedEnd |
Expiration |
Creation |
Modification |
Unspecified |
RequestedShippingDate |
ActualShippingDate |
Calibration |
ADAPT has