Issue 1717:  Description of the IN parameter tdf is missing (Time Service)                                                                                                                                          (issues)
Source:  (, )
Nature:  Clarification
Severity:  Significant
Summary: Summary: For the interface
 	UTO CosTime::TimeService::new_universal_time(
 		in TimeBase::TimeT time,
 		in TimeBase::InaccuracyT inaccuracy,
 		in TimeBase::TdfT tdf
 	);
 the description of the IN parameter tdf is missing.
 
 

Resolution: :TimeService::new_universal_time(
Revised Text: :TimeT time,
Actions taken:
July 22, 1998: received issue
Discussion: 

End of Annotations:=====
Return-Path: <www>
Date: Wed, 22 Jul 1998 08:00:49 -0400
From: www
To: juergen@omg.org, web-incoming@omg.org
Subject: WWW Form output

Name: Wolf Geldmacher
Company: UBS AG
Email: wgeldmacher@paus.ch
Specification: CORBAservices: Common Object Services Specification
Section: 14. Time Service Specifiaction
Formal #: 
Version: V1.0
Revision_Date: 07/04/97
Page: 14-12
Nature: Clarification
Severity: Significant
full_desc: For the interface
	UTO CosTime::TimeService::new_universal_time(
		in TimeBase::TimeT time,
		in TimeBase::InaccuracyT inaccuracy,
		in TimeBase::TdfT tdf
	);
the description of the IN parameter tdf is missing.

The semantics of the interface are therefore unclear: Is the time
displacement factor tdf just stored in the constructed UTO or is
it evaluated to convert the TimeT argument from the local time to
UTC? Depending on the correct interpretation of tdf the UTO object
could represent a time that is almost a day off.

In analogy to the other interfaces defined I would assume that the
tdf is just stored in the generated object - i.e. the time argument
is also stored unmodified.
submit: Submit Issue Report