← Back to team overview

oship-dev team mailing list archive

Re: Activities progress and doubts about DvDate implementation

 

Thanks Wagner,

Yeah, at least keep Diego informed is important.

Glad you finished moving.  That is never much fun.  

Cheers,
Tim

On Wed, 2010-11-17 at 11:26 -0200, Wagner Francisco wrote:
> Hi Diego,
> 
> I had some problems with my laptop and my internet connection, I moved
> from my old apartment and now I'm finishing my course final paper. So
> I was too busy. I sent an e-mail to Sergio and Luciana explaining the
> situation, I should have copied it here too. 
> 
> But now I'm having more time and I'll work more on OSHIP.
> 
> 
> Cheers,
> Wagner.
> 
> 
> 
> 2010/11/12 Diego Manhães Pinheiro <me@xxxxxxxxxxxxxx>
>         -----BEGIN PGP SIGNED MESSAGE-----
>         Hash: SHA1
>         
>         
>         Hi all again,
>         
>         
>         First of all, I've seen litte progress on tasks assigned for
>         two months.
>         So, I ask with great humility: Eduardo and Wagner, do you have
>         any
>         detail that stuck you on code implementation ?
>         
>         At the moment, I'm stucked on specific detail about a DvDate
>         object: The
>         ISO8601 interface defined at openEHR specifications define
>         some rules to
>         validate a string date. The format must follow the gregorian
>         calendar,
>         which means that the most old year supported is the 0001 year.
>         In other
>         hand, the method described on the openEHR specification that
>         validates
>         an year considers 0000 as a valid year, but the year 0000
>         doesn't exists
>         in the gregorian calendar. The ISO 8601 specification supports
>         years
>         before christ death, but the gregorian calendar don't. So, how
>         could I
>         fix that ?
>         The simple solution that I found is don't validate days on
>         months(because the gregorian calendar don't support it) if is
>         the year 0.
>         I will be glad on any other better solution. Please, don't
>         throw up the
>         possibility that I'm wrong on any detail described here. I'm
>         not an ISO
>         8601 expert, so any idea will help. :)
>         
>         
>         Thanks in advance.
>         -----BEGIN PGP SIGNATURE-----
>         Version: GnuPG v1.4.11 (Darwin)
>         
>         iQEcBAEBAgAGBQJM3KVkAAoJEEfarWn4YOc8OmcH/RIdCiTHkek13CFdkdp0vDKy
>         LfpalWhd+PTBhBa7NyxwLVWwAJ/H/Tq7aafdPr0I0l1nW9dxf
>         +nZ3drrM7/m4VmH
>         KEG28sirVxTdB+aSxwvQZaYHFBNq5xc/oCkdMjzP7wK0Bb+wGIukjq
>         +adiR3fWFu
>         G5XSi+Fcq7EXdpYvOOMkIzsnOUR
>         +L5pKSFl4xc6Nn12sQsTyBnZOV3MR6sOdldbg
>         Ozw6SicIrnymVLx58iC5D8tZO/H0yYzVlwILWvw1ClP8b0ry0izMkUJ
>         +nyc3cxBk
>         DWewo55+U1xTpxlZUuus7nD
>         ++Te3dajIFekJv8QHxye9cHYebm9KmyzJjvhNej8=
>         =fquT
>         -----END PGP SIGNATURE-----
>         
>         _______________________________________________
>         Mailing list: https://launchpad.net/~oship-dev
>         Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
>         Unsubscribe : https://launchpad.net/~oship-dev
>         More help   : https://help.launchpad.net/ListHelp
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~oship-dev
> Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~oship-dev
> More help   : https://help.launchpad.net/ListHelp

-- 
***************************************************************
Timothy Cook, MSc
Project Lead - Multi-Level Healthcare Information Modeling
http://www.mlhim.org 

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook
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