Because of some concerns that were brought to my attention during the
transition, I finished a long-standing project I've been working on
during my tenure on the advisory board: a proposed specification for
the existing RSS format that has been written from scratch.
Here's the URL:
http://www.rssboard.org/rss-draft-1
The "RSS-Draft-1" proposal is offered for evaluation by the public. I
don't intend to bring it before the board for consideration for at
least 60 days -- more if some of the other spec geeks tell me I made a
botch of things.
The current Really Simple Syndication spec, a product of six revisions
by the board since its founding, is here:
http://www.rssboard.org/rss-2-0-1-rv-6
Welcome to the board!
Randy Charles Morin on RSS-Public:
"I created an OPML file of all RSS feeds for the board members and
board Website and mailing lists. Did I miss anything?"
http://www.kbcafe.com/rss/rssadvisoryboard.xml
This enables people to grab all of our feeds as an OPML reading list,
and it ties into something I think would be good for the board site: a
simple aggregator that demonstrates how they work for people
completely new to RSS.
Would anyone object to their personal blog being part of a sample
aggregator?
No objection from me.
--- In rss-board@yahoogroups.com, "rcade" <rcade@y...> wrote:
> Would anyone object to their personal blog being part of a sample
> aggregator?
>
May I suggest that we all tag our blogs with rss and rssboard?
You can get the details here:
http://technorati.com/blogs/rsshttp://technorati.com/blogs/rssboard
We can then automatically add the blogs to our Explore section, so
people can automatically keep up with the most interesting posts from
board members too.
e.g.
http://technorati.com/explore/rss
Dave
rcade wrote:
> Randy Charles Morin on RSS-Public:
>
> "I created an OPML file of all RSS feeds for the board members and
> board Website and mailing lists. Did I miss anything?"
>
> http://www.kbcafe.com/rss/rssadvisoryboard.xml
>
> This enables people to grab all of our feeds as an OPML reading list,
> and it ties into something I think would be good for the board site: a
> simple aggregator that demonstrates how they work for people
> completely new to RSS.
>
> Would anyone object to their personal blog being part of a sample
> aggregator?
>
>
>
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
> * Visit your group "rss-board
> <http://groups.yahoo.com/group/rss-board>" on the web.
>
> * To unsubscribe from this group, send an email to:
> rss-board-unsubscribe@yahoogroups.com
> <mailto:rss-board-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>
--
David L. Sifry
Founder and CEO, Technorati, Inc.
dsifry@...
415 846-0232 (Mobile)
Dave,
I went into my profile and manually added the rssboard tag to The
RSS Blog, but I'm not there [http://technorati.com/blogs/rssboard].
Does it take time? Also, I already had the rss tag and I don't seem
to be there either [http://technorati.com/blogs/rss].
Thanks,
Randy Charles Morin
--- In rss-board@yahoogroups.com, David Sifry <dsifry@t...> wrote:
>
> May I suggest that we all tag our blogs with rss and rssboard?
>
> You can get the details here:
>
> http://technorati.com/blogs/rss
> http://technorati.com/blogs/rssboard
>
> We can then automatically add the blogs to our Explore section, so
> people can automatically keep up with the most interesting posts
from
> board members too.
>
> e.g.
> http://technorati.com/explore/rss
>
> Dave
>
> rcade wrote:
> > Randy Charles Morin on RSS-Public:
> >
> > "I created an OPML file of all RSS feeds for the board members
and
> > board Website and mailing lists. Did I miss anything?"
> >
> > http://www.kbcafe.com/rss/rssadvisoryboard.xml
> >
> > This enables people to grab all of our feeds as an OPML reading
list,
> > and it ties into something I think would be good for the board
site: a
> > simple aggregator that demonstrates how they work for people
> > completely new to RSS.
> >
> > Would anyone object to their personal blog being part of a sample
> > aggregator?
> >
> >
> >
> >
> >
> > -----------------------------------------------------------------
-------
> > YAHOO! GROUPS LINKS
> >
> > * Visit your group "rss-board
> > <http://groups.yahoo.com/group/rss-board>" on the web.
> >
> > * To unsubscribe from this group, send an email to:
> > rss-board-unsubscribe@yahoogroups.com
> > <mailto:rss-board-unsubscribe@yahoogroups.com?
subject=Unsubscribe>
> >
> > * Your use of Yahoo! Groups is subject to the Yahoo! Terms
of
> > Service <http://docs.yahoo.com/info/terms/>.
> >
> >
> > -----------------------------------------------------------------
-------
> >
>
> --
> David L. Sifry
> Founder and CEO, Technorati, Inc.
> dsifry@t...
> 415 846-0232 (Mobile)
>
In the time I've been serving on the RSS Advisory Board, I've been
asked fairly often to look at a Really Simple Syndication feed and
help someone figure out why it isn't working.
The first thing I do in response is load it in the Feed Validator [1],
the open source validator developed by Sam Ruby, Mark Pilgrim, Joseph
Walton and Phil Ringnalda that supports RSS and Atom. I did the same
thing when I was drafting the proposed specification, pasting each
example into a sample document [2] and running it through the
validator to catch potential mistakes.
At FeedBurner, Eric Lunt has a similar troubleshooting approach when
users have problems with their feeds, so we're making a joint proposal.
Proposed: The board should officially recommend and use the Feed
Validator.
A validator complements a specification, as long as they're
in agreement. In the three years the validator has been around, I've
asked Sam a half-dozen times about its interpretation of RSS, and each
time he was quick to address my concerns. If there's an area where
the validator and board members have disagreed over an aspect of RSS,
my experience has been that he eagerly defers to our judgment.
I've leaned on the validator so often that I recently became one of
the developers [3] so I could pitch in on RSS-related issues.
If this proposal is seconded, we'll have seven days of discussion here
and on RSS-Public followed by seven days in which board members can
vote on it [4].
1: http://feedvalidator.org
2: http://www.rssboard.org/files/rss-2.0-sample.xml
3: http://sourceforge.net/projects/feedvalidator
4: http://www.rssboard.org/charter
Seconded, but note at some point in the future I'd like to present a
Schematron schema for RSS that is platform/language agnostic and can
be integrated directly into any XSLT capable application. Note
Schematron is limited to validating well-formed XML. Validating
well-formedness and HTTP conformity is something the FeedValidator
does very well and could not be replaced by any XML schema.
Thanks,
Randy Charles Morin
http://www.kbcafe.com
--- In rss-board@yahoogroups.com, "rcade" <rcade@...> wrote:
>
> In the time I've been serving on the RSS Advisory Board, I've been
> asked fairly often to look at a Really Simple Syndication feed and
> help someone figure out why it isn't working.
>
> The first thing I do in response is load it in the Feed Validator [1],
> the open source validator developed by Sam Ruby, Mark Pilgrim, Joseph
> Walton and Phil Ringnalda that supports RSS and Atom. I did the same
> thing when I was drafting the proposed specification, pasting each
> example into a sample document [2] and running it through the
> validator to catch potential mistakes.
>
> At FeedBurner, Eric Lunt has a similar troubleshooting approach when
> users have problems with their feeds, so we're making a joint proposal.
>
> Proposed: The board should officially recommend and use the Feed
> Validator.
>
> A validator complements a specification, as long as they're
> in agreement. In the three years the validator has been around, I've
> asked Sam a half-dozen times about its interpretation of RSS, and each
> time he was quick to address my concerns. If there's an area where
> the validator and board members have disagreed over an aspect of RSS,
> my experience has been that he eagerly defers to our judgment.
>
> I've leaned on the validator so often that I recently became one of
> the developers [3] so I could pitch in on RSS-related issues.
>
> If this proposal is seconded, we'll have seven days of discussion here
> and on RSS-Public followed by seven days in which board members can
> vote on it [4].
>
> 1: http://feedvalidator.org
> 2: http://www.rssboard.org/files/rss-2.0-sample.xml
> 3: http://sourceforge.net/projects/feedvalidator
> 4: http://www.rssboard.org/charter
>
Today begins the seven-day voting period for this proposal, which was
made by Eric Lunt and I and seconded by Randy Charles Morin.
Use this mailing list to cast your vote, which can be Yes (or +1) to
support the proposal, No (or -1) to oppose it, and Abstain (or 0) to
defer the decision to the rest of the board.
Voting's a requirement of board membership [1], so please do so in the
next seven days.
PROPOSAL
In the time I've been serving on the RSS Advisory Board, I've been
asked fairly often to look at a Really Simple Syndication feed and
help someone figure out why it isn't working.
The first thing I do in response is load it in the Feed Validator [2],
the open source validator developed by Sam Ruby, Mark Pilgrim, Joseph
Walton and Phil Ringnalda that supports RSS and Atom. I did the same
thing when I was drafting the proposed specification, pasting each
example into a sample document [3] and running it through the
validator to catch potential mistakes.
At FeedBurner, Eric Lunt has a similar troubleshooting approach when
users have problems with their feeds, so we're making a joint proposal.
Proposed: The board should officially recommend and use the Feed
Validator.
A validator complements a specification, as long as they're
in agreement. In the three years the validator has been around, I've
asked Sam a half-dozen times about its interpretation of RSS, and each
time he was quick to address my concerns. If there's an area where
the validator and board members have disagreed over an aspect of RSS,
my experience has been that he eagerly defers to our judgment.
I've leaned on the validator so often that I recently became one of
the developers [4] so I could pitch in on RSS-related issues.
1: http://www.rssboard.org/charter
2: http://feedvalidator.org
3: http://www.rssboard.org/files/rss-2.0-sample.xml
4: http://sourceforge.net/projects/feedvalidator
--- In rss-board@yahoogroups.com, "rcade" <rcade@...> wrote:
> Proposed: The board should officially recommend and use the Feed
> Validator.
My vote's Yes, naturally.
The Feed Validator's a great tool when you're helping people implement
Really Simple Syndication and resolve problems in an RSS feed. We're
also relying on it as we develop the proposed specification on RSS-Public.
Yes
Randy
--- In rss-board@yahoogroups.com, "rcade" <rcade@...> wrote:
>
> Today begins the seven-day voting period for this proposal, which
was
> made by Eric Lunt and I and seconded by Randy Charles Morin.
>
> Use this mailing list to cast your vote, which can be Yes (or +1)
to
> support the proposal, No (or -1) to oppose it, and Abstain (or 0)
to
> defer the decision to the rest of the board.
>
> Voting's a requirement of board membership [1], so please do so in
the
> next seven days.
>
> PROPOSAL
>
> In the time I've been serving on the RSS Advisory Board, I've been
> asked fairly often to look at a Really Simple Syndication feed and
> help someone figure out why it isn't working.
>
> The first thing I do in response is load it in the Feed Validator
[2],
> the open source validator developed by Sam Ruby, Mark Pilgrim,
Joseph
> Walton and Phil Ringnalda that supports RSS and Atom. I did the
same
> thing when I was drafting the proposed specification, pasting each
> example into a sample document [3] and running it through the
> validator to catch potential mistakes.
>
> At FeedBurner, Eric Lunt has a similar troubleshooting approach
when
> users have problems with their feeds, so we're making a joint
proposal.
>
> Proposed: The board should officially recommend and use the Feed
> Validator.
>
> A validator complements a specification, as long as they're
> in agreement. In the three years the validator has been around,
I've
> asked Sam a half-dozen times about its interpretation of RSS, and
each
> time he was quick to address my concerns. If there's an area where
> the validator and board members have disagreed over an aspect of
RSS,
> my experience has been that he eagerly defers to our judgment.
>
> I've leaned on the validator so often that I recently became one of
> the developers [4] so I could pitch in on RSS-related issues.
>
> 1: http://www.rssboard.org/charter
> 2: http://feedvalidator.org
> 3: http://www.rssboard.org/files/rss-2.0-sample.xml
> 4: http://sourceforge.net/projects/feedvalidator
>
Thanks for coordinating, Rogers.
+1
rcade wrote:
> Today begins the seven-day voting period for this proposal, which was
> made by Eric Lunt and I and seconded by Randy Charles Morin.
>
> Use this mailing list to cast your vote, which can be Yes (or +1) to
> support the proposal, No (or -1) to oppose it, and Abstain (or 0) to
> defer the decision to the rest of the board.
>
> Voting's a requirement of board membership [1], so please do so in the
> next seven days.
>
> PROPOSAL
>
> In the time I've been serving on the RSS Advisory Board, I've been
> asked fairly often to look at a Really Simple Syndication feed and
> help someone figure out why it isn't working.
>
> The first thing I do in response is load it in the Feed Validator [2],
> the open source validator developed by Sam Ruby, Mark Pilgrim, Joseph
> Walton and Phil Ringnalda that supports RSS and Atom. I did the same
> thing when I was drafting the proposed specification, pasting each
> example into a sample document [3] and running it through the
> validator to catch potential mistakes.
>
> At FeedBurner, Eric Lunt has a similar troubleshooting approach when
> users have problems with their feeds, so we're making a joint proposal.
>
> Proposed: The board should officially recommend and use the Feed
> Validator.
>
> A validator complements a specification, as long as they're
> in agreement. In the three years the validator has been around, I've
> asked Sam a half-dozen times about its interpretation of RSS, and each
> time he was quick to address my concerns. If there's an area where
> the validator and board members have disagreed over an aspect of RSS,
> my experience has been that he eagerly defers to our judgment.
>
> I've leaned on the validator so often that I recently became one of
> the developers [4] so I could pitch in on RSS-related issues.
>
> 1: http://www.rssboard.org/charter
> 2: http://feedvalidator.org
> 3: http://www.rssboard.org/files/rss-2.0-sample.xml
> 4: http://sourceforge.net/projects/feedvalidator
>
>
>
>
>
> SPONSORED LINKS
> Xml format
>
<http://groups.yahoo.com/gads?t=ms&k=Xml+format&w1=Xml+format&w2=Advisory+board&\
c=2&s=36&.sig=KSg7t3lUtXUVPpohyDwW9A>
> Advisory board
>
<http://groups.yahoo.com/gads?t=ms&k=Advisory+board&w1=Xml+format&w2=Advisory+bo\
ard&c=2&s=36&.sig=nyPlw7lUdOy3F9-YtxxLjw>
>
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
> * Visit your group "rss-board
> <http://groups.yahoo.com/group/rss-board>" on the web.
>
> * To unsubscribe from this group, send an email to:
> rss-board-unsubscribe@yahoogroups.com
> <mailto:rss-board-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>
--
Eric Lunt
CTO, FeedBurner
eric@...
http://www.burningdoor.com/eric
I vote yes.
_rcade_ wrote:
> Today begins the seven-day voting period for this proposal, which was
> made by Eric Lunt and I and seconded by Randy Charles Morin.
>
> Use this mailing list to cast your vote, which can be Yes (or +1) to
> support the proposal, No (or -1) to oppose it, and Abstain (or 0) to
> defer the decision to the rest of the board.
>
> Voting's a requirement of board membership [1], so please do so in the
> next seven days.
>
> PROPOSAL
>
> In the time I've been serving on the RSS Advisory Board, I've been
> asked fairly often to look at a Really Simple Syndication feed and
> help someone figure out why it isn't working.
>
> The first thing I do in response is load it in the Feed Validator [2],
> the open source validator developed by Sam Ruby, Mark Pilgrim, Joseph
> Walton and Phil Ringnalda that supports RSS and Atom. I did the same
> thing when I was drafting the proposed specification, pasting each
> example into a sample document [3] and running it through the
> validator to catch potential mistakes.
>
> At FeedBurner, Eric Lunt has a similar troubleshooting approach when
> users have problems with their feeds, so we're making a joint proposal.
>
> Proposed: The board should officially recommend and use the Feed
> Validator.
>
> A validator complements a specification, as long as they're
> in agreement. In the three years the validator has been around, I've
> asked Sam a half-dozen times about its interpretation of RSS, and each
> time he was quick to address my concerns. If there's an area where
> the validator and board members have disagreed over an aspect of RSS,
> my experience has been that he eagerly defers to our judgment.
>
> I've leaned on the validator so often that I recently became one of
> the developers [4] so I could pitch in on RSS-related issues.
>
> 1: http://www.rssboard.org/charter
> 2: http://feedvalidator.org
> 3: http://www.rssboard.org/files/rss-2.0-sample.xml
> 4: http://sourceforge.net/projects/feedvalidator
>
>
>
>
>
> SPONSORED LINKS
> Xml format
>
<http://groups.yahoo.com/gads?t=ms&k=Xml+format&w1=Xml+format&w2=Advisory+board&\
c=2&s=36&.sig=KSg7t3lUtXUVPpohyDwW9A>
> Advisory board
>
<http://groups.yahoo.com/gads?t=ms&k=Advisory+board&w1=Xml+format&w2=Advisory+bo\
ard&c=2&s=36&.sig=nyPlw7lUdOy3F9-YtxxLjw>
>
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
> * Visit your group "rss-board
> <http://groups.yahoo.com/group/rss-board>" on the web.
>
> * To unsubscribe from this group, send an email to:
> rss-board-unsubscribe@yahoogroups.com
> <mailto:rss-board-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>
--
David L. Sifry
Founder and CEO, Technorati, Inc.
dsifry@...
415 846-0232 (Mobile)
Yes!
-----Original Message-----
From: rss-board@yahoogroups.com [mailto:rss-board@yahoogroups.com] On
Behalf Of rcade
Sent: Monday, February 13, 2006 8:07 AM
To: rss-board@yahoogroups.com
Subject: [rss-board] Vote: Recommend the Feed Validator
Today begins the seven-day voting period for this proposal, which was
made by Eric Lunt and I and seconded by Randy Charles Morin.
Use this mailing list to cast your vote, which can be Yes (or +1) to
support the proposal, No (or -1) to oppose it, and Abstain (or 0) to
defer the decision to the rest of the board.
Voting's a requirement of board membership [1], so please do so in the
next seven days.
PROPOSAL
In the time I've been serving on the RSS Advisory Board, I've been asked
fairly often to look at a Really Simple Syndication feed and help
someone figure out why it isn't working.
The first thing I do in response is load it in the Feed Validator [2],
the open source validator developed by Sam Ruby, Mark Pilgrim, Joseph
Walton and Phil Ringnalda that supports RSS and Atom. I did the same
thing when I was drafting the proposed specification, pasting each
example into a sample document [3] and running it through the validator
to catch potential mistakes.
At FeedBurner, Eric Lunt has a similar troubleshooting approach when
users have problems with their feeds, so we're making a joint proposal.
Proposed: The board should officially recommend and use the Feed
Validator.
A validator complements a specification, as long as they're in
agreement. In the three years the validator has been around, I've asked
Sam a half-dozen times about its interpretation of RSS, and each time he
was quick to address my concerns. If there's an area where the validator
and board members have disagreed over an aspect of RSS, my experience
has been that he eagerly defers to our judgment.
I've leaned on the validator so often that I recently became one of the
developers [4] so I could pitch in on RSS-related issues.
1: http://www.rssboard.org/charter
2: http://feedvalidator.org
3: http://www.rssboard.org/files/rss-2.0-sample.xml
4: http://sourceforge.net/projects/feedvalidator
Yahoo! Groups Links
Opera has joined MSIE and Firefox in adopting the common syndication icon:
http://www.cadenhead.org/workbench/news/2859
I'm not a web designer or usability guru, but I've been talking up
this effort since Microsoft adopted it. Millions of people are going
to associate the orange blibbet with the concept of syndication when
IE 7 launches, so the rest of us ought to consider following along.
Any thoughts on whether the board should offer official support for
it, both as an endorsement and by using it on our site?
> Opera has joined MSIE and Firefox in adopting the common syndication icon:
>
> http://www.cadenhead.org/workbench/news/2859
>
> I'm not a web designer or usability guru, but I've been talking up
> this effort since Microsoft adopted it. Millions of people are going
> to associate the orange blibbet with the concept of syndication when
> IE 7 launches, so the rest of us ought to consider following along.
>
> Any thoughts on whether the board should offer official support for
> it, both as an endorsement and by using it on our site?
I think the idea of a common syndication icon is wonderful. I've always
hated the orange "RSS" box that people have used, it just makes no sense
unless you already understand the value and meaning of RSS. Granted, more
people do now, but still...
One of the things that's always bothered me about RSS (not the format per
se, but the marketing of the concept) from the get-go was the way it foisted
another acronym on the less tech savvy, and totally did nothing to explain
the benefit of using RSS. Sticking orange RSS labels on sites certainly
didn't help.
I like what you (Rogers) wrote in your post wrt language (feed, reader,
subscribe) because it helps move the idea of syndication away from the
technicality of formats (which regardless of what us geeks think about RSS
1.0, 2.0, some other fork, Atom, etc., most people couldn't care less as
long as the stuff arrives in their reader/browser when it's new) and closer
to a real-world natural language description of what's happening. As you
say, "The technical details ought to fade into the background."
It may be beyond the scope of what we're supposed to be doing as an
organization, but to me it's important that we work towards
ease-of-use/usability with everything we do. I think endorsing the icon is a
good start in this direction. Any idea if Safari plans to adopt it?
Thanks,
-meg
Dave Winer and John Palfrey have voiced some new concerns about the
continued operation of the RSS Advisory Board.
I walk through the process of how the board got from the old, private
membership to the present on my personal weblog:
http://www.cadenhead.org/workbench/news/2860
Before new members were recruited, I felt very strongly that you
should not have to inherit the disagreements and structural problems
that kept the board from being fully effective in the past.
This was the primary impetus behind the launch of a new web site and
the work being done on a proposed specification. When Dave and John
told me privately they didn't want work to be done on the old site or
the old spec, I figured the best course of action was to start a new
site and a new spec, even though I had editing privileges on the old
site and was hoping to keep running it there.
I serve as chair and webmaster at your discretion.
Any decisions made up to this point by the board are subject to your
reevaluation, and any declarations of what we take as our mission for
the future are your decision to make.
> This was the primary impetus behind the launch of a new web site and
> the work being done on a proposed specification. When Dave and John
> told me privately they didn't want work to be done on the old site or
> the old spec, I figured the best course of action was to start a new
> site and a new spec, even though I had editing privileges on the old
> site and was hoping to keep running it there.
Could someone clarify for me what we mean by "new spec" and "old spec"?
My understanding was that "new spec" meant re-writing the existing spec so
that it was easier to understand and implement (e.g provide better
documentation, examples, etc.). I did not think it meant changing the spec
(e.g. adding new elements, removing un-used elements, etc.). Am I confused?
Thanks,
-meg
--- In rss-board@yahoogroups.com, Meg Hourihan <meg@...> wrote:
> My understanding was that "new spec" meant re-writing the existing
spec so
> that it was easier to understand and implement (e.g provide better
> documentation, examples, etc.). I did not think it meant changing
the spec
> (e.g. adding new elements, removing un-used elements, etc.).
That's my intent as well.
The new spec (a.k.a. proposed spec) is being developed as an effort to
document the existing format without adding or removing elements or
attributes. That's what I'm hoping to bring to the board for
consideration in early April (assuming it's ready).
My personal belief is that holding to the existing element set of RSS
is important, because that's the format Microsoft will be supporting
in its new OS and MSIE 7.
Rogers, what are you suggesting? Are you saying that Dave Winer and John
Palfrey want to shut down the RSS Advisory Board?
Dave
rcade wrote:
> Dave Winer and John Palfrey have voiced some new concerns about the
> continued operation of the RSS Advisory Board.
>
> I walk through the process of how the board got from the old, private
> membership to the present on my personal weblog:
>
> http://www.cadenhead.org/workbench/news/2860
>
> Before new members were recruited, I felt very strongly that you
> should not have to inherit the disagreements and structural problems
> that kept the board from being fully effective in the past.
>
> This was the primary impetus behind the launch of a new web site and
> the work being done on a proposed specification. When Dave and John
> told me privately they didn't want work to be done on the old site or
> the old spec, I figured the best course of action was to start a new
> site and a new spec, even though I had editing privileges on the old
> site and was hoping to keep running it there.
>
> I serve as chair and webmaster at your discretion.
>
> Any decisions made up to this point by the board are subject to your
> reevaluation, and any declarations of what we take as our mission for
> the future are your decision to make.
>
>
>
>
>
>
> SPONSORED LINKS
> Xml format
>
<http://groups.yahoo.com/gads?t=ms&k=Xml+format&w1=Xml+format&w2=Advisory+board&\
c=2&s=36&.sig=KSg7t3lUtXUVPpohyDwW9A>
> Advisory board
>
<http://groups.yahoo.com/gads?t=ms&k=Advisory+board&w1=Xml+format&w2=Advisory+bo\
ard&c=2&s=36&.sig=nyPlw7lUdOy3F9-YtxxLjw>
>
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
> * Visit your group "rss-board
> <http://groups.yahoo.com/group/rss-board>" on the web.
>
> * To unsubscribe from this group, send an email to:
> rss-board-unsubscribe@yahoogroups.com
> <mailto:rss-board-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>
--
David L. Sifry
Founder and CEO, Technorati, Inc.
dsifry@...
415 846-0232 (Mobile)
> --- In rss-board@yahoogroups.com, Meg Hourihan <meg@...> wrote:
>> My understanding was that "new spec" meant re-writing the existing
> spec so
>> that it was easier to understand and implement (e.g provide better
>> documentation, examples, etc.). I did not think it meant changing
> the spec
>> (e.g. adding new elements, removing un-used elements, etc.).
>
> That's my intent as well.
Ok, yay! I'm not confused.
> The new spec (a.k.a. proposed spec) is being developed as an effort to
> document the existing format without adding or removing elements or
> attributes. That's what I'm hoping to bring to the board for
> consideration in early April (assuming it's ready).
>
> My personal belief is that holding to the existing element set of RSS
> is important, because that's the format Microsoft will be supporting
> in its new OS and MSIE 7.
I agree.
-meg
> Rogers, what are you suggesting? Are you saying that Dave Winer and John
> Palfrey want to shut down the RSS Advisory Board?
I think Winer wants to shut down the board (see his post today, "2. The RSS
Advisory Board, when it existed, performed a support function.") I'm not
sure why the board cannot continue to exist and perform a support function.
That's what I thought we were doing.
I do not know John Palfrey nor what his stance is. It seems there is some
misunderstanding wrt the intent of this board. We are not trying to change
RSS or fork it, or take control of it, or anything. And I didn't accept
Rogers invitation to join this Board in any hopes of "owning the spec" to
RSS.
It's all this kind of squabbling that's kept me quite removed from any
public RSS discussions in the past. I'd hoped we were past that now, but it
seems that's not the case. :(
-meg
Meg Hourihan wrote:
>
> It's all this kind of squabbling that's kept me quite removed from any
> public RSS discussions in the past. I'd hoped we were past that now,
> but it
> seems that's not the case. :(
>
> -meg
>
Meg, I totally agree. I've gotta say that this is somewhat disturbing
to me. Looking forward to hearing some more clarifying info from Rogers.
Dave
--
David L. Sifry
Founder and CEO, Technorati, Inc.
dsifry@...
415 846-0232 (Mobile)
--- In rss-board@yahoogroups.com, David Sifry <dsifry@...> wrote:
> Rogers, what are you suggesting? Are you saying that Dave Winer
> and John Palfrey want to shut down the RSS Advisory Board?
My understanding of Palfrey's position is that his interest begins and
ends with the spec Harvard received from UserLand in 2003. He wants to
ensure that it always will be published permanently at this URL:
http://blogs.law.harvard.edu/tech/rss
Right now, he's running the current spec at that URL, which includes
subsequent work by the board and was last published Jan. 25, 2005. I
offered him a copy of the 2003 revision of the spec, which the board
mirrors here:
http://www.rssboard.org/rss-2-0-1
As for Dave Winer, I agree with him that this organization has a
conservative mission, is not a standards body, and does not own RSS,
as the license of the proposed spec make clear:
http://www.rssboard.org/rss-draft-1#license
We do own the newly written spec, and that's for a reason -- we need
the ability to withdraw it from distribution if the board ultimately
decides not to adopt it.
I've added a new tool to the RSS Advisory Board site that makes it
easier to test RSS element and attribute values against the Feed
Validator:
http://www.rssboard.org/rss-playground
The RSS Playground tool uses a valid RSS document as a starting point,
letting you change values and create a new document that stays online
for 72 hours.
Here's a sample file I created with it to see what the Feed Validator
does with RFC 2822 date-time values:
http://www.rssboard.org/rss-playground-xml/1140375571
Very nice! What a great tool to have on hand. About the only thing I
could think to add would be a way to omit an element, but that's a minor
point. I really like this. Thank you!
rcade wrote:
> I've added a new tool to the RSS Advisory Board site that makes it
> easier to test RSS element and attribute values against the Feed
> Validator:
>
> http://www.rssboard.org/rss-playground
>
> The RSS Playground tool uses a valid RSS document as a starting point,
> letting you change values and create a new document that stays online
> for 72 hours.
>
> Here's a sample file I created with it to see what the Feed Validator
> does with RFC 2822 date-time values:
>
> http://www.rssboard.org/rss-playground-xml/1140375571
>
>
--
Eric Lunt | FeedBurner
eric@... | http://www.feedburner.comhttp://www.burningdoor.com/eric |
I didn't think about this vote ending on a holiday when I posted the
proposal -- sorry about that.
Ross Mayfield sent this to me in e-mail today:
If it is not too late, I vote for the validator.
Could we setup a Webpage on rssboard.org that has a form that submits
to the FeedValidator?
Thanks Rogers,
Randy
--- In rss-board@yahoogroups.com, "rcade" <rcade@...> wrote:
>
> I didn't think about this vote ending on a holiday when I posted the
> proposal -- sorry about that.
>
> Ross Mayfield sent this to me in e-mail today:
>
> If it is not too late, I vote for the validator.
>
Send Email
