As posted in a previous topic, I vote in favor of the proposal.

Also, I can agree to the request to leave the namespace untouched since my previous message seems to have created some kind of troubles.

-- Simone Carletti

--- In rss-board@yahoogroups.com, Ryan Parman <ryan.lists.warpshare@...> wrote:
>
> I vote in favor of the proposal.
>
> --
> Ryan Parman
> <http://ryanparman.com>
>
>
>
>
>
> On Dec 1, 2009, at 12:22 PM, Rogers wrote:
>
> > I vote Yes on the proposal.
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
>

As posted in a previous topic, I vote in favor of the proposal.

Also, I can agree to the request to leave the namespace untouched since my
previous message seems to have created some kind of troubles.

-- Simone Carletti


--- In rss-board@yahoogroups.com, Ryan Parman <ryan.lists.warpshare@...> wrote:
>
> I vote in favor of the proposal.
>
> --
> Ryan Parman
> <http://ryanparman.com>
>
>
>
>
>
> On Dec 1, 2009, at 12:22 PM, Rogers wrote:
>
> > I vote Yes on the proposal.
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
>

I vote in favor of the proposal.

--
Ryan Parman
<http://ryanparman.com>





On Dec 1, 2009, at 12:22 PM, Rogers wrote:

> I vote Yes on the proposal.
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

I vote Yes on the proposal.

I vote in favor of the proposal. Just a note. If the vote doesn't pass, then I
would encourage compromise to make certain it happens.


--- In rss-board@yahoogroups.com, "randymorin" <randy@...> wrote:
>
> Today begins the one week period of voting to transfer publication of the mRSS
spec to the board.
>
> Please review Rogers proposal (see following message).
> http://tech.groups.yahoo.com/group/rss-board/message/295
>

In favor.

--- In rss-board@yahoogroups.com, "randymorin" <randy@...> wrote:
>
> Today begins the one week period of voting to transfer publication of the mRSS
spec to the board.
>
> Please review Rogers proposal (see following message).
> http://tech.groups.yahoo.com/group/rss-board/message/295
>

Today begins the one week period of voting to transfer publication of the mRSS
spec to the board.

Please review Rogers proposal (see following message).
http://tech.groups.yahoo.com/group/rss-board/message/295

On Sun, Nov 29, 2009 at 2:25 PM, James Holderness <j4_james@...> wrote:
> Given what has been said in this thread, it seems to me that some people
> either don't realise that they're making that promise by agreeing to the
> proposal, or that they think it's just a temporary commitment that they can
> back out of if circumstances change.

I think it's good that you've called attention to this aspect of the
proposal. It will help ensure that board members know the significance
of that provision.

The vote begins tomorrow, so I hope that members who have concerns or
comments will post today.

Rogers Cadenhead wrote:
> It would be a shame not to take
> this opportunity because of what I regard as a minor concern -- the
> idea we'd change the namespace URI after explicitly promising not to
> do so.

I agree. But I don't think it's asking a lot to expect some clarification
from board members about whether they really would stick to that promise.

Given what has been said in this thread, it seems to me that some people
either don't realise that they're making that promise by agreeing to the
proposal, or that they think it's just a temporary commitment that they can
back out of if circumstances change.

Regards
James

On Sat, Nov 28, 2009 at 6:08 PM, James Holderness <j4_james@...> wrote:
> What scares me is that something that should be unthinkable, clearly isn't.

The confusion occurs because namespace URIs look like web addresses,
so people naturally think that when the web address changes the URI
should change as well.

Neither solution is perfect. If the owner of the domain that matches
the URI stops forwarding, it will confuse some people who go looking
for the namespace documentation at that URI. But one of the things we
can do as a board is to help people realize that a namespace URI is
just a unique identifier. It doesn't have to be associated with a web
page.

As to whether it's naive or not, as a board we've been extremely
conservative about making changes to things that affect existing
implementations. That's why we published the RSS Profile instead of
revising the specification to address things like the multiple
enclosures issue. My expectation is that we'll continue to tread
carefully.

