Hi Sam (and Rong)

Sam Heard wrote:

> Dear Rahil
>
> The syntax for allowable text string values in the .Net parser and 
> Tom's I believe is a set of delimited strings as you have described. 
> There is no use of regular expressions here at the moment. I am not 
> sure of the latest developments in the parser but this is how it is in 
> all current archetypes used by Ocean.

In such an event, it might be necessary then for the team to allow for 
comma-separated values to be dealt with by the ADLParser. I hope this 
will be possible. Please let me know otherwise, as I will be dealing 
with a large set of arbitrary archetype models which will require 
parsing with the help of the ADLParser and openEHR Java Kernel API.

Thanks.

Regards
Rahil

>
> Sam
>
> Rahil wrote:
>
>> Hi
>>
>> Comments in line.
>>
>> Rong Chen wrote:
>>
>>> Rahil wrote:
>>>
>>>> Hi
>>>>
>>>> I am trying to parse an ADL file using the ADLParser API. However, 
>>>> the ADLParser is throwing up an error in the ADL file that Im 
>>>> passing it. The block of code where the error occurs is :
>>>>
>>>> ------------
>>>> ELEMENT[at0008] occurrences matches {0..1} matches {    -- Person
>>>>                       value matches {
>>>>                           TEXT matches {
>>>>                               value matches {"Patient", "Relative"}
>>>>                           }
>>>>                       }
>>>>                   }
>>>> -----------
>>>>
>>>> and the line with the error is     ------ value matches {"Patient", 
>>>> "Relative"}----. The compile time error thrown is
>>>
>>>
>>>
>>> A string constraint can be expressed either by a fixed string or a 
>>> regular expression. If you want to limit the string value to either 
>>> "Patient" or "Relative", the correct syntax should be as following:
>>>
>>> value matches {/Patient|Relative/}
>>>
>> The syntax in which the {"Patient", "Relative"} appears in the ADL 
>> file is probably the result of me selecting the "Free text or coded" 
>> option in the Entry model of the archetype editor. I havent manually 
>> written the values in this format so theres no way I can change it to 
>> look like this {/Patient|Relative/}.
>>
>> The Editor version Im working with is 0.99.2 Beta. Im not sure if 
>> theres been any later release in which changes have been made with 
>> the ADL syntax.
>>
>> Regards
>> Rahil
>>
>>> Cheers,
>>> Rong
>>>
>>>
>>>>
>>>> Will appreciate help with this.
>>>>
>>>> Thanks
>>>> Regards
>>>> Rahil
>>>>
>>>
>>> -
>>> If you have any questions about using this list,
>>> please send a message to d.lloyd at openehr.org
>>>
>>>
>>
>
> -- 
>
>
>     Dr. Sam Heard
>     MBBS, FRACGP, MRCGP, DRCOG, FACHI
>
> CEO and Clinical Director
> Ocean Informatics Pty. Ltd.
> <http://www.oceaninformatics.biz/>Adjunct Professor, Health 
> Informatics, Central Queensland University
> Senior Visiting Research Fellow, CHIME, University College London
> Chair, Standards Australia, EHR Working Group (IT14-9-2)
> Ph: +61 (0)4 1783 8808
> Fx: +61 (0)8 8948 0215
>
>
> - If you have any questions about using this list, please send a 
> message to d.lloyd at openehr.org
>
>------------------------------------------------------------------------
>
>No virus found in this incoming message.
>Checked by AVG Anti-Virus.
>Version: 7.0.344 / Virus Database: 267.11.14/128 - Release Date: 10/10/2005
>
>  
>

-- 
Rahil Qamar

Ph.D. Student
Room 2.89 Kilburn Building
University of Manchester
Work number: +44 (0) 161 275 5719
Email: qamarr at cs.man.ac.uk
Website: http://www.cs.man.ac.uk/~qamarr/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051012/8db2779e/attachment.html>

Reply via email to