BSA — using Time Service

I would like to discuss the usage of data types from TimeBase module. It
is probable that I just need some patient explanation - but it may also
turn out that some clarification in our bsa spec could be made. I mean a
clarification how to use the TimeBase data types properly.

The talk is about the "absolute" attributes: created, started, ended
(whatever moment they mean - it is a different topic).

These attributes are expressed as TimeBase::UtcT. Which means that each
of them consists from 4 values: TimeT, two InaccuracyT's and TdfT.
The simplest is probably TdfT which defines in which time zone the
analysis was executed. Is this interpretation correct?
The members for inaccuracy may be used to say that the main time (in
TimeT, see below) is actually only precise for milliseconds - because I
guess most implementations and languages give us easily only milliseconds
and not 100 nanoseconds. Again, would this interpretation of these
attributes be correct?
The main attribute is TimeT. Here is the definition from the TimeBase
spec:

"TimeT represents a single time value, which is 64 bits in size, and
holds the number of 100 nanoseconds that have passed since the base time.
For absolute time the base is 15 October 1582 00:00 of the Gregorian
Calendar. All absolute time shall be computed using dates from the
Gregorian Calendar."

My question is: Does CORBA Time Service specify that this attribute
must be an absolute time? Would not be easier (and more appropriate for
our purposes) to say in our spec that this time is relative to the
beginning of the epoch (1/1/1970)? In other words, there are actually two
questions:

• Do we need to use an absolute time here (to remain compliant with the
  Time Service)?
• And if the answer is "no", then: do we want to have here an absolute
  gregorian time?

Accepted. Yes, we use absolute time, in compliance with the Time Service. No change to specification