We have an opportunity here to help the Media-RSS community. The
proposal that Ryan and I drafted is the result of more than a year's
communication with Yahoo and Media-RSS developers to achieve the
strongest consensus going forward. It would be a shame not to take
this opportunity because of what I regard as a minor concern -- the
idea we'd change the namespace URI after explicitly promising not to
do so.

On Nov 28, 2009, at 2:31 PM, Rogers Cadenhead wrote:

> If the proposal passes, Yahoo is going to forward its old URLs to the
> documents on the RSS board web site.

For me, it was simply a question of what's going to happen with the old URLs.

The aforementioned statement answers my question.

Rogers Cadenhead wrote:
> Whether individual board members retract their statements seems less
> relevant to me than the language of the proposal, if it passes. If we
> agree collectively to keep that obligation, I think the members in the
> future will keep that obligation.

I think that's a little naive. I'd hate to think that the board couldn't
vote to correct past mistakes, even if that means allowing the board to undo
good decisions.

What scares me is that something that should be unthinkable, clearly isn't.

Regards
James

Agreed.  I see no reason to retract my statement, because as long as Yahoo
continues to support the existing URL, it should remain there.

--- In rss-board@yahoogroups.com, Rogers Cadenhead <cadenhead@...> wrote:
>
> --- In rss-board@yahoogroups.com, "James Holderness" <j4_james@> wrote:
> > I would not feel comfortable having control of this specification in
> > the hands of the board if these members could not be persuaded to
> > retract their statements.
>
> The phrase "Finally, the board resolves that the namespace URI for
> Media RSS will remain "http://search.yahoo.com/mrss/" for as long as
> it is published to ensure that software using the namespace will
> continue to function properly." is part of the proposal. If it passes,
> the board will have expressed its obligation to keep the URI unchanged
> for as long as we publish the specification.
>
> The reason this obligation is in the proposal is because changes to
> the namespace URI have been an issue for the Media-RSS community in
> the past.
>
> If the proposal passes, Yahoo is going to forward its old URLs to the
> documents on the RSS board web site.
>
> Whether individual board members retract their statements seems less
> relevant to me than the language of the proposal, if it passes. If we
> agree collectively to keep that obligation, I think the members in the
> future will keep that obligation.
>

--- In rss-board@yahoogroups.com, "James Holderness" <j4_james@...> wrote:
> I would not feel comfortable having control of this specification in
> the hands of the board if these members could not be persuaded to
> retract their statements.

The phrase "Finally, the board resolves that the namespace URI for
Media RSS will remain "http://search.yahoo.com/mrss/" for as long as
it is published to ensure that software using the namespace will
continue to function properly." is part of the proposal. If it passes,
the board will have expressed its obligation to keep the URI unchanged
for as long as we publish the specification.

The reason this obligation is in the proposal is because changes to
the namespace URI have been an issue for the Media-RSS community in
the past.

If the proposal passes, Yahoo is going to forward its old URLs to the
documents on the RSS board web site.

Whether individual board members retract their statements seems less
relevant to me than the language of the proposal, if it passes. If we
agree collectively to keep that obligation, I think the members in the
future will keep that obligation.

Rogers wrote:
> Finally, the board resolves that the namespace URI for Media RSS
> will remain "http://search.yahoo.com/mrss/" for as long as it is
> published to ensure that software using the namespace will
> continue to function properly.

And yet we've already had two board members suggest that it would be ok to
change the namespace URI in the future.

I would not feel comfortable having control of this specification in the
hands of the board if these members could not be persuaded to retract their
statements.

Regards
James

I also agree with the aforementioned proposal, but have the same question as
"wepposcarletti".

--
Ryan Parman
<http://ryanparman.com>





On Nov 26, 2009, at 12:56 AM, wepposcarletti wrote:

