SourceForge : Post

Project: Editor Discussion > REC: Usage Record - XML Fmt > Time granularity > List of Posts

Forum Topic - Time granularity: (2 Items)

View: as

08/11/2004 2:29 PM

post4319

Time granularity

2.3.5.2 seems to imply that seconds are the lowest level of granularity.  Yet, many systems will account for data at the
 millisecond or microsecond level (or even in something like clockticks).

I would like to see added specificity in time accounting options, especially the addition of some sort of granularity or
 accuracy measure.  For example, if a system reports a value of 60 seconds, it should also be able to report that this 
is +/- 5 seconds if needed. 

Is there a way to include a reference clock in these records?  With Kerberos, there is a high level of time 
synchronization - but with other types of authentication, systems might not be synchronized.  Maybe this is out of scope
, but if for example two systems are reporting a dateTime, it would be nice to know whether they are using the same 
reference clock or are otherwise synchronized.

Scott Jackson

02/22/2005 8:12 PM

post4320

RE: Time granularity

That is correct. Our approach has been to use primitive XML Schema data types whenever possible. The use of dateTime and
 duration with the smallest granularity being in seconds was sufficient for the contemporary systems that were sampled. 
A couple of workarounds that you might employ to get around this would be to use the description attribute of the 
desired property to encode the fine-grained time information and/or any accuracy measure. For instance, you could use 
something like:

<WallDuration description="176204U/5U">P3DT10H32M47S</WallDuration>

to mean 176204 microseconds and +/-.000005 seconds accuracy -- whatever you would like to dream up for your application.

Return