# Date/times in dADL

**Category:** [Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)
**Created:** 2006-06-26 22:12 UTC
**Views:** 4
**Replies:** 2
**URL:** https://discourse.openehr.org/t/date-times-in-dadl/14544

---

## Post #1 by @thomas.beale

Dear all,
I have just noticed that in the dADL part of the ADL spec it says that
partial date/times are expressed in a form using "??" characters rather
than the standard ISO8601 format, which is to simply leave out missing
parts\. E\.g\. april 1954 is 1954\-04 in ISO8601, but the dADL spec
currently says it should be 1954\-04\-??\. While I wish the ISO8601
standard was like this, it is not, and in fact in our Eiffel parser, we
have implemented the standard\. We can't handle just a year or just an
hour, since these get confused with integers \(which is the original
reason for making dADL deviate from ISO8601\)\. But realistically, will
there be many instances where only a year or only an hour is needed
\(there might be \- I don't really know\.\.\.\.\. \- Sam \- any comments?\)\.

Rong, what did you implement in the Java parser?

\- thomas

---

## Post #2 by @system

> reason for making dADL deviate from ISO8601\)\. But realistically, will
> there be many instances where only a year or only an hour is needed
> \(there might be \- I don't really know\.\.\.\.\. \- Sam \- any comments?\)\.

I would say, for research purposes, when only the year of birth is needed to
know

Bert

---

## Post #3 by @rong.chen

Thomas Beale wrote:
> Dear all,
> I have just noticed that in the dADL part of the ADL spec it says that
> partial date/times are expressed in a form using "??" characters rather
> than the standard ISO8601 format, which is to simply leave out missing
> parts\. E\.g\. april 1954 is 1954\-04 in ISO8601, but the dADL spec
> currently says it should be 1954\-04\-??\. While I wish the ISO8601
> standard was like this, it is not, and in fact in our Eiffel parser, we
> have implemented the standard\. We can't handle just a year or just an
> hour, since these get confused with integers \(which is the original
> reason for making dADL deviate from ISO8601\)\. But realistically, will
> there be many instances where only a year or only an hour is needed
> \(there might be \- I don't really know\.\.\.\.\. \- Sam \- any comments?\)\.
>
> Rong, what did you implement in the Java parser?
>  

According to the ADL spec I think\. See examples from test adl file\.

date\_attr1 matches \{yyyy\-mm\-dd\}
                date\_attr2 matches \{yyyy\-??\-??\}
                date\_attr3 matches \{yyyy\-mm\-??\}
                date\_attr4 matches \{yyyy\-??\-XX\}

---


**Canonical:** https://discourse.openehr.org/t/date-times-in-dadl/14544
**Original content:** https://discourse.openehr.org/t/date-times-in-dadl/14544