Reminder of HCLS Terminology telcon, Friday Feb 20, 1500h UTC

Hi Terminology Taskforce participants! I'm posting this as usual to  
the listserv and cc'ing our regulars and others who have expressed  
interest recently.

(If I have forgetten any individuals, don't take it personally!!!!)

We have our weekly call tomorrow at the usual time. Here's the call-in  
info:

Date of next call
Friday, February 20, 2009
What time?
1500h UTC = 1000h US Eastern Time (EDT) = 1100h Central European time  
(CET)
Dial-In # (US)
+1.617.761.6200 (Cambridge, MA)
Dial-In # (Continental Europe)
+33.4.89.06.34.99 (Nice, France)
Dial-In # (UK)
+44.117.370.6152 (Bristol, UK)
Participant Access Code
8376# ("TERM")
IRC Channel
irc.w3.org port 6665 channel #HCLS2 (see W3C IRC page for details, or  
see Web IRC, or see note below)
Duration
~1 hour
Convener
John Madden, Duke University

Agenda for next call (Friday, February 20, 2009 (1500h UTC)

Test of AIDA front end
Addition of RDFS reasoner to Sesame server
Other terminologies to be added
Potential collaboration with Pharma on Patient-of-a-Physician (POAP)  
ontology
C-SHALS
F2F plans



-------------------------------------------------------------------------
PROBLEMS WITH IRC?
-------------------------------------------------------------------------

If you do not have an IRC client installed on your computer, you can  
get one of the many free ones (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" (highlighted in red in attached image) to reveal the  
"Server address" field.

** Fill it out server address as shown.

** Pick a Nickname (usually your first name (all lowercase) and family  
name initial (uppercase).

** Fill in the Channel ("#hcls2").

*** Note: I suggest using port 80 from mibbit, as shown below. The W3C  
irc server supports this, and it bypasses enterprise firewall issues  
that some users have with (the more conventional) port 6667.

Received on Thursday, 19 February 2009 20:43:59 UTC