← Back to team overview

oship-dev team mailing list archive

Re: XMLSchemas openEHR version 1.0.2

 

Hi Tarsis,

I am sorry that you could not attend the workshop.  I did speak with
Diego about these issues and what you should be focusing on in the
coming weeks.  Also, while I am preparing the new roadmap/vision
document Diego will share this information with you in advance of me
completing the document.

Thanks,
Tim


On Tue, 2010-06-29 at 20:51 -0300, Tarsis Azevedo wrote:
> Hi Tim,
> 
> i don't understand what you want! =/
> 
> I worked with PyXB and not seen when its help us! 
> 
> You help me?
> 
> Tarsis Figueredo Azevedo. 
> -------------------
> Linux User: #496982
> -------------------
> 
> "Any fool can write code that a computer can understand. Good
> programmers write code that humans can understand.
> 
> -Martin Fowler, Refactoring: Improving the Design of Existing Code"
> 
> 
> 2010/6/22 Tim Cook <timothywayne.cook@xxxxxxxxx>
>         On Tue, 2010-06-22 at 00:58 -0500, Tim Cook wrote:
>         > At this point you know it validated through the SAXparser.
>         
>         
>         This is true.  But, it doesn't mean it is a valid archetype.
>          You'll
>         need to read the section in the PyXB docs about BIND and using
>         anonymous
>         elements.
>         http://pyxb.sourceforge.net/userref_usebind.html
>         
>         >From this I believe that you can write your remaining
>         validation code.
>         Even though they talk about creating instances.
>         
>         If you have problems let us know.  Someone here can work it
>         out. :-)
>         
>         
>         
>         --Tim
>         
> 

-- 
***************************************************************
Timothy Cook, MSc

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == (upon request)
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

You may get my Public GPG key from  popular keyservers or    
from this link http://timothywayne.cook.googlepages.com/home 

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


References