Re: [Fwd: Re: [rss-media] Specification currently lists the wrong namespace]

Sapna, et al:

Several months back, there was discussion about placing the=20=20
custodianship of the Media RSS spec with the RSS Advisory Board. The=20=20
folks at Yahoo! at the time had consented that it was a good idea (I=20=20
believe this was Jeremy Zawdony, IIRC), but there never seemed to be=20=20
any forward progress on that initiative.

My concern stems from the fact that the Media RSS spec has been broken/=20
incorrect multiple times now under Yahoo!'s custodianship. This is a=20=20
spec that many people depend on, and speaking as the developer of the=20=20
SimplePie RSS parser, arbitrarily changing the namespace URL=20=20
substantially affects our ability to handle Media RSS feeds. (We=20=20
already have to normalize the two different Media RSS namespace URLs=20=20
that are floating around: one with, and one without the trailing slash=20=20
-- which was broken for over a year.)

I would really like to see the RSS Advisory Board pass a resolution to=20=20
publish the namespace documentation on its site with the proper=20=20
longtime namespace URI. Netscape trusted the board to oversee RSS 0.90=20=20
and RSS 0.91, and I would hope that Yahoo! would be able to see that=20=20
this transfer of custodianship would be a Good Thing=99 for the Media=20=20
RSS community.

Future changes to the spec could be handled by the Media RSS=20=20
community, of which Yahoo! and others could be a part.

Thoughts?



On Jul 28, 2009, at 12:52 AM, Sapna Chandiramani wrote:

> Folks,
>
> I apologize for the issues on behalf of Yahoo.
> There were indeed some problems with the spec. This happened when we=20=20
> were moving the spec to the Video Search servers so it would be=20=20
> easier to respond to issues and requests henceforth.
>
> In any case, we have reverted back the spec. We are also working on=20=20
> a newer version of the spec that addresses some concerns this group=20=20
> had pointed out earlier, as well as some enhancements that we felt=20=20
> would be good to have.
>
> We will send that out for review to you soon.
>
> Thanks,
> Sapna
>
> -------- Original Message --------
> Subject: Re: [rss-media] Specification currently lists the wrong=20=20
> namespace
> Date: Tue, 21 Jul 2009 01:17:48 +0530
> From: Joly MacFie <[email protected]>
> Reply-To: [email protected] <[email protected]>
> To: [email protected] <[email protected]>
> References: <[email protected]>
> <[email protected]>
>
> Earlier discussion:
> http://tech.groups.yahoo.com/group/rss-media/msearch?query=3Dslash&submit=
=3DSearch&charset=3DISO-8859-1
> <http://tech.groups.yahoo.com/group/rss-media/msearch?query=3Dslash&submi=
t=3DSearch&charset=3DISO-8859-1=20
> >
>
> Yahoo's neglect is a shame. Wasn't there some talk of moving it out of
> their control?
>
> joly
>
> On Mon, Jul 20, 2009 at 1:52 PM, Ryan Parman
> <[email protected]=20=20
> <mailto:[email protected]>>
> wrote:
>
> 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
> >
>
> --=20
> ----------------------------------------------------------
> Joly MacFie 917 442 8665 Skype:punkcast
> WWWhatsup NYC - http://wwwhatsup.com <http://wwwhatsup.com>
> http://pinstand.com <http://pinstand.com> - http://punkcast.com
> <http://punkcast.com>
> ----------------------------------------------------------
>
>
>=20



[Non-text portions of this message have been removed]



------------------------------------

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]=20
    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/