FpML Issues Tracker
closed
Minor
N/A
Validation Rules
danieldui
danieldui
Summary
When Andrew J raised the related issue about time zones, Tony Coates noted that perhaps the timezone should not be indicated in a date when also businessCenter is present.
Notes:
h_mcallister
08/31/10 2:14 pm
I do not think that dates need to include a timezone, where the businessCenter(s) is|are present or implied by context. In such cases timezone is redundant and potentially inconsistent with the specified businessCenter(s). This was one of the reasons why I was sceptical about the global imposition of the “Z” suffix on dates in the FpML sample trades at FpML 4-4.
This topic has been discussed at FpML Coordination in the past – please see message thread at http://www.fpml.org/_wgmail/_coordmail/msg01181.html, in particular the responses at http://www.fpml.org/_wgmail/_coordmail/msg01195.html.
danieldui
09/21/10 12:09 pm
I’d like to hear feedback from implementers, but I agree with Harry. A time offset can introduce confusion when also business center is present.
The time offsets are useful mostly when a date is recording when something has happened rather than indicating when something is due to happen.
danieldui
10/02/10 7:43 pm
This issue was discussed on Sep 21 meeting.
Someone (Irina ?) Noted that although often having both the time offset and the businessCenter is redundant as one implies the other. But they identify different concepts: The time offset indicates the local time at a particular geographical location, whereas the business center indicates a business calendar. Moreover a document may specify multiple business centers.
Preventing the use of business center and time offset at the same time could therefore be too restrictive.
With hindsight, the element businessCenter should perhaps have been called businessCalendar or businessDayCalendar .
This issue is related to new issue 1020 (http://www.fpml.org/issues/view.php?id=1020) .
iyermakova
06/29/11 7:03 pm
danieldui
07/05/11 11:59 am
mgratacos
07/19/11 1:05 pm
Discussed at the Coordination Committee on 2011-07-18. There was agreement to remove the Z suffix from the 4.10 and 5.2 examples. In addition, the Architecture Working Group will update the Architecture Specification to update the recommended use of time zones.
danieldui
07/19/11 2:11 pm
danieldui
08/23/11 1:32 pm
mgratacos
09/22/11 3:12 pm
I am checking the reporting view.
mgratacos
09/22/11 6:10 pm
I reviewed the Reporting view examples. There were two examples in the Transparency view, ex 04 and ex 20, which contained time zones in the trade details. The time zones have been removed.