- From: Joanne Luciano (gmail) <jluciano@gmail.com>
- Date: Mon, 15 Feb 2010 12:26:39 -0500
- To: John Madden <john.madden@duke.edu>
- Cc: w3c semweb HCLS <public-semweb-lifesci@w3.org>
- Message-Id: <80EDEFC8-BFB8-4BFB-85EA-01E39C1E7A9E@gmail.com>
Regrets,
I didn't realized we were meeting today (holiday). I won't be able to
make the call.
Cheers,
Joanne
On Feb 15, 2010, at 9:06 AM, John Madden wrote:
> This is a reminder that the next HCLS Terminology conference call is
> scheduled for MONDAY, February 15, 2010.
>
> Conference Details
> . Date of Call: Monday Februrary 15, 2010
> . Time of Call: 1700h UTC (1200h U.S. Eastern Standard Time,
> 1700h
> London, 1800h CET, 0900h U.S. Pacific Standard Time)
> . Dial-In #: +1.617.761.6200 (Cambridge, MA)
> . Dial-In #: +33.4.89.06.34.99 (Nice, France)
> . Dial-In #: +44.117.370.6152 (Bristol, UK)
> . Participant Access Code: 42572# ("HCLS2")
> . IRC Channel: irc.w3.org port 6665 channel #hcls2
> (see W3C IRC page for details, or see Web IRC*)
> . Duration: ~1 hour
> . Convener: John Madden
> * Scribe: TBD
>
>
> John F. Madden, M.D., Ph.D.
> Associate Professor
> Department of Pathology (3712)
> Duke University Medical Center
> Durham, NC 27710
> USA
>
> john.madden@duke.edu
> +1 919 681 6671 (voice)
> +1 919 618 6671 (fax)
> +1 919 597 0304 (mobile)
>
>
> * If you do not have an IRC client installed on your computer, you
> can get
> one of the many free one (search "irc client" and your platform), or
> you can
> use a web-based client.
>
> One possible web-based client you might try is Mibbit
> (http://www.mibbit.com/chat/). If you use mibbit, fill out the
> blanks like
> this (you need to click on "Server" to reveal the "Server address"
> field.
> Fill in server address with irc.w3.org:80. Select a chat name you
> like,
> often people use first name in lowercase followed by family name
> initial (no
> spaces, e.g. John Smith might use johnS).
>
> (Note that I suggest using port 80 from mibbit. The W3C irc server
> supports
> this, and it bypasses enterprise firewall issues that many users
> seem to be
> having with port 6667.)
>
>
>
>
Received on Monday, 15 February 2010 17:27:10 UTC