video/rss+xml [was: Re: Re: Using dc:language vs language]

Are there any objections to "video/rss+xml" (given all that that was just said)?


I'm inclined to encourage people to use "video/rss+xml" (and "video/atom+xml").

(Perhaps write a quick Wordpress plugin to make it easy for to do this.  Etc.)


See ya

-- 
    Charles Iliya Krempeaux, B.Sc. <http://ChangeLog.ca/>


                  All the Vlogging News on One Page
                         http://vlograzor.com/


On 6/6/07, Charles Iliya Krempeaux <[email protected]> wrote:
> Hello Bill,
>
> On 6/6/07, Bill Kearney <[email protected]> wrote:
>
> [...]
>
> > I think the crux of my objection is the attempt to define an entire instance
> > of a 'feed' as being solely of one content type.  I reject that notion
> > completely.  I can understand why some folks might want to do this, I don't
> > think I support the idea.  I could, perhaps, be swayed with more effective
> > examples.
>
> In the Videoblogging/Vlogging/Vodcasting world, it is very very common
> to have feeds that just do video and only video.
>
> One (of many many many) examples is Rocketboom...
>
> http://rocketboom.com/
>
> It's an Internet TV show.  It will always be an Internet TV show.
>
> We're not talking about blogs that sometimes post links to video or
> sometimes embed video.
>
> We're talking about sites that always and only post video (with some
> auxiliary text).
>
> You can get a human readable description of these feeds at...
>
>   http://www.rocketboom.com/vlog/rss.html
>
>
> This is the use case for the "video/rss+xml" MIME type.  (Internet TV
> sites like Rocketboom.)
>
>
>
> > The trouble is crappy tools like iTunes fail to support the full range of a
> > feed's content.  As in, only playing the audio, not showing the text.
> > Leading to folks trying to publish feeds with content solely for the audio
> > or video device instead of just publishing one feed.  The enclosure URI and
> > metadata are small enough as to be trivial.  Or likewise the text content
> > being ignored.
> >
> > We could go off on a whole other tangent regarding accept headers during
> > HTTP requests...
>
> Yeah... I did that :-)
>
> http://tech.groups.yahoo.com/group/rss-public/message/1358
>
> > Those would be better served as a means to "optimize" a
> > feed based on the retrieving end's ability/desire to consume content types.
> > But here again I sense over-optimization, and the unlikelihood of any
> > serious uptake in the field.
> >
> > > The other is that it can be hard to tell even when looking inside. Some
> > > enclosure types are ambiguous, and as Bill Kearney said, a feed can
> > > contain one thing one day, something else entirely the next. So it might
> > > be nice if authors could be specific.
> >
> > To what end?
>
> Because different helper applications or web sites/services, are
> "launched" (from the web browser) based on a MIME type basis.
>
> And if you have one MIME type for text-based, audio-based, and
> video-based RSS feeds, then you can NOT launch a different application
> or web site/service to handle each of them.
>
> Handling all RSS feeds with a single RSS aggregator or a single web
> site/service is no longer desirable. Internet TV (vloging/vodcasting)
> RSS feeds may be handled by one piece of software. Internet Radio
> (podcast) RSS feeds may be handled by another piece of software. And
> (text) news and blog RSS feeds may be handled by yet another piece of
> software or web site/service.
>
> [...]
>
>
> Does that explain, well enough, why "video/rss+xml" and
> "audio/rss+xml" is needed?
>
>
> See ya
>
> --
>     Charles Iliya Krempeaux, B.Sc. <http://ChangeLog.ca/>
>
>
>                   All the Vlogging News on One Page
>                          http://vlograzor.com/
>


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rss-public/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/rss-public/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/