I think we changed this somewhere in the past. Now we only allow date as
yyyy-mm-dd or yyyy-??-?? and times as hh:mm:ss, hh:mm:?? or hh:mm:XX (as we
haven't been able to find use cases for the all question marks dateTime).
Having said that, LinkEHR parses ????-??-??T??:??:?? but it is interpreted
as yyyy-??-??
We are preparing a new version of LinkEHR lite with all these changes
2013/9/2 Bert Verhees <bert.verhees at rosa.nl>
> I have received a few archetypes created with the LinkEHR editor.
>
> In there is a dateTime pattern like this:
> time existence matches {1..1} matches {????-??-??T??:??:??}
>
> I wonder if it is a legal pattern according to the specifications. I must
> say that it is an EN13606 archetype.
>
> If it is legal, then we (or me) need to change the Java-software, because
> at this time, it does not accept this pattern.
>
> se.acode.openehr.parser.**ParseException: Encountered " "?" "? "" at line
> 200, column 136.
> Was expecting:
> "}" ...
>
> at se.acode.openehr.parser.**ADLParser.**generateParseException(**
> ADLParser.java:7258)
> at se.acode.openehr.parser.**ADLParser.jj_consume_token(**
> ADLParser.java:7122)
> at se.acode.openehr.parser.**ADLParser.c_attribute(**
> ADLParser.java:2801)
> at se.acode.openehr.parser.**ADLParser.c_complex_object_**
> body(ADLParser.java:2578)
> at se.acode.openehr.parser.**ADLParser.c_complex_object(**
> ADLParser.java:2561)
> at se.acode.openehr.parser.**ADLParser.c_object(ADLParser.**java:2606)
> at se.acode.openeh...............**.............................
>
> Can someone please comment on this?
>
> Thanks in advance
> Bert
>
>
> ______________________________**_________________
> openEHR-technical mailing list
> openEHR-technical at lists.**openehr.org<openEHR-technical at
> lists.openehr.org>
> http://lists.openehr.org/**mailman/listinfo/openehr-**
> technical_lists.openehr.org<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130902/6904ba83/attachment-0001.html>