> I agree both with the proposal and the suggestion to move the namespace at
some point.
>
> What are your plans for the http://video.search.yahoo.com/mrss URL?
> Will it redirect to the corresponding page on the RSS Board site?
>
> -- Simone
>
>
> --- In rss-board@yahoogroups.com, "scamden" <sterling@...> wrote:
>>
>> It makes sense to me to have the Board as the central reference point for all
things RSS. so I'm in favor of this proposal.  I could see down the road maybe
moving the namespace URL here as well, should it ever be abandoned by yahoo --
but I agree we should leave it where it is for now, for compatibility.
>>
>> --- In rss-board@yahoogroups.com, "Rogers" <cadenhead@> wrote:
>>>
>>> The following RSS Advisory Board proposal has been made by Rogers Cadenhead
and seconded by Ryan Parman.
>>>
>>> Under the advisory board charter, the board has seven days to discuss the
proposal followed by seven days to vote on it. Interested parties can comment on
the proposal on the mailing list RSS-Public [1].
>>>
>>> Media RSS [2] is a namespace for syndicating audio, video and image files
that was created by Yahoo in 2004. The namespace extends RSS support for
enclosures to enable a number of different applications, such as video and audio
search engines, multiple bitrates and encodings of the same content, artist
credits and copyright information, and the ability to play the content with a
specified media player.
>>>
>>> In the five years since its launch, Media RSS has become highly popular with
podcasters and other multimedia publishers and fostered an active development
community at the Yahoo Groups mailing list RSS-Media [3]. The namespace is
supported by Yahoo Search, Bing, Wikipedia, Flock, Picasa, FriendFeed, Bebo and
many other sites and software.
>>>
>>> Yahoo, with the participation of members of RSS-Media, recently published
version 1.5 of the Media RSS specification.
>>>
>>> Over the past year, there have been discussions about the RSS Advisory Board
becoming the publisher of the Media RSS namespace to ensure its continued
availability and stability, a function the board serves for RSS 0.90 and RSS
0.91. Netscape transferred those specifications [4] to the board in November
2008.
>>>
>>> Sapna Chandiramani, a senior engineering manager at Yahoo whose department
has responsibility for the Media RSS namespace, has indicated a willingness to
have the board take over custodianship.
>>>
>>> I propose that the RSS Advisory Board agrees to become the custodian of the
namespace, publishing the current version at the permanent URL
http://www.rssboard.org/media-rss and archiving past versions.
>>>
>>> Additionally, the board offers to manage the RSS-Media mailing list.
>>>
>>> Finally, the board resolves that the namespace URI for Media RSS will remain
"http://search.yahoo.com/mrss/" for as long as it is published to ensure that
software using the namespace will continue to function properly.
>>>
>>> 1: http://groups.yahoo.com/group/rss-public
>>> 2: http://video.search.yahoo.com/mrss
>>> 3: http://tech.groups.yahoo.com/group/rss-media
>>> 4: http://www.rssboard.org/news/181/rss-090-091-moving-rss-advisory-board
>>>
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

I agree both with the proposal and the suggestion to move the namespace at some
point.

What are your plans for the http://video.search.yahoo.com/mrss URL?
Will it redirect to the corresponding page on the RSS Board site?

-- Simone


