Re: Review: Use Case & Requirements Draft

>
> >>> * Section 1.4:
> >>>  - This use case is again for me an application of 1.1, that is this
> >>time
> >>> linking for recomposing (making playlist)
> >>
> >>Recompositing poses very different challenges to an application that
> >>just playback. I can see where you come from - for you it is just a
> >>piece of content delivered to a user agent and you don't really care
> >>what the user agent does with it. However, I am looking at use cases
> >>from the user's POV. A user would not regard watching a video as the
> >>same use case as editing clips together. I am just weary that we might
> >>oversee some things if we throw these use cases together too much.
> >
> > Note that there is another issue with the recomposition of media
> fragments.
> > For instance, consider scenario 3 where video fragments (possibly all
> having
> > different parent media resources) are put together. Since different
> parent
> > resources implies potentially different underlying media formats, things
> > become complicated if we expect a smooth playback of a mashup of media
> > fragments. This is because different underlying media formats require the
> > (re-)initialization of the decoder(s) during playback of the mashup.
> > Therefore, I think we should make clear that in this scenario, we do not
> > expect smooth transitions between the different media fragments in the
> > playlist, because otherwise, this use case is far from trivial to
> implement.
>
>
I've read this UC&Req. document and looks good to me. Particularly, Section
1.4 is a close related to my research in conjunction with IPTV business. I
am saying this UC as *storytelling*. There are lots of widely spreaded
pieces on the web, and if we can recomposit them into one media to be palyed
on TV screen, that would be good for IPTV viewers since IPTV viewers fully
make sense to watch out these long video in their living room. Merging those
fragments media allow me to make a entirely new media to IPTV users. If it
can play very smoothly, it's also great of course.

One concern in my mind is how to deal with copyright of each fragment. If I
missed this threads, I am sorry about that...:-)


-- 
Daniel Park [at] Samsung Electronics