# another possible error in ADL-parser?

**URL:** https://discourse.openehr.org/t/another-possible-error-in-adl-parser/12654
**Category:** Reference Implementation: Java (archive)
**Created:** [23 November 2007 11:22 UTC](https://discourse.openehr.org/t/another-possible-error-in-adl-parser/12654 "2007-11-23T11:22:28Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)
#### Post date: [23 November 2007 11:22 UTC](https://discourse.openehr.org/t/another-possible-error-in-adl-parser/12654/1 "2007-11-23T11:22:28Z")

</div>

It is the same archetype, as previous mail, but the line-number below is  
not correct,

this is the line: time\_attr5 matches {|22:00:05,0|}

regards  
Bert Verhees

se.acode.openehr.parser.ParseException: Encountered "| 22:00:05 ," at  
line 412, column 69.  
Was expecting one of:  
&nbsp;&nbsp;&nbsp;&nbsp;"use\_node" ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<SYM\_ALLOW\_ARCHETYPE\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"c\_dv\_quantity" ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_LOCAL\_TERM\_CODE\_REF\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_CODE\_PHRASE\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_TYPE\_IDENTIFIER\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_TERMINOLOGY\_ID\_BLOCK\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"+" ...  
&nbsp;&nbsp;&nbsp;&nbsp;"-" ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_INTEGER\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"C\_DV\_ORDINAL" ...  
&nbsp;&nbsp;&nbsp;&nbsp;"true" ...  
&nbsp;&nbsp;&nbsp;&nbsp;"false" ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_ISO8601\_DATE\_CONSTRAINT\_PATTERN\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_DATE\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_DATE\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" "\<" ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" "\<=" ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" "\>" ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" "\>=" ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_ISO8601\_TIME\_CONSTRAINT\_PATTERN\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_HHMM\_TIME\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_HHMMSS\_TIME\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_HHMMSSss\_TIME\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_HHMMSSZ\_TIME\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_HHMMSSssZ\_TIME\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_HHMM\_TIME\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_HHMMSS\_TIME\> ".." ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_HHMMSS\_TIME\> "|" ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_ISO8601\_DATE\_TIME\_CONSTRAINT\_PATTERN\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_DATE\_TIME\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_DATE\_TIME\_MS\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_DATE\_TIME\_Z\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_DATE\_TIME\_MSZ\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_DATE\_TIME\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_DATE\_TIME\_MS\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_DATE\_TIME\_Z\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_DATE\_TIME\_MSZ\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_ISO8601\_DURATION\_CONSTRAINT\_PATTERN\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_ISO8601\_DURATION\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_ISO8601\_DURATION\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_STRING\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_REGEXP\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" "+" ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" "-" ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_INTEGER\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"\*" ...  
&nbsp;&nbsp;&nbsp;&nbsp;\<V\_REAL\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_REAL\> ...  
&nbsp;&nbsp;&nbsp;&nbsp;"|" \<V\_HHMMSS\_TIME\> ...

---

<div class="post-metadata">

### Author: ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)
#### Post date: [23 November 2007 15:22 UTC](https://discourse.openehr.org/t/another-possible-error-in-adl-parser/12654/2 "2007-11-23T15:22:56Z")

</div>

Thanks, Bert!  
Besides the problem with fractional separator, both the parser and DvDateTimeParser only allow 3 digits for fractional seconds. Now these are fixed on the trunk.  
/Rong