--- In rss-board@yahoogroups.com, "scamden" <sterling@...> wrote:
>
> It makes sense to me to have the Board as the central reference point for all
things RSS. so I'm in favor of this proposal.  I could see down the road maybe
moving the namespace URL here as well, should it ever be abandoned by yahoo --
but I agree we should leave it where it is for now, for compatibility.
>
> --- In rss-board@yahoogroups.com, "Rogers" <cadenhead@> wrote:
> >
> > The following RSS Advisory Board proposal has been made by Rogers Cadenhead
and seconded by Ryan Parman.
> >
> > Under the advisory board charter, the board has seven days to discuss the
proposal followed by seven days to vote on it. Interested parties can comment on
the proposal on the mailing list RSS-Public [1].
> >
> > Media RSS [2] is a namespace for syndicating audio, video and image files
that was created by Yahoo in 2004. The namespace extends RSS support for
enclosures to enable a number of different applications, such as video and audio
search engines, multiple bitrates and encodings of the same content, artist
credits and copyright information, and the ability to play the content with a
specified media player.
> >
> > In the five years since its launch, Media RSS has become highly popular with
podcasters and other multimedia publishers and fostered an active development
community at the Yahoo Groups mailing list RSS-Media [3]. The namespace is
supported by Yahoo Search, Bing, Wikipedia, Flock, Picasa, FriendFeed, Bebo and
many other sites and software.
> >
> > Yahoo, with the participation of members of RSS-Media, recently published
version 1.5 of the Media RSS specification.
> >
> > Over the past year, there have been discussions about the RSS Advisory Board
becoming the publisher of the Media RSS namespace to ensure its continued
availability and stability, a function the board serves for RSS 0.90 and RSS
0.91. Netscape transferred those specifications [4] to the board in November
2008.
> >
> > Sapna Chandiramani, a senior engineering manager at Yahoo whose department
has responsibility for the Media RSS namespace, has indicated a willingness to
have the board take over custodianship.
> >
> > I propose that the RSS Advisory Board agrees to become the custodian of the
namespace, publishing the current version at the permanent URL
http://www.rssboard.org/media-rss and archiving past versions.
> >
> > Additionally, the board offers to manage the RSS-Media mailing list.
> >
> > Finally, the board resolves that the namespace URI for Media RSS will remain
"http://search.yahoo.com/mrss/" for as long as it is published to ensure that
software using the namespace will continue to function properly.
> >
> > 1: http://groups.yahoo.com/group/rss-public
> > 2: http://video.search.yahoo.com/mrss
> > 3: http://tech.groups.yahoo.com/group/rss-media
> > 4: http://www.rssboard.org/news/181/rss-090-091-moving-rss-advisory-board
> >
>

It makes sense to me to have the Board as the central reference point for all
things RSS. so I'm in favor of this proposal.  I could see down the road maybe
moving the namespace URL here as well, should it ever be abandoned by yahoo --
but I agree we should leave it where it is for now, for compatibility.

--- In rss-board@yahoogroups.com, "Rogers" <cadenhead@...> wrote:
>
> The following RSS Advisory Board proposal has been made by Rogers Cadenhead
and seconded by Ryan Parman.
>
> Under the advisory board charter, the board has seven days to discuss the
proposal followed by seven days to vote on it. Interested parties can comment on
the proposal on the mailing list RSS-Public [1].
>
> Media RSS [2] is a namespace for syndicating audio, video and image files that
was created by Yahoo in 2004. The namespace extends RSS support for enclosures
to enable a number of different applications, such as video and audio search
engines, multiple bitrates and encodings of the same content, artist credits and
copyright information, and the ability to play the content with a specified
media player.
>
> In the five years since its launch, Media RSS has become highly popular with
podcasters and other multimedia publishers and fostered an active development
community at the Yahoo Groups mailing list RSS-Media [3]. The namespace is
supported by Yahoo Search, Bing, Wikipedia, Flock, Picasa, FriendFeed, Bebo and
many other sites and software.
>
> Yahoo, with the participation of members of RSS-Media, recently published
version 1.5 of the Media RSS specification.
>
> Over the past year, there have been discussions about the RSS Advisory Board
becoming the publisher of the Media RSS namespace to ensure its continued
availability and stability, a function the board serves for RSS 0.90 and RSS
0.91. Netscape transferred those specifications [4] to the board in November
2008.
>
> Sapna Chandiramani, a senior engineering manager at Yahoo whose department has
responsibility for the Media RSS namespace, has indicated a willingness to have
the board take over custodianship.
>
> I propose that the RSS Advisory Board agrees to become the custodian of the
namespace, publishing the current version at the permanent URL
http://www.rssboard.org/media-rss and archiving past versions.
>
> Additionally, the board offers to manage the RSS-Media mailing list.
>
> Finally, the board resolves that the namespace URI for Media RSS will remain
"http://search.yahoo.com/mrss/" for as long as it is published to ensure that
software using the namespace will continue to function properly.
>
> 1: http://groups.yahoo.com/group/rss-public
> 2: http://video.search.yahoo.com/mrss
> 3: http://tech.groups.yahoo.com/group/rss-media
> 4: http://www.rssboard.org/news/181/rss-090-091-moving-rss-advisory-board
>

