See also: IRC log
<scribe> scribenick: jackjansen
raphael: opens meeting and greets
... Comments on the minutes?
raphael: will create wiki page
capturing current email discussion
... What's the currrent status of use cases?
... start with media annotation. Sylvia?
Sylvia: not much progress,
... Did look at accessibility issues. Results into wiki TBD.
Sylvia: For the moment, can be seen at another wiki, url here in the chat.
<mhausenblas> Michael: Silvia, refer to -> http://blog.gingertech.net/2008/09/27/demo-of-new-html5-features/ Demo of new HTML5 features
raphael: next use case, media delivery. Davey?
Davey: not much yet, will do soon.
raphael: only server side issue?
Sylvia: no, also protocol (in addtion to client and server)
michael: is client/server important?
<Yves> you also have to check if the client is responsible for crafting a specific request, and not just a regular HTTP request with a carefully crafted URI for the server
<Yves> (ie: delegate processing on the two sides, or only server-side)
<raphael> Jack: distinguish between functionalities and implementations
<raphael> Silvia: HTTP is ok as protocol ... question is rather working on the headers
Yves: does this mean we're doing a protocol or not?
Silvia: open issue.
Michael: need to involve TAG in the process early.
raphael: will take care of
... next use case, media linking.
Michael: also fine-grained linking, see posted url.
<Yves> I wonder, once we have a URI to define a media fragment, what is the difference bewteen a link and a bookmark (which is a link from a page, or an internal db)
Michael: it's not only about humans, but also agents (?). Bookmarks for humans, links for agents.
raphael: shall we separate the two use cases, then?
Sylvia: fits to media playlist UC.
raphael: merge the two?
jackjansen: aren't these mashups?
<raphael> Yves: not merging, but put under the same umbrela Media Linking and Media Playlist
Sylvia: playlists are simpler than mashups.
Michael: ca people think about whether UCs are for humans or computerrs, please?
raphael: who takes responsibility for search UC and browse UC?
Sylvia: maybe later, not now.
Raphael: on to photobook UC. Erik isn't here, Davy?
Davy: no real news yet.
raphael: map and multires
... Investigating how this works in current technology, expect results next teleconf.
... audio UCs, no volunteers yet.
... but karaoka is like annotation.
... video UCs.
Sylvia: not looked into browser UC yet.
raphael: next agenda point, state of the art.
Yves: how should we structure this?
raphael: don't know yet.
Michael: common way to describe things will make life easier in future.
jackjansen: how about initially structuring this from a source-technology point of view? With one person per technology?
... Jack can do SMIL, Sylvia CMML.
Sylvia: also worked on MPEG21.
Davy: can also look at mpeg21.
raphael: I can look at SVG.
<mhausenblas> Michael: re HTTP and URI I can take care
<Yves> and I will help as well
Sylvia: have http ideas as well.
Yves: me too.
Sylvia: let's try and have some data by f2f.
raphael: good idea.
... I will look at key issues, create page (?)
Sylvia: have created page about what a video resource is.
<nessy> already created that in the glossary
Michael: like the drawing.
<Yves> Yves also likes the drawing :)
raphael: closing meeting. Next time will go into UCs deeper.