W3C

- DRAFT -

SV_MEETING_TITLE

03 Dec 2009

See also: IRC log

Attendees

Present
John_Madden, +1.707.321.aaaa, nalbarr, EricP.a
Regrets
Chair
SV_MEETING_CHAIR
Scribe
nalbarr

Contents


 

 

<johnM> +1.707.321.aaaa is Alan

<johnM> zakim. +1.847.832.aabb is nalbarr

nalbarr can scribe if you like

jenny has icd10 in skos

might be exposed in talis later?

jmadden: may propose some new projects next call

mscottm, ericp: coordination of thurs calls on hcls2# may be challenging with other conference calls

<ericP> monday 17:00Z (12:00 us east cost)

mscottm: proposes mon move to 12 est / 11 cst

start on 12/14

<mscottm> http://esw.w3.org/topic/HCLSIG/Terminology/SNOMEDisa

all: proposing letter of support for kp/peter hendler's work

np.

<mscottm> from Peter Hendler: I'm applying for funding to officially move SNOMED to OWL at Kaiser. Most of the money will be needed for the tooling. I've proved it can be done (very slowly and painfully) with Protege, but now we need a better tool for handling this in production.

<mscottm> also: I'll keep you posted. If this does get funded, then one side effect would be that the IHTSDO toolbench would become an enterprise class tool for large OWL ontologies.

jmadden: raises challenge of sct to owl/owl2 being more of modeling issue versus technical
... proposes a focused use cases in peter's domain speciality for differential diagnosis

ericp: ... use cases should be focus on soundness of conclusions... versus technical complexity/scability/classification

jmadden: ...more towards abox / instances side versus tbox only focus
... rdfs level is really the level of snomed ct modelinng
... rdfs/skos direction more usable...

ericp: peter did use negative assertions (above rdfs)

jmadden: wants to avoid heavyweight approach... to convert all snomed ct axioms, etc.

alan: leverage peter's pragmatic and practical approach for target use cases

jmadden: there is no "one" owl view of snomed ct; could be many perspectives

ericp: need to review proposal in order to draft letter of support

jmadden: make sure efforts are shareable within w3c

mscottm: there is a possibility of aligning with ihtsdo workbench direction?

ericp: provides w3c sounding board; technical guidance; offer to have a demonstrator

jmadden: need to clarify the scope and deliverable and relationship to tools

mscottm: will engage peter on specifics

jmadden/erip: draft letter together...

<ericP> eric@w3.org

<ericP> allen.hobbs@ap.org

<mscottm> http://dev.adaptivedisclosure.org/search/

please draft minutes

ericp... i need the incantatios

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009/12/03 15:58:34 $

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: nalbarr
Inferring Scribes: nalbarr

WARNING: No "Topic:" lines found.

Default Present: John_Madden, +1.707.321.aaaa, nalbarr, EricP.a
Present: John_Madden +1.707.321.aaaa nalbarr EricP.a

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: 03 Dec 2009
Guessing minutes URL: http://www.w3.org/2009/12/03-hcls2-minutes.html
People with action items: 

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]