Thanks for your reply. Indeed, the terms CC is referring to the century, together with the next YY it combines the year in total. I've just tested the date given by you but I'm afraid it is not valid. It seems that the year (CCYY) needs to have a minimum of 4 characters. Same for the other items, MM & DD 1111-11-11T11:11:11.1 Is valid. This makes it hard to validate the receiving files from other parties. Because we validate each incoming file with the ISO XSD. If the sender sends the file with a dateTime like 111111-11-11T11:11:11.1 Then our internal processing will go in Error. We may not adjust the ISO XSD-scheme, but I think we need to adapt our internal processing to comply with these cases.
Hello all! I'm having some discussions at work and need some clarification/help 🙂 I'm currently working on XML PACS files (pacs.008.001.02) where timestamps are being used. One of the tags is CreDtTm - Creation Date Time. A simple timestamp as far as I'm aware… Please see XSD scheme definition below: <xs:schema xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.02" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.02" elementFormDefault="qualified"> ... <xs:element name="CreDtTm" type="ISODateTime"/> ... <xs:simpleType name="ISODateTime"> <xs:restriction base="xs:dateTime"/> </xs:simpleType> xs:dateTime should be in format 'CCYY-MM-DDThh:mm:ss.sss' if I'm correct? The issue now is, if I check my input XML file with the corresponding XSD and the tag filled in like (mind the year 22019) <CreDtTm>22019-10-09</CreDtTm> XMLSpy says it's valid. Even if I change the content to something rediculous, e.g. 220000000000019-10-09 XMLSpy says it's valid. Does the CC mean it is a variable lenght and not restricted to 2 digits? Please advice 🙂 Thanks a lot in advance!