The following RSS Advisory Board proposal has been made by Rogers Cadenhead and
seconded by Ryan Parman.

Under the advisory board charter, the board has seven days to discuss the
proposal followed by seven days to vote on it. Interested parties can comment on
the proposal on the mailing list RSS-Public [1].

Media RSS [2] is a namespace for syndicating audio, video and image files that
was created by Yahoo in 2004. The namespace extends RSS support for enclosures
to enable a number of different applications, such as video and audio search
engines, multiple bitrates and encodings of the same content, artist credits and
copyright information, and the ability to play the content with a specified
media player.

In the five years since its launch, Media RSS has become highly popular with
podcasters and other multimedia publishers and fostered an active development
community at the Yahoo Groups mailing list RSS-Media [3]. The namespace is
supported by Yahoo Search, Bing, Wikipedia, Flock, Picasa, FriendFeed, Bebo and
many other sites and software.

Yahoo, with the participation of members of RSS-Media, recently published
version 1.5 of the Media RSS specification.

Over the past year, there have been discussions about the RSS Advisory Board
becoming the publisher of the Media RSS namespace to ensure its continued
availability and stability, a function the board serves for RSS 0.90 and RSS
0.91. Netscape transferred those specifications [4] to the board in November
2008.

Sapna Chandiramani, a senior engineering manager at Yahoo whose department has
responsibility for the Media RSS namespace, has indicated a willingness to have
the board take over custodianship.

I propose that the RSS Advisory Board agrees to become the custodian of the
namespace, publishing the current version at the permanent URL
http://www.rssboard.org/media-rss and archiving past versions.

Additionally, the board offers to manage the RSS-Media mailing list.

Finally, the board resolves that the namespace URI for Media RSS will remain
"http://search.yahoo.com/mrss/" for as long as it is published to ensure that
software using the namespace will continue to function properly.

1: http://groups.yahoo.com/group/rss-public
2: http://video.search.yahoo.com/mrss
3: http://tech.groups.yahoo.com/group/rss-media
4: http://www.rssboard.org/news/181/rss-090-091-moving-rss-advisory-board

The RSS Advisory Board is now running a local copy of the Feed Validator:

http://rssboard.org/rss-validator

I'm still making some adjustments to the presentation, but it looks like it
works properly. If you could test it with your own RSS feeds and let me know if
you encounter problems, that would be helpful.

The validator didn't have a "valid RSS" badge that includes the Feed Icon, so I
created one:

http://rssboard.org/rss-validator/images/valid-rss.png

I will try to keep the code up to date with the Feed Validator and contribute
any changes I make back to the project. So far it's running the exact same code.

The valid RSS badge is available for reuse under the Creative Commons
Attribution/Share Alike license [1]

1: http://creativecommons.org/licenses/by-sa/2.0/

IMHO, I don't understand how anybody thinks that rssCloud could possibly work.
There's simply too many scenarios where the spec fails.

See scenarios of failure
http://www.therssweblog.com/?guid=20090916100620

Unless there is major changes to address these holes, then I'm not really
prepared to put any time into it.

Thanks,

Randy

--- In rss-board@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> As you probably know, Dave Winer's been working to revive the cloud element in
RSS and the RSSCloud Interface that defines how it is used. These date back to
RSS 0.92. The work's described on a web site he has launched:
>
> http://www.rsscloud.org/
>
> For this effort, Winer is unilaterally making changes to the RSSCloud
Interface. He has added multiple url# arguments (url1, url2, url3 and so on) to
the REST interface:
>
> http://rsscloud.org/walkthrough.html#requestingNotificationUsingRest
>
> He also has added a REST ping method:
>
> http://rsscloud.org/walkthrough.html#pingingViaRestaNamepingresta
>
> WordPress has implemented RSSCloud with Winer's participation for all seven
million of its hosted blogs on wordpress.com.
>
> I'd like to know what the members think that the RSS Advisory Board should do,
if anything, in regard to this effort. I've posted the same question on the
RSS-Public mailing list.
>