Transition to HTTPS July 19 – Be advised that the FpML website has transitioned to secure HTTP on July 19. URLs are now forwarded to HTTPS automatically. Please make sure you update any internal implementation relying on HTTP URLs accordingly. For further information please email info@fpml.org
The Z suffix indicates that the time is UTC (e.g. +00:00). A time without any suffix or time zone offset has no time zone and can not be normally be ordered relative to a time with zone information. So 12:00:00 != 12:00:00Z
Thanks for the answer but according to your answer many attached messages that appear as valid should fail for rule share-28. like message: fpml-4-8-5-rec-1xmlvalidationvalid-testcasesvalid-shared-14-01.xml another question: 2005-11-01T15:38:00Z2005-11-01T15:38:00Z should be included in validation of share 27 and share 28 do they have to match all the other timezones in the message? Thanks Tamar
In FpML 5.1 we have decided to removed shared-28 from the rule set because as stated the rule is not very practical. For example I might want to have time zones on ‘technical’ time values, like those in the message header but not on ‘business’ time values in the trade or product description. Thats why I have never implemented it in the HandCoded Toolkit — It was a poorly considered rule.