[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DE Conformance
We addressed some good points in the IF-SC yesterday that I thought should be brought up offline to the TC…
While we were addressing other issues Dave ran some sample messages through CAM to do some validation & conformance evaluation. My sample messages (which were generated from XMLSpy) didn’t specify a timezone or offset from UTC, which was discussed as a side item. The DE schema uses the W3C standard DateTime Format, but then clearly states that the dateTimeSent element must include the offset time for time zone. So this was mia culpa. At the meeting the question was raised that if no offset is specified UTC is assumed. I did a little digging and it turns out local time is assumed, which as stated in the ISO 8601 documentation introduces ambiguity.
Thanks to Dave and the CAM tool for bringing out conformance to the forefront in a solid example.
Dave – Can you share your CAM tool configuration file with the TC ?
From the W3C standard site (http://www.w3.org/TR/xmlschema-2/#timeZonePermited)
W3C uses ISO 8601 for DateTime. Their spec states that:
“If no UTC relation information is given with a time representation, the time is assumed to be in local time. While it may be safe to assume local time when communicating in the same time zone, it is ambiguous when used in communicating across different time zones. It is usually preferable to indicate a time zone (zone designator) using the standard’s notation.
After discussing this and a couple of other conformance issues for DE 2.0 I went through the document and pulled out all of the conformance points not covered in the schema to share with the TC. Please look this over and comment / add to the list so we can have list that we agree is representative of the documentation. I will then put this on the Adoption TC’s wiki section on implementing the standards so we have a public reference point.
I will also save this table in an excel spreadsheet and post it to kavi.
Please provide input so we can move ahead with a solid set of conformance rules.
The MITRE Corp.