[This message was posted by Scott Atwell of American Century Investments
<[email protected]> to the "General Q/A" discussion forum at
http://fixprotocol.org/discuss/22. You can reply to it on-line at
http://fixprotocol.org/discuss/read/2ba35e00 - PLEASE DO NOT REPLY BY MAIL.]
UTCTimestamp_t should probably simply eliminate "daily___" attributes and make
the __Value ones xs:time
FIXatdl 1.1 spec defines the UTCTimstamp_t Parameter type with 2 sets of 3
attributes (in conjunction with its localMktTz for interpreting):
minValue UTCTimestamp
maxValue UTCTimestamp
constValue UTCTimestamp
dailyMinValue time
dailyMaxValue time
dailyConstValue time
The "daily__" ones are there to support expressing "HH:MM:SS" with the app
supplying the current date for to complete the timestamp. The first three
likely would never be used (eg when would you say I want a constant value of
Jan 15, 2011 at 4pm, or a max value of Dec 31, 2012 at 10pm). Having both sets
makes implementing all of this a pain (from experience).
In addition, the Clock control's initValue is a xs:time ("Daily"), thus there
is an inconsistency between Clock/@initValue and UTCTimestamp/@constValue.
I see no reason to keep const, min, and max as full timestamps, and thus the
divergence with the daily ones is confusing. My recommendation is to do away
with the 3 daily ones and change the type of minValue, maxValue, and constValue
to be xs:time.
[You can unsubscribe from this discussion group by sending a message to
mailto:[email protected]]
--
You received this message because you are subscribed to the Google Groups
"Financial Information eXchange" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/fix-protocol?hl=en.
