W3C

- DRAFT -

SV_MEETING_TITLE

22 Feb 2010

See also: IRC log

Attendees

Present
HaroldSolbrig, mscottm, EricP, John_Madden
Regrets
Chair
SV_MEETING_CHAIR
Scribe
solbrig

Contents


<mscottm> Hi, anybody here? I can't hear anyone on hcls2

<mscottm> scott: brings up serving UMLS terms from a different location than UMLS, would it be possible?

<mscottm> harold: I've looked into this type of thing for some time in the context of HL7

<mscottm> ..NLM thinks it would require 'semantic lifting' although I'm not entirely convinced

<mscottm> ..example: take 'cabernet sauvignon' from wine ontology, remove namespace and replace it with PURL namespace of bioportal

<johnM> Hi all I will be back on momentarily

<mscottm> http://sharedterm/snomedct/1234567

<mscottm> http://sharedterm/umls/12345678

<mscottm> two issues: 1) using the same URI 2) providing RDF when you resolve that URI

urn: iso:2.16.840.1.113883.6.92:12345678

URI to cannonical URI: f(urn:iso:2.16.840.1.1138836.92) --> http://sharedterm.org/snocmetct/1234567

f(http://sharedterm.org/snomedct/1234567) --> http://sharedterm.org/snomedct/1234567

f(http://sharedterm.org/snomedct/) --> http://sharedterm.org/snomedct/

the challenge is the "1234567"

Two issues: (1) there are many URI's for 1234567 in SNOMED and (2) there are multiple renderings for SNOMDE 1234567

(1) Someone need a map from many URI's to a (contextual) cannonical URI

(e.g. http://purlz.og/sct/)

What this allows is, instead of telling HL7 "your URI's are no good", we say - use this URL and we will return the source (e.g. IHTSDO) URI, which you can then use on the web

Use the URL (purlz.org/uri/urn:iso:216.840.1.113883.6.92) to the http://ihtsdo.org/

or http://purlz.org/uri/http://ihtsdo.org/ --> http://ihtsdo.org/

<mscottm> http://esw.w3.org/topic/HCLS/CSHALS2010/Tutorial#outline

Actually, what I would hope happens is that http://purlz.org/uri/urn:iso:2.16.840.1.113883.6.92 --> http://purlz.org/ontology/ which, in turn, dereferences to the appropriate RDF or other resources....

<mscottm> harold: CDM is a metadata interchange format for clinical trial data from CDISC (there's another CDM too..)

<mscottm> NCBO is looking at the type of RDF that they will serve, looking at SKOS..

Also, CTS2 is looking at SKOS/RDF rendering of the LexGrid rendering of UMLS, SNOMED, etc.

So that is another path that may acutally work slightly better than each community coming up with their own RDF

We are working with Nigam and Natasha on this as well.

NCBO == Stanford + Mayo

<mscottm> great!

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/02/22 17:55:56 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: solbrig
Inferring Scribes: solbrig

WARNING: No "Topic:" lines found.

Default Present: HaroldSolbrig, mscottm, EricP, John_Madden
Present: HaroldSolbrig mscottm EricP John_Madden

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 22 Feb 2010
Guessing minutes URL: http://www.w3.org/2010/02/22-hcls2-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]