On Fri, 2009-11-27 at 00:25 +0900, KOBAYASHI, Shinji wrote: > Hi Tim, and Roger > > I am sorry to misreading. > Otherwise, this is the first time to challenge connectathon. I think we > should suppose simple situation, such as same timezone, using NTP > server(or omit subtle time mismatch) > > Best regards > Shinji
But Shinji, the "patient" doesn't see all providers at the same time. We have to advance time in an unrealistic manner in order to SIMULATE a real situation. --Tim > > On Thu, 26 Nov 2009 12:58:51 -0200 > Tim Cook <timothywayne.cook at gmail.com> wrote: > > > On Thu, 2009-11-26 at 23:24 +0900, KOBAYASHI, Shinji wrote: > > > Hi Roger, > > > > > > I do not think we need special time server, because we can use NTP > > > server to adjust time. > > > > I think you may want to re-read Roger's email and reconsider his > > reasoning. It is a solution to one of the issues I pointed out (on the > > Wiki) that could be a problem. > > > > BTW: Thanks for finally sending the Workshop document. > > > > --Tim > > > > > > > > > > > > > > On Wed, 25 Nov 2009 22:11:05 +0100 > > > Roger Erens <roger.erens at e-s-c.biz> wrote: > > > > > > > On Wed, Nov 25, 2009 at 13:10, KOBAYASHI, Shinji <skoba at moss.gr.jp> > > > > wrote: > > > > > Hi Tim, > > > > > > > > > > Sorry to late response. I have been troubled. > > > > > I list up what we have to implement for connectathon bellow: > > > > > i) Connectathon scineario(done) > > > > > http://www.openehr.org/wiki/display/resources/Connect-a-thon+Details > > > > > > > > So there's only 1 journey, right? I think the encounters could use > > > > some date-times attached to them. > > > > > > > > A suggestion for tackling the first problem area mentioned: during the > > > > connect-a-thon the connect-a-thon coordinator (c24r) should run a > > > > time-server, to which the machines running the health information > > > > applications should sync their time with (say every 10 or 15 minutes). > > > > The c24r could then use the time-server to 'fast-forward' through time > > > > and have every machine update their date and time within 10 or 15 > > > > minutes. > > > > > > > > Another idea might be to use a Google Wave to broadcast changes > > > > real-time. Or use a Skype-meeting. They seem simpler to set up than > > > > using an IRC channel for instant messaging. I don't know about > > > > Twitter. > > > > > > > > Best regards, > > > > > > > > Roger > > > > _______________________________________________ > > > > openEHR-technical mailing list > > > > openEHR-technical at openehr.org > > > > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > > > > > > > -- > > *************************************************************** > > 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 > > > -- *************************************************************** 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20091126/332312ae/attachment.asc>
