FpML Issues Tracker
closed
Minor
Always
Examples/Test Cases
Admin
sheinrich
Summary
Add the time offset to all time and date examples because use of the time offset is recommended best practise in FpML, and we should be setting a good example.
Add a rule to the build system to check this.
Notes:
andrew
05/30/07 9:11 am
The architecture specification states that use of the time offset in documents must be consistent, e.g. all dates use it or no dates use it.
We need a couple of examples that obey this rule but no more.
matthew
06/05/07 10:16 am
If we recommend something, all examples should follow it.
mgratacos
06/19/07 9:25 pm
Examples of dates with offset (in respect to Zulu time):
Examples with dateTime with offset:
mgratacos
06/26/07 10:26 am
All examples include offsets.
matthew
09/06/07 2:01 pm
The FpML Manual says:
”
4.6.1 Evaluation of Dates
The evaluation of dates in the validation rules is not trivial. The optionality of including time offsets in date datatypes makes comparisons between dates more difficult since sometimes the result is indeterminate as any ISO8601 date is +/- 18 hours of timezone, and +/- 24 hours of day.
The Validation Working Group recommends the use of the XPath 2.0 date/time comparison rules which defines a definitive true / false value even for indeterminate calculations.
The Architecture Specification also suggests that time offsets appear on all date/time values used in FpML documents.
”
The last sentence needs fixing, because the Architecture specification doesn’t say this.
I suggest it is replaced with:
“The Validation Working Group recommends that time offsets appear on all date/time values used in FpML documents.”
mgratacos
01/04/08 5:06 pm
The last sentence has been fixed.