Page Comparison

...

• ADAPT TimeContext Definitions
• ADAPT - ISO ASP - TIM Use Cases
  

TimeScope

Image Added 

...

Description:

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 locationTimeStamps (DateTime) and two Locations. 

contains TimeScopes contain information regarding the timing of an event. It They can either document a single moment in time, or a range (as specified by a start and end); for that purpose it contains TImeSciopes contain two stamps..

TimeScopes can be are used by reference or by value. They are used by reference 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:

<Timescope>

<Stamp1>

<TimeStamp>1/1/2016 00:00:00</TimeStamp>

<DateContext>CropSeason</DateContext>

</Stamp1>

<Stamp2>

...

:

...

<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>

Usage notes:

• A single TimeScope should not be used to convey different kinds of information in the two stamps. The second stamp should only be used to finish specifying a time interval, as in the case of a CropSeason   (e.g., "2016 Crop") or TimingEvent (e.g., "2016 Burndown").

...

Referenced by:

• XXX
• XXXX
• XXXXX

DateWithContext

...

Documentation

ADAPT has 

...