Re: [Fwd: Re: [rss-media] Specification currently lists the wrong namespace]
- Sapna, et al:
Several months back, there was discussion about placing the
custodianship of the Media RSS spec with the RSS Advisory Board. The
folks at Yahoo! at the time had consented that it was a good idea (I
believe this was Jeremy Zawdony, IIRC), but there never seemed to be
any forward progress on that initiative.
My concern stems from the fact that the Media RSS spec has been broken/
incorrect multiple times now under Yahoo!'s custodianship. This is a
spec that many people depend on, and speaking as the developer of the
SimplePie RSS parser, arbitrarily changing the namespace URL
substantially affects our ability to handle Media RSS feeds. (We
already have to normalize the two different Media RSS namespace URLs
that are floating around: one with, and one without the trailing slash
-- which was broken for over a year.)
I would really like to see the RSS Advisory Board pass a resolution to
publish the namespace documentation on its site with the proper
longtime namespace URI. Netscape trusted the board to oversee RSS 0.90
and RSS 0.91, and I would hope that Yahoo! would be able to see that
this transfer of custodianship would be a Good Thing� for the Media
Future changes to the spec could be handled by the Media RSS
community, of which Yahoo! and others could be a part.
On Jul 28, 2009, at 12:52 AM, Sapna Chandiramani wrote:
> I apologize for the issues on behalf of Yahoo.
> There were indeed some problems with the spec. This happened when we
> were moving the spec to the Video Search servers so it would be
> easier to respond to issues and requests henceforth.
> In any case, we have reverted back the spec. We are also working on
> a newer version of the spec that addresses some concerns this group
> had pointed out earlier, as well as some enhancements that we felt
> would be good to have.
> We will send that out for review to you soon.
> -------- Original Message --------
> Subject: Re: [rss-media] Specification currently lists the wrong
> Date: Tue, 21 Jul 2009 01:17:48 +0530
> From: Joly MacFie <joly@...>
> Reply-To: email@example.com <firstname.lastname@example.org>
> To: email@example.com <firstname.lastname@example.org>
> References: <h421vv+3t1f@...>
> Earlier discussion:
> Yahoo's neglect is a shame. Wasn't there some talk of moving it out of
> their control?
> On Mon, Jul 20, 2009 at 1:52 PM, Ryan Parman
> It looks like Yahoo once again arbitrarily changed the spec without
> telling anybody.
> As of the last update that anybody was aware of, we had:
> 03/12/2008 - Namespace corrections: [1.1.2]
> * Added trailing slash to namespace
> The correct namespace *should* be exactly what you posted.
> Apparently, Yahoo thought it'd be a good idea to change the
> namespace again and break all sorts of parsing software. It is
> embarrassing how badly they've bungled this spec.
> Once upon a time it fell to Jeremy Zawdony, but he's left Yahoo
> since then. From what I can tell, nobody at Yahoo is paying
> attention to this spec.
> On Jul 20, 2009, at 8:20 AM, James Abley wrote:
> > Hi,
> > I'm putting http://search.yahoo.com/mrss/
> > <http://search.yahoo.com/mrss/> into my browser, which used to
> > display the spec and have the correct namespace on the page. At
> > the moment, I'm getting a 302 back to
> > Location: http://video.search.yahoo.com/mrss
> > <http://video.search.yahoo.com/mrss>
> > and that URL is used as the namespace URI in the rendered
> > specification.
> > Anyone else noticed this and know who to raise it with? I don't
> > want any more ambiguity in the world as to the correct namespace
> > URI for this extension!
> > Cheers,
> > James
> Joly MacFie 917 442 8665 Skype:punkcast
> WWWhatsup NYC - http://wwwhatsup.com <http://wwwhatsup.com>
> http://pinstand.com <http://pinstand.com> - http://punkcast.com
[Non-text portions of this message have been removed]
- --- In email@example.com, Ryan Parman <ryan.lists.warpshare@...> wrote:
> I would really like to see the RSS Advisory Board pass a resolution toI favor this proposal and will work up a draft for consideration by the board. The RSS Advisory Board has been around for years and has proven to be a useful place for specs and other documentation related to RSS. We've recently moved the site to its own server -- taking it off my own -- to ensure its continued availability. We could publish the spec under any terms desired by Yahoo and the Media RSS community.
> publish the namespace documentation on its site with the proper
> longtime namespace URI. Netscape trusted the board to oversee RSS 0.90
> and RSS 0.91, and I would hope that Yahoo! would be able to see that
> this transfer of custodianship would be a Good Thing for the Media
> RSS community.