oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

On Wed, 2009-07-08 at 15:57 +0200, Roberto Siqueira wrote:

>   My opinion is that this approach deserves to be further investigated 
> (maybe on a new Blueprint?), at least as a way to cross-check the XML 
> against the ADL. The only downside I found was that unicode strings 
> (like the German definitions in 
> openEHR-EHR-OBSERVATION.blood_pressure.v1.xml) were not properly 
> handled, but maybe this is so because I am doing something wrong -- I am 
> still "discovering" the program and the schemas (schemata?).

Hi Roberto,

I would certainly support a blueprint and a code branch being developed
to explore this further.

If you need help with how to do this on Launchpad then let me know.

I do have reservations about how generateDS develops the code especially
for the definition section.  I think it will still need some hand
editing. But, that said, maybe we can learn from and adapt generateDS
into an OSHIP specific module.

We will certainly need a new parser even for ADL.  I like pyparsing
because it is simple to use; in relative terms.  However,  I would
rather see someone exploring using the ADL grammar in a more
conventional lexx/yacc approach.  Volunteers?

In summary, I think that your efforts are worthwhile and can be combined
with other branches to produce a better approach than we have now.

Cheers,
Tim

Attachment: signature.asc
Description: This is a digitally signed message part