W3C

- DRAFT -

SV_MEETING_TITLE

2 Nov 2005

See also: IRC log

Attendees

Present
Chris_Halaschek-Wiener, Jacco, Raphael, Giorgos_Stamou, Nikolaos_Simou, Vassilis
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Jacco

Contents


 

busy ...

:-)

<chalaschek> i know the feeling :)

This is my last day before traveling to Galway...

<Raphael> hi Chris

<chalaschek> hi Rapheal

hi vassilis

Vassilis, the logs and minutes will be at http://www.w3.org/2005/11/02-MMTF-irc

vassilis, we get classic music from your phone.

<Raphael> list attendees

<Raphael> i will scribe

<Raphael> Jacco: ALL: read carefully the full document and the use cases

<Raphael> ACTION: ALL send feedback to the TF about the document, use cases, solutions ... [recorded in http://www.w3.org/2005/11/02-MMTF-minutes.html#action01]

<Giorgos> Surprised! I have a public wireless in my home!

<Raphael> Monday in Galway: TF have a dinner :-)

<Raphael> Second deliverable structure ...

giorgos: propose to split syntactic and semantic interoperability

Jacco and Raphael: how much will be in the syntax part?

is it useful to make this separation

giorgos, yes, conversion is one thing but alignment still needs to be done

syntax issues: from owl to non-owl, and vice versa

nikolaos: only images?

Jacco: yes, but we can discuss all more general standards to the extent they apply also to images

Raphael: borderline between feasability study and make conversion tools ourself

?

<vasilis> jacco it was vassilis taling about interoperability

<vasilis> not nikos

Giorgos: jjc once stated he could help with conversion tools, we should ask him in Galway

vasilis, sorry for the mix up

vasilis: previous work and projects on semantic interoperability

Chris: hard to scope

vasilis: link on resource pages

giorgos: mention also in intro

jacco: do we need use cases for 2nd deliverable?

vasilis: yes ,the issues are different for different domains

Giorgos: 2nd deliverable is more abstract, we should not go into the individual tools
... we do not have time to do more, unless we have more work

Raphael, ok, we can discuss this further in Galway. It is still not clear to me what is a good depth for the 2nd document

<vasilis> Jacco: prepare a 15 minuts talk about the deliverable and then focus on the reviews

<vasilis> Jacco: it is beeter to hove one presentation

<vasilis> intro + deliverable

<Raphael> ACTION: Jacco prepares the slides for Galway [recorded in http://www.w3.org/2005/11/02-MMTF-minutes.html#action02]

RSSagent, draft minutes

RSSAgent, draft minutes

RSSAgent, format minutes

Summary of Action Items

[NEW] ACTION: ALL send feedback to the TF about the document, use cases, solutions ... [recorded in http://www.w3.org/2005/11/02-MMTF-minutes.html#action01]
[NEW] ACTION: Jacco prepares the slides for Galway [recorded in http://www.w3.org/2005/11/02-MMTF-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2005/11/02 14:02:41 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.127  of Date: 2005/08/16 15:12:03  
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: Jacco
Inferring Scribes: Jacco

WARNING: No "Topic:" lines found.

Default Present: Chris_Halaschek-Wiener, Jacco, Raphael, Giorgos_Stamou, Nikolaos_Simou, Vassilis
Present: Chris_Halaschek-Wiener Jacco Raphael Giorgos_Stamou Nikolaos_Simou Vassilis

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: 2 Nov 2005
Guessing minutes URL: http://www.w3.org/2005/11/02-MMTF-minutes.html
People with action items: all feedback jacco send

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]