You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
772 lines
29 KiB
772 lines
29 KiB
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
|
|
<html lang='en' xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
|
|
<head>
|
|
<meta name="generator" content=
|
|
"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
|
|
|
|
<title>MMSEM Athens F2F Meeting, December 8-9 2006 -- 9 Dec
|
|
2006</title>
|
|
<link type="text/css" rel="STYLESHEET" href=
|
|
"http://www.w3.org/StyleSheets/base.css" />
|
|
<link type="text/css" rel="STYLESHEET" href=
|
|
"http://www.w3.org/StyleSheets/public.css" />
|
|
<link type="text/css" rel="STYLESHEET" href=
|
|
"http://www.w3.org/2004/02/minutes-style.css" />
|
|
<meta content="MMSEM Athens F2F Meeting, December 8-9 2006" name=
|
|
"Title" />
|
|
<meta content="text/html; charset=us-ascii" http-equiv=
|
|
"Content-Type" />
|
|
</head>
|
|
|
|
<body>
|
|
<p><a href="http://www.w3.org/"><img src=
|
|
"http://www.w3.org/Icons/w3c_home" alt="W3C" border="0" height=
|
|
"48" width="72" /></a></p>
|
|
|
|
<h1>- DRAFT -</h1>
|
|
|
|
<h1>MMSEM Athens F2F Meeting, December 8-9 2006</h1>
|
|
|
|
<h2>9 Dec 2006</h2>
|
|
|
|
<p><a href=
|
|
'http://lists.w3.org/Archives/Public/public-xg-mmsem/2006Dec/0014.html'>
|
|
Agenda</a></p>
|
|
|
|
<h2><a name="attendees" id="attendees">Attendees</a></h2>
|
|
|
|
<div class="intro">
|
|
<dl>
|
|
<dt>Present</dt>
|
|
|
|
<dd>Vassilis, Susanne_Boll, Suzanne_Little, Sophia, Stamatia,
|
|
Erik, Michael, Thomas, Ioannis, Raphael, Jeff, Thierry,
|
|
Oscar</dd>
|
|
|
|
<dt>Regrets</dt>
|
|
|
|
<dt>Chair</dt>
|
|
|
|
<dd>Jeff, Raphael</dd>
|
|
|
|
<dt>Scribe</dt>
|
|
|
|
<dd>Raphael</dd>
|
|
</dl>
|
|
</div>
|
|
|
|
<h2>Contents</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
<a href="#agenda">Topics</a>
|
|
|
|
<ol>
|
|
<li><a href="#item01">Algorithm Use Case (Suzanne
|
|
Little)</a></li>
|
|
|
|
<li><a href="#item02">Tagging Use Case (Tomas)</a></li>
|
|
|
|
<li><a href="#item03">Breaking out session</a></li>
|
|
|
|
<li><a href="#item04">Breakout Session, Group JEFF</a></li>
|
|
|
|
<li><a href="#item05">Breakout Session, Group
|
|
Vassilis</a></li>
|
|
|
|
<li><a href="#item06">Debrieffing session</a></li>
|
|
|
|
<li><a href="#item07">Deliverable about
|
|
Interoperability</a></li>
|
|
|
|
<li><a href="#item08">Other Deliverables</a></li>
|
|
|
|
<li><a href="#item09">Future Plans</a></li>
|
|
|
|
<li><a href="#item10">AOB</a></li>
|
|
</ol>
|
|
</li>
|
|
|
|
<li><a href="#ActionSummary">Summary of Action Items</a></li>
|
|
</ul>
|
|
<hr />
|
|
|
|
<div class="meeting">
|
|
<p class='phone'> </p>
|
|
|
|
<p class='phone'> </p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Scribe: Raphael</p>
|
|
|
|
<p class='phone'>Scribenick raphael</p>
|
|
|
|
<h3 id="item01">Algorithm Use Case (Suzanne Little)</h3>
|
|
|
|
<p class='phone'><cite>Problem:</cite> it is difficult for
|
|
users and applications to identify, manage and apply algorithms
|
|
for image analysis</p>
|
|
|
|
<p class='phone'>Interoperability issues:</p>
|
|
|
|
<p class='phone'>1/ low level: data formats and algorithms,
|
|
their transition and selection</p>
|
|
|
|
<p class='phone'>2/ high level: defining domain semantics,
|
|
learning from similar problems</p>
|
|
|
|
<p class='phone'><cite>Solution:</cite> an algorithm
|
|
ontology</p>
|
|
|
|
<p class='phone'>The algorithm ontology should consist of
|
|
information such as: name, informal natural language
|
|
description, formal description, input format, output format,
|
|
goal of the algorithm, example media prior and after the
|
|
application, etc.</p>
|
|
|
|
<p class='phone'><cite>Challenges:</cite> to articulate and
|
|
qualify the visual result of applying algorithms, to integrate
|
|
and harmonize the ontologies, to reason with and apply the
|
|
knowledge in the algorithm ontology</p>
|
|
|
|
<p class='phone'><cite>Technology:</cite> potential overlap
|
|
with web service choregraphy domain</p>
|
|
|
|
<p class='phone'><cite>Problem:</cite> see wiki page (pneumo
|
|
thorax)</p>
|
|
|
|
<p class='phone'>Suzanne describe the outline of a possible
|
|
solution</p>
|
|
|
|
<p class='phone'>The use case focus on high-level
|
|
interoperability</p>
|
|
|
|
<p class='phone'>The driving question: how to describe media
|
|
analysis algorithms ?</p>
|
|
|
|
<p class='phone'><cite>Michael:</cite> the problem reminds me
|
|
the pre-condition / post-condition parameters in the software
|
|
enginnering problems ?<br />
|
|
... why not specifying the possible and impossible chaining of
|
|
various algorithms ?</p>
|
|
|
|
<p class='phone'><cite>Suzanne:</cite> yes, exactly, this is
|
|
where we would like to go</p>
|
|
|
|
<p class='phone'><cite>Susanne:</cite> I see links with my
|
|
problems</p>
|
|
|
|
<p class='phone'><cite>Suzanne:</cite> it is about the
|
|
description of a workflow at a very abstract level<br />
|
|
... we can work in the medical domain, and/or in the
|
|
manufacturer workflow</p>
|
|
|
|
<p class='phone'><cite>Oscar:</cite> what is the state of the
|
|
art ?</p>
|
|
|
|
<p class='phone'>Suzanne mention some work I didn't get ...</p>
|
|
|
|
<p class='irc'><<cite>ocelma</cite>> some people from
|
|
Russia...</p>
|
|
|
|
<p class='phone'><cite>Raphael:</cite> seems very close to the
|
|
SW web services<br />
|
|
... proposel also to take a look at the Multimedia Ontology
|
|
made of several design patterns ... among them, an algorithm
|
|
design pattern</p><a name="action01" id="action01"></a>
|
|
|
|
<p class='irc'><<cite>scribe</cite>>
|
|
<strong>ACTION:</strong> Raphael to send the paper describing
|
|
this work to Suzanne [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action01">http://www.w3.org/2006/12/09-mmsem-minutes.html#action01</a>]</p>
|
|
|
|
<p class='phone'>Sophia mention an interesting work about an
|
|
application toolbow where the user can select some algorithm to
|
|
do feature extraction on music</p><a name="action02" id=
|
|
"action02"></a>
|
|
|
|
<p class='irc'><<cite>scribe</cite>>
|
|
<strong>ACTION:</strong> Sophia to find and send a
|
|
documentation about this work [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action02">http://www.w3.org/2006/12/09-mmsem-minutes.html#action02</a>]</p>
|
|
|
|
<p class='phone'><cite>Ioannis:</cite> I present an image
|
|
analysis use case, with some similarities<br />
|
|
... warn about the huge number of parameters that are generally
|
|
use in image analysis<br />
|
|
... sounds too ambitious for me<br />
|
|
... propose to focus on a single (simple) application</p>
|
|
|
|
<p class='phone'><cite>Suzanne:</cite> I tend to agree<br />
|
|
... difference between the complexity of the algorithm and the
|
|
generic usefulness of such an ontology</p>
|
|
|
|
<p class='phone'><cite>Ioannis:</cite> what is useful is a
|
|
framework that could allow to chain algorithms, and do
|
|
optimization</p>
|
|
|
|
<p class='phone'><cite>Suzanne:</cite> we would like to do that
|
|
... close to what do the Web Services</p>
|
|
|
|
<p class='phone'><cite>Vassilis:</cite> is it worth to merge
|
|
the use case</p>
|
|
|
|
<p class='phone'>Timeline ?</p>
|
|
|
|
<p class='phone'><cite>Suzanne:</cite> don't want too
|
|
specific</p><a name="action03" id="action03"></a>
|
|
|
|
<p class='irc'><<cite>scribe</cite>>
|
|
<strong>ACTION:</strong> Suzanne, Massimo to further exemplify
|
|
and sketch the solution: what will be needed to model in the
|
|
ontology, and how it would be used [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action03">http://www.w3.org/2006/12/09-mmsem-minutes.html#action03</a>]</p>
|
|
|
|
<p class='phone'><cite>Issue:</cite> merge of these two use
|
|
cases ?</p>
|
|
|
|
<p class='phone'><cite>Proposal:</cite> the two use cases
|
|
continue on their own</p>
|
|
|
|
<p class='phone'>Sophia will join Ioannis to work on the
|
|
semantic retrieval use case</p>
|
|
|
|
<h3 id="item02">Tagging Use Case (Tomas)</h3>
|
|
|
|
<p class='irc'><<cite>mhausenblas</cite>> ScribeNick:
|
|
mhausenblas</p>
|
|
|
|
<p class='phone'><cite>Thomas:</cite> Demo using flickr,
|
|
del.icio.us, YouTube, Technorati<br />
|
|
... e.g. there might be a user Raphael that has some pieces on
|
|
flickr<br />
|
|
... other stuff (video) might be located on YouTube<br />
|
|
... but not connected<br />
|
|
... OR there are two users<br />
|
|
... using different platforms<br />
|
|
... may share a location, event, etc. - how to share them
|
|
accross system boundaries<br />
|
|
... Proposed solution: ontology describing personomies and
|
|
tagging<br />
|
|
... platforms offer a Web-API, helps accessing it<br />
|
|
... Status:<br />
|
|
... no standards given<br />
|
|
... tagging ontology (Koblenz, Newman)<br />
|
|
... SKOS<br />
|
|
... we opt to go for SKOS</p>
|
|
|
|
<p class='phone'>Thomas shows a RDF graph from the SKOS
|
|
guide</p>
|
|
|
|
<p class='phone'><cite>Thomas:</cite> We use SKOS to model
|
|
tagging<br />
|
|
... also personomie terms are somehow available in SKOS<br />
|
|
... multilingua aspects<br />
|
|
... learn relations between tags</p>
|
|
|
|
<p class='phone'><cite>Jeff:</cite> Common sense reasoning?</p>
|
|
|
|
<p class='phone'><cite>Thomas:</cite> we can relate different
|
|
modalities</p>
|
|
|
|
<p class='phone'><cite>Michael:</cite> Relation to Tom Grubers
|
|
approach?</p>
|
|
|
|
<p class='phone'><cite>Thomas:</cite> Work in parallel</p>
|
|
|
|
<p class='phone'><cite>Raphael:</cite> Explains connection
|
|
between the lightweight way and the SKOS schemes<br />
|
|
... one SKOS schema per user accross all systems</p>
|
|
|
|
<p class='phone'><cite>Susanne:</cite> How to integrate with
|
|
the platforms _I_ use ?</p>
|
|
|
|
<p class='phone'>Raphael demos the "Personomy Manager"</p>
|
|
|
|
<p class='phone'><cite>scribe:</cite> currently flickr and
|
|
del.icio.us are supported<br />
|
|
... available operations: Config, Tag cloud (per platform or
|
|
merged)<br />
|
|
... operations cntd: download personomy<br />
|
|
... how to tag a resource is just as easy<br />
|
|
... enter URL, descr., tags, etc.<br />
|
|
... everything done within the PM, using the Web-API of the
|
|
diverse platform</p>
|
|
|
|
<p class='phone'><cite>Susanne:</cite> Usability issues. How
|
|
about "reusing" flickr, etc. ?</p>
|
|
|
|
<p class='phone'><cite>Raphael:</cite> Back to interop issue
|
|
...<br />
|
|
... guess relations between tags<br />
|
|
... SKOS enables to do "small things" like broader, wider,
|
|
etc.<br />
|
|
... SKOS is not for the interop issue</p>
|
|
|
|
<p class='phone'><cite>Thomas:</cite> the ontology makes the
|
|
tagging explicit<br />
|
|
... so, interop is somehow supported with this</p>
|
|
|
|
<p class='phone'><cite>Raphael:</cite> The ontology focus on:
|
|
what is a tag, a user, etc.</p>
|
|
|
|
<p class='phone'><cite>Suzanne:</cite> How to do merging when
|
|
having different organisational/structural patterns</p>
|
|
|
|
<p class='phone'><cite>Raphael:</cite> Cf. work at Yahoo that
|
|
looks at tag characteristics<br />
|
|
... have a look at <a href=
|
|
"http://rawsugar.com/index.faces">http://rawsugar.com/index.faces</a>
|
|
as well</p>
|
|
|
|
<p class='irc'><<cite>ocelma</cite>> Re www2006 tagging
|
|
workshop::<a href=
|
|
"http://www.rawsugar.com/www2006">http://www.rawsugar.com/www2006</a></p>
|
|
|
|
<p class='phone'><cite>Raphael:</cite> The proposed solution
|
|
will contain the common format (SKOS-based), "core"-ontology,
|
|
features</p>
|
|
|
|
<h3 id="item03">Breaking out session</h3>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> The participants
|
|
split into 2 groups and meet outside on the sunny terrasse (in
|
|
front of the Parthenon</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> ... to discuss the
|
|
commonalities between the various use cases</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> ... and see how
|
|
they are related to, how they can be clustered, etc.</p>
|
|
|
|
<h3 id="item04">Breakout Session, Group JEFF</h3>
|
|
|
|
<p class='phone'>Discussion on a "common framework" that
|
|
support multi modalities</p>
|
|
|
|
<p class='phone'>propose to use RDF/XML as base</p>
|
|
|
|
<p class='phone'>core ontology may also contain guidelines
|
|
how-to use</p>
|
|
|
|
<p class='phone'><cite>Thomas:</cite> feasible to align the
|
|
concepts in the UC used</p>
|
|
|
|
<p class='phone'><cite>Suzanne:</cite> from ABC model
|
|
experience, might yield some 10 classes</p>
|
|
|
|
<p class='phone'><cite>Jeff:</cite> break it down now, make it
|
|
concrete<br />
|
|
... good to base on existing Standards (RDF, bit-of-OWL,
|
|
etc.)<br />
|
|
... SKOS sitll not a standard</p>
|
|
|
|
<p class='phone'><cite>Thomas:</cite> Concerns about
|
|
reinventing the wheel</p>
|
|
|
|
<p class='phone'><cite>Jeff:</cite> Our vocabulary should be
|
|
more domain-specific</p>
|
|
|
|
<p class='phone'><cite>Suzanne:</cite> We got to be careful,
|
|
cf. MPEG-7 concepts, etc.</p>
|
|
|
|
<p class='phone'>Group now puts each of the 7 UC on a card
|
|
(Music, News, Authoring, Algorithm, Retrieval, Photo,
|
|
Tagging)</p>
|
|
|
|
<p class='phone'><cite>scribe:</cite> discusses common
|
|
characteristics, goals, solutions</p>
|
|
|
|
<p class='phone'>We now try to put UC into certain
|
|
categories</p>
|
|
|
|
<p class='phone'><cite>scribe:</cite> e.g.: Modality (audio,
|
|
vision, AV, etc.), Retrieval/Process, Solution-Exist,</p>
|
|
|
|
<p class='phone'><cite>Michael:</cite> Might be good idea to
|
|
use the categories proposed in <a href=
|
|
"http://www.w3.org/2005/Incubator/mmsem/wiki/Vocabularies#head-5db084087806d9105c4f4ebd094b517b20913c5e">
|
|
http://www.w3.org/2005/Incubator/mmsem/wiki/Vocabularies#head-5db084087806d9105c4f4ebd094b517b20913c5e</a></p>
|
|
|
|
<p class='irc'><<cite>scribe</cite>> new proposal: 3
|
|
layers (concepts/process, medium/instances, applications
|
|
domains)</p>
|
|
|
|
<h3 id="item05">Breakout Session, Group Vassilis</h3>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Oscar, Raphael,
|
|
Susanne, Giorgos, Thierry, Erik, Ioannis</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Picture showing how
|
|
the use cases can be grouped together</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Common framework:
|
|
describre how all these use cases can work together ... towards
|
|
integration of RDF data</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Commonalities:
|
|
decomposition of an image vs temporal sequence of audio</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> ... all use cases
|
|
make use of some common schema</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> ... needs
|
|
ontologies to model some knowledge</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> ... integration of
|
|
data among the use cases</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Some issues:
|
|
cultural heritage use case ? liaison with Content labelling ?
|
|
SKOS vs OWL ?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Consensus on
|
|
interoperability: common ontology ? using SKOS as a glue?</p>
|
|
|
|
<h3 id="item06">Debrieffing session</h3>
|
|
|
|
<p class='phone'>addendum to "Breakout Group JEFF":</p>
|
|
|
|
<p class='phone'><cite>scribe:</cite> participants were: Jeff,
|
|
Thomas, Stamatia, Suzanne Little, Sophia, Michael</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Drawing of two
|
|
schemas !</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> There are pretty
|
|
much the same thing</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Common
|
|
framework:</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Syntax: RDF</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Common schema /
|
|
ontology</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Schema / ontology
|
|
harmonization and extension</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Guidelines: what to
|
|
use in which context ?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Interoperability
|
|
problems between layer</p>
|
|
|
|
<h3 id="item07">Deliverable about Interoperability</h3>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Table of
|
|
Contents:</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Section 1:
|
|
Introduction / Motivations</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Section 2: Summary
|
|
of the interoperability problems of the use cases</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> ... the schemas
|
|
drawn, categorization of the use cases</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Do we need a state
|
|
of the art ?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Jeff: could be an
|
|
Appendix, mentionning the related work</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Suzanne: could be
|
|
in the vocabularies / tools / resources pages</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> ... and just refer
|
|
from the document</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Vassilis: issue
|
|
about multilinguility ?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Could be an open
|
|
issue</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Section 3: Use
|
|
cases</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Section 4: Common
|
|
Framework (putting all together)</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Section 5: Open /
|
|
Other problems</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> For every layer:
|
|
what are the similarities between the use cases ?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Jeff: section 3 and
|
|
4 or the other way around ?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Having a scenario
|
|
for putting all together ...</p><a name="action04" id=
|
|
"action04"></a>
|
|
|
|
<p class='irc'><<cite>raphael</cite>>
|
|
<strong>ACTION:</strong> Vassilis update the structure of the
|
|
deliverable and fill it in a XG report template, HTML document
|
|
in our W3C space [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action04">http://www.w3.org/2006/12/09-mmsem-minutes.html#action04</a>]</p><a name="action05"
|
|
id="action05"></a>
|
|
|
|
<p class='irc'><<cite>raphael</cite>>
|
|
<strong>ACTION:</strong> Jeff to find the tool to move a wiki
|
|
page into an HTML page [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action05">http://www.w3.org/2006/12/09-mmsem-minutes.html#action05</a>]</p><a name="action06"
|
|
id="action06"></a>
|
|
|
|
<p class='irc'><<cite>raphael</cite>>
|
|
<strong>ACTION:</strong> Authors of each use case to fill the
|
|
summary of their interoperability problems [recorded in
|
|
<a href="http://www.w3.org/2006/12/09-mmsem-minutes.html#action06">
|
|
http://www.w3.org/2006/12/09-mmsem-minutes.html#action06</a>]</p><a name="action07"
|
|
id="action07"></a>
|
|
|
|
<p class='irc'><<cite>raphael</cite>>
|
|
<strong>ACTION:</strong> Vassilis and Jeff to start the Common
|
|
Framework [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action07">http://www.w3.org/2006/12/09-mmsem-minutes.html#action07</a>]</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Giorgos to help on
|
|
this Common Framework</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Open Issue:
|
|
Multilinguality ? Multmedia Authoring ?</p>
|
|
|
|
<h3 id="item08">Other Deliverables</h3><a name="action08" id=
|
|
"action08"></a>
|
|
|
|
<p class='irc'><<cite>raphael</cite>>
|
|
<strong>ACTION:</strong> Rapahel to finish the Image Annotation
|
|
on the Semantic Web Deliverable [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action08">http://www.w3.org/2006/12/09-mmsem-minutes.html#action08</a>]</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Approved: to have
|
|
an MPEG-7 document</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Issue: do we want a
|
|
frozen version of the Vocabularies document ?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> YES</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Vassilis: all
|
|
vocabularies used in the use case should be described HERE
|
|
!</p><a name="action09" id="action09"></a>
|
|
|
|
<p class='irc'><<cite>raphael</cite>>
|
|
<strong>ACTION:</strong> all use case authors to check if their
|
|
vocabularies are described in this page ... [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action09">http://www.w3.org/2006/12/09-mmsem-minutes.html#action09</a>]</p><a name="action10"
|
|
id="action10"></a>
|
|
|
|
<p class='irc'><<cite>raphael</cite>>
|
|
<strong>ACTION:</strong> Michael to make testing how to
|
|
transfert the wiki page into an XG report template [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action10">http://www.w3.org/2006/12/09-mmsem-minutes.html#action10</a>]</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Schedule: be in
|
|
position of reviewing a frozen version in End of February</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Michael: proposal
|
|
to merge resource and tools pages</p>
|
|
|
|
<p class='phone'><a href=
|
|
"http://ontoworld.org/wiki/Upcoming_events">http://ontoworld.org/wiki/Upcoming_events</a></p><a name="action11"
|
|
id="action11"></a>
|
|
|
|
<p class='irc'><<cite>raphael</cite>>
|
|
<strong>ACTION:</strong> Sophia to be the main editor of a
|
|
merge between the vocabularies and resources page [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action11">http://www.w3.org/2006/12/09-mmsem-minutes.html#action11</a>]</p>
|
|
|
|
<h3 id="item09">Future Plans</h3>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Leave the telecon
|
|
as it is</p><a name="action12" id="action12"></a>
|
|
|
|
<p class='irc'><<cite>raphael</cite>>
|
|
<strong>ACTION:</strong> chairs to give hints how it could be
|
|
possible to join the telecon for free [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action12">http://www.w3.org/2006/12/09-mmsem-minutes.html#action12</a>]</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> and provide more
|
|
phone numbers ...</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> having more
|
|
scribing turning</p>
|
|
|
|
<p class='phone'><a href=
|
|
"http://www.w3.org/2001/sw/sweo/">http://www.w3.org/2001/sw/sweo/</a></p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Next F2F ?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Beginning of April
|
|
?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Transition to a WG
|
|
?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Jeff shows the
|
|
ususal W3C process diagramm</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> What are the
|
|
advantages to move to Rec Track ?</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> An XG report has no
|
|
W3C endorsment</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Recommendation
|
|
means Specifications or Guidelines ...</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Michael: we still
|
|
have till March 2007 to prepare such a document</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Vassilis: many work
|
|
to do</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> ... the WG could be
|
|
a good idea, but make the work before</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Possibility to have
|
|
a F2F in April 2007</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> ... could be also a
|
|
workshop to start a WG</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Jeff and Raphael
|
|
will report on the teleconference with the SW Coordination
|
|
Activity</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> Week of 16 April
|
|
for a possible of F2F</p>
|
|
|
|
<h3 id="item10">AOB</h3>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> no ... apart to
|
|
make a photo all together !</p>
|
|
|
|
<p class='irc'><<cite>raphael</cite>> We close the
|
|
meeting</p>
|
|
</div>
|
|
|
|
<h2><a name="ActionSummary" id="ActionSummary">Summary of Action
|
|
Items</a></h2><!-- Action Items -->
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> all use case
|
|
authors to check if their vocabularies are described in this page
|
|
... [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action09">http://www.w3.org/2006/12/09-mmsem-minutes.html#action09</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Authors of each
|
|
use case to fill the summary of their interoperability problems
|
|
[recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action06">http://www.w3.org/2006/12/09-mmsem-minutes.html#action06</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> chairs to give
|
|
hints how it could be possible to join the telecon for free
|
|
[recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action12">http://www.w3.org/2006/12/09-mmsem-minutes.html#action12</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Jeff to find the
|
|
tool to move a wiki page into an HTML page [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action05">http://www.w3.org/2006/12/09-mmsem-minutes.html#action05</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Michael to make
|
|
testing how to transfert the wiki page into an XG report template
|
|
[recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action10">http://www.w3.org/2006/12/09-mmsem-minutes.html#action10</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Rapahel to finish
|
|
the Image Annotation on the Semantic Web Deliverable [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action08">http://www.w3.org/2006/12/09-mmsem-minutes.html#action08</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Raphael to send
|
|
the paper describing this work to Suzanne [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action01">http://www.w3.org/2006/12/09-mmsem-minutes.html#action01</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Sophia to be the
|
|
main editor of a merge between the vocabularies and resources
|
|
page [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action11">http://www.w3.org/2006/12/09-mmsem-minutes.html#action11</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Sophia to find
|
|
and send a documentation about this work [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action02">http://www.w3.org/2006/12/09-mmsem-minutes.html#action02</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Suzanne, Massimo
|
|
to further exemplify and sketch the solution: what will be needed
|
|
to model in the ontology, and how it would be used [recorded in
|
|
<a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action03">http://www.w3.org/2006/12/09-mmsem-minutes.html#action03</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Vassilis and Jeff
|
|
to start the Common Framework [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action07">http://www.w3.org/2006/12/09-mmsem-minutes.html#action07</a>]<br />
|
|
|
|
<strong>[NEW]</strong> <strong>ACTION:</strong> Vassilis update
|
|
the structure of the deliverable and fill it in a XG report
|
|
template, HTML document in our W3C space [recorded in <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html#action04">http://www.w3.org/2006/12/09-mmsem-minutes.html#action04</a>]<br />
|
|
|
|
<br />
|
|
[End of minutes]<br />
|
|
<hr />
|
|
|
|
<address>
|
|
Minutes formatted by David Booth's <a href=
|
|
"http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm">
|
|
scribe.perl</a> version 1.127 (<a href=
|
|
"http://dev.w3.org/cvsweb/2002/scribe/">CVS log</a>)<br />
|
|
$Date: 2006/12/09 14:10:42 $
|
|
</address>
|
|
|
|
<div class="diagnostics">
|
|
<hr />
|
|
|
|
<h2>Scribe.perl diagnostic output</h2>[Delete this section
|
|
before finalizing the minutes.]<br />
|
|
<pre>
|
|
This is scribe.perl Revision: 1.127 of Date: 2005/08/16 15:12:03
|
|
Check for newer version at <a href=
|
|
"http://dev.w3.org/cvsweb/~checkout~/2002/scribe/">http://dev.w3.org/cvsweb/~checkout~/2002/scribe/</a>
|
|
|
|
Guessing input format: RRSAgent_Text_Format (score 1.00)
|
|
|
|
Succeeded: s/to/too/
|
|
Succeeded: s/Sussane/Susanne/
|
|
Succeeded: s/look/looks/
|
|
Found Scribe: Raphael
|
|
Inferring ScribeNick: raphael
|
|
WARNING: No scribe lines found matching previous ScribeNick pattern: <mhausenblas> ...
|
|
Found ScribeNick: mhausenblas
|
|
ScribeNicks: mhausenblas, raphael
|
|
Present: Vassilis Susanne_Boll Suzanne_Little Sophia Stamatia Erik Michael Thomas Ioannis Raphael Jeff Thierry Oscar
|
|
Agenda: <a href=
|
|
"http://lists.w3.org/Archives/Public/public-xg-mmsem/2006Dec/0014.html">http://lists.w3.org/Archives/Public/public-xg-mmsem/2006Dec/0014.html</a>
|
|
|
|
WARNING: No date found! Assuming today. (Hint: Specify
|
|
the W3C IRC log URL, and the date will be determined from that.)
|
|
Or specify the date like this:
|
|
<dbooth> Date: 12 Sep 2002
|
|
|
|
Guessing minutes URL: <a href=
|
|
"http://www.w3.org/2006/12/09-mmsem-minutes.html">http://www.w3.org/2006/12/09-mmsem-minutes.html</a>
|
|
People with action items: all authors case chairs each jeff massimo michael of rapahel raphael sophia suzanne use vassilis
|
|
|
|
WARNING: IRC log location not specified! (You can ignore this
|
|
warning if you do not want the generated minutes to contain
|
|
a link to the original IRC log.)
|
|
|
|
|
|
</pre>[End of <a href=
|
|
"http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm">
|
|
scribe.perl</a> diagnostic output]
|
|
</div>
|
|
</body>
|
|
</html>
|