another possible error in ADL-parser?

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:
    "use_node" ...
    <SYM_ALLOW_ARCHETYPE> ...
    "c_dv_quantity" ...
    <V_LOCAL_TERM_CODE_REF> ...
    <V_CODE_PHRASE> ...
    <V_TYPE_IDENTIFIER> ...
    <V_TERMINOLOGY_ID_BLOCK> ...
    "+" ...
    "-" ...
    <V_INTEGER> ...
    "C_DV_ORDINAL" ...
    "true" ...
    "false" ...
    <V_ISO8601_DATE_CONSTRAINT_PATTERN> ...
    <V_DATE> ...
    "|" <V_DATE> ...
    "|" "<" ...
    "|" "<=" ...
    "|" ">" ...
    "|" ">=" ...
    <V_ISO8601_TIME_CONSTRAINT_PATTERN> ...
    <V_HHMM_TIME> ...
    <V_HHMMSS_TIME> ...
    <V_HHMMSSss_TIME> ...
    <V_HHMMSSZ_TIME> ...
    <V_HHMMSSssZ_TIME> ...
    "|" <V_HHMM_TIME> ...
    "|" <V_HHMMSS_TIME> ".." ...
    "|" <V_HHMMSS_TIME> "|" ...
    <V_ISO8601_DATE_TIME_CONSTRAINT_PATTERN> ...
    <V_DATE_TIME> ...
    <V_DATE_TIME_MS> ...
    <V_DATE_TIME_Z> ...
    <V_DATE_TIME_MSZ> ...
    "|" <V_DATE_TIME> ...
    "|" <V_DATE_TIME_MS> ...
    "|" <V_DATE_TIME_Z> ...
    "|" <V_DATE_TIME_MSZ> ...
    <V_ISO8601_DURATION_CONSTRAINT_PATTERN> ...
    <V_ISO8601_DURATION> ...
    "|" <V_ISO8601_DURATION> ...
    <V_STRING> ...
    <V_REGEXP> ...
    "|" "+" ...
    "|" "-" ...
    "|" <V_INTEGER> ...
    "*" ...
    <V_REAL> ...
    "|" <V_REAL> ...
    "|" <V_HHMMSS_TIME> ...

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