Thanks, Matthias. I have linked your examples from the microarray use case. I agree that a totally manual semantic markup would not be not-scalable. Some (semi-)automatic would help.

Cheers,

-Kei

Matthias Samwald wrote:

Addendum: I started manually curating / annotating some of the papers for the microarray use case (following the aTag convention, as usual). See http://hcls.deri.org/atag/data/gene_expression_atags.html This kind of manual curation is quite time consuming, so I only did it for key findings in some of the papers.

I have also integrated the NCBO ontology term selection widget into the aTag Generator, so this NCBO service can now be used for the curation of web content. At the moment it works only for the NIFSTD and the NCI Thesaurus. Bookmarklets can be found on http://hcls.deri.org/atag/

Cheers,
Matthias Samwald


--------------------------------------------------
From: "Kei Cheung" <kei.che...@yale.edu>
Sent: Monday, January 04, 2010 9:42 PM
To: "HCLS" <public-semweb-lifesci@w3.org>
Subject: Re: BioRDF Telcon

Today's minutes are available at: http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Meetings/2010/01-04_Conference_Call

Cheers,

-Kei

Kei Cheung wrote:

Happy 2010!

This is a reminder that the next BioRDF telcon call will be held at 11 am EDT (5 pm CET) on Monday, January 4 (see details below).

Cheers,

-Kei

== Conference Details ==
* Date of Call: Monday January 4, 2010
* Time of Call: 11:00 am Eastern 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: 4257 ("HCLS")
* IRC Channel: irc.w3.org port 6665 channel #HCLS (see W3C IRC page for details, or see Web IRC), Quick Start: Use http://www.mibbit.com/chat/?server=irc.w3.org:6665&channel=%23hcls for IRC access.
* Duration: ~1 hour
* Frequency: bi-weekly
* Convener: Kei Cheung
* Scribe: to-be-determined

==Agenda==
* Introduction: Kei
* Microarray use case -- explore RDF structure based on some sample queries (All)







Reply via email to