Hey,
Just getting started after our eventful return from the other half of the
world. There are a couple things I don't completely like in this proposal:
1) How do we deal with the fact that several "versions" of the same
MediaPackage can be distributed to the same distribution channel? For
instance, I'm thinking of one Youtube video with just the slides (and the
sound) and another with just the teacher. Or one with the slides and the
sound and another with a composition of the camera and the slides. Will we
have, then, two (or more) "presentation" elements?
2) I don't like the name "presentations", because it may be confusing with
the term "presentation", often used to refer to the PowerPoint presentation
("slides") used in a recording. Due to the lack of a better term, I'd
suggest "distribution", which in the end is the term used to describe what
this new MediaPackage item is for. I'm not very sure about this last name,
but I do think it's more accurate and less confusing than the proposed
"presentations".
3) I have just realized of the "channel" argument in the second example
given by Tobias. Shouldn't we make a difference between elements
distributed as "downloads" and as "streaming"? In that case, "engage" would
be an ambiguous term, and we should specify 'channel="engage-download"' or
'channel="engage-streaming"' (or, at least, 'channel="download"' or
'channel="streaming"'). I know those are mere examples, and not "real"
pieces of xml, but I think it's good to point this out and make it clear.
Best regards,
Rubén Pérez Vázquez
<http://www.teltek.es>
www.teltek.es
2013/1/31 Christoph Drießen <christ...@entwinemedia.com>
> Karen,
>
> Am 31.01.2013 um 10:34 schrieb Karen Dolan <kdo...@dce.harvard.edu>:
>
> > I'm hoping the inclusion of the presentation element might allow the
> media to contain the RTMP link (within the presentation element), and
> workflow operations, such as archive, can successfully access the media
> because they can ignore or skip the presentation element.
>
> That's exactly how it will be. So stay tuned.
>
> Christoph
>
> _______________________________________________
> Matterhorn mailing list
> Matterhorn@opencastproject.org
> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>
>
> To unsubscribe please email
> matterhorn-unsubscr...@opencastproject.org
> _______________________________________________
>
_______________________________________________
Matterhorn mailing list
Matterhorn@opencastproject.org
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
matterhorn-unsubscr...@opencastproject.org
_______________________________________________
