Then you shouldn't have any problems
El 23/08/2013 15:43, "Bert Verhees" <bert.verhees at rosa.nl> escribi?:

>  On 08/23/2013 03:33 PM, Diego Bosc? wrote:
>
> You will have problems with openehr c_quantity domain type.
>
> I am not sure about that.
>
> There are a lot of test-files with that domain-type and no problem occurs.
> It is, I think, because the "units" will always occur inside this domain
> type, and inside the domain type, the DOMAIN_TYPE_C_QUANTITY lexical state
> should be active.
>
> But please feel free to correct me, I don't have much experience with JJ
>
> Bert
>
>
>  El 23/08/2013 15:31, "Bert Verhees" <bert.verhees at rosa.nl> escribi?:
>
>>
>>  2)
>>>
>>> The ADL-Parser is not capable of parsing EN13606 archetypes because of
>>> the keyword "units" which belongs to the EN13606 datatype PQ.
>>>
>>
>> I solved this problem by commenting out all occurrences of SYM_UNITS
>>
>> This is in line 2958, becomes: (<SYM_C_QUANTITY_UNITS>/*|<SYM_UNITS>*/)
>> <SYM_EQ> "<"
>> and line 341 becomes: /*| < SYM_UNITS: "units"> :DOMAIN_TYPE_C_QUANTITY*/
>>
>> When done these changes, it parses the EN13606 PQ datatype, and I don't
>> see another error-situation coming up.
>>
>> What do you think?
>>
>> Bert
>>
>>
>>
>> _______________________________________________
>> openEHR-technical mailing list
>> openEHR-technical at lists.openehr.org
>>
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>
>
>
> _______________________________________________
> openEHR-technical mailing listopenEHR-technical at 
> lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at 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/20130823/d97a466d/attachment-0001.html>

Reply via email to