You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
142 lines
15 KiB
XML
142 lines
15 KiB
XML
15 years ago
|
<?xml version="1.0"?>
|
||
|
|
<!-- RSS generated by UserLand Frontier v9.5 on Mon, 23 Jan 2006 20:08:00 GMT -->
|
||
|
|
<rss version="2.0" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:dc="http://purl.org/dc/elements/1.1/">
|
||
|
|
<channel>
|
||
|
|
<title>Really Simple Syndication</title>
|
||
|
|
<link>http://blogs.law.harvard.edu/tech/</link>
|
||
|
|
<description>RSS Advisory Board announcements and RSS news</description>
|
||
|
|
<creativeCommons:license>http://creativecommons.org/licenses/by-sa/1.0/</creativeCommons:license>
|
||
|
|
<language>en-us</language>
|
||
|
|
<pubDate>Sat, 21 Jan 2006 05:00:00 GMT</pubDate>
|
||
|
|
<lastBuildDate>Sun, 22 Jan 2006 02:01:58 GMT</lastBuildDate>
|
||
|
|
<docs>http://backend.userland.com/rss</docs>
|
||
|
|
<generator>UserLand Frontier v9.5</generator>
|
||
|
|
<category domain="http://www.weblogs.com/rssUpdates/changes.xml">rssUpdates</category>
|
||
|
|
<managingEditor>rcade@yahoo.com</managingEditor>
|
||
|
|
<webMaster>rcade@yahoo.com</webMaster>
|
||
|
|
<item>
|
||
|
|
<title>Simple Syndication in Communist China</title>
|
||
|
|
<link>http://english.peopledaily.com.cn/rss/rss.html</link>
|
||
|
|
<description>The English language edition of <a href="http://english.peopledaily.com.cn/">People's Daily</a>, the official newspaper of the Communist Party of China, offers <a href="http://english.peopledaily.com.cn/rss/rss.html">18 RSS 2.0 newsfeeds</a>.<br>
|
||
|
|
<br>
|
||
|
|
In addition to feeds on current events in news, business, sports, and
|
||
|
|
other areas, the paper devotes feeds to party leaders such as Chinese
|
||
|
|
President <a href="http://english.people.com.cn/rss/hujintao.xml">Hu Jintao</a> and Premier <a href="http://english.peopledaily.com.cn/rss/rss.html">Wen Jiabao</a>.<br>
|
||
|
|
<br>
|
||
|
|
Outside observers of China often look to <span style="font-style: italic;">People's Daily</span> for clues about the inner workings of the government, as described in <a href="http://en.wikipedia.org/wiki/People%27s_Daily">Wikipedia</a>:<br>
|
||
|
|
<p style="margin-left: 40px;">Newspaper articles in the <span style="font-style: italic;">People's Daily</span> are often not read for
|
||
|
|
content, so much as placement. A large number of articles devoted to a
|
||
|
|
political figure or idea is often taken as a sign that that official is
|
||
|
|
rising.</p><br><br><div style="margin-left: 40px;">In addition, editorials in the <i>People's Daily</i> are also still regarded as fairly authoritative statements of government policy.<br>
|
||
|
|
</div></description>
|
||
|
|
<dc:creator>Rogers Cadenhead</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2005/07/10#a852</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=852&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2005%2F07%2F10%23a852</comments>
|
||
|
|
</item>
|
||
|
|
<item>
|
||
|
|
<title>RSS Takes Flight at NASA</title>
|
||
|
|
<link>http://www.nasa.gov/rss/</link>
|
||
|
|
<description>The National Aeronautics and Space Administration makes extensive use
|
||
|
|
of RSS 2.0 to provide news, photographs, and press releases on upcoming
|
||
|
|
missions and other space-related topics.<br>
|
||
|
|
<br>
|
||
|
|
People looking ahead to the planned July 13 launch of the space shuttle Discovery can subscribe to a <a href="http://www.nasa.gov/rss/rtf_news.rss">Return to Flight RSS feed</a>.<br>
|
||
|
|
<br>
|
||
|
|
NASA's RSS information page also includes an interesting demonstration of an RSS viewer created in Macromedia Flash.<br></description>
|
||
|
|
<dc:creator>Rogers Cadenhead</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2005/07/09#a851</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=851&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2005%2F07%2F09%23a851</comments>
|
||
|
|
</item>
|
||
|
|
<item>
|
||
|
|
<title>RSS Usage Skyrockets in the U.S.</title>
|
||
|
|
<link>http://blogs.law.harvard.edu/tech/2005/01/04#a821</link>
|
||
|
|
<description>Six million Americans get news and information from RSS aggregators, according to a <a href="http://www.pewinternet.org/pdfs/PIP_blogging_data.pdf">nationwide telephone survey</a> conducted by the Pew Internet and American Life Project in November.<br>
|
||
|
|
<br>
|
||
|
|
The project, an ongoing survey of the 120 million Americans using the
|
||
|
|
Internet, found that 5 percent follow their favorite sources through
|
||
|
|
RSS syndication. "This is a first-time measurement from our surveys and
|
||
|
|
is an indicator that this application is gaining an impressive
|
||
|
|
foothold."<br>
|
||
|
|
<br>
|
||
|
|
The survey also found that 27 percent of those polled are weblog
|
||
|
|
readers, a 58 percent jump in the 9 months since the preceding poll was
|
||
|
|
conducted.<br></description>
|
||
|
|
<dc:creator>Rogers Cadenhead</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2005/01/04#a821</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=821&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2005%2F01%2F04%23a821</comments>
|
||
|
|
</item>
|
||
|
|
<item>
|
||
|
|
<title>Added link to encoding examples in RSS 2.0 spec</title>
|
||
|
|
<link>http://blogs.law.harvard.edu/tech/2004/06/19#a683</link>
|
||
|
|
<description><P>We added a link to a page of <A href="http://blogs.law.harvard.edu/tech/encodingDescriptions">encoding examples</A> for descriptions, <A href="http://blogs.law.harvard.edu/tech/rss#hrelementsOfLtitemgt">under</A> Elements of &lt;item>. The change is also <A href="http://blogs.law.harvard.edu/tech/rssChangeNotes#61904Dw">noted</A> on the Change Notes page.</P></description>
|
||
|
|
<dc:creator>Dave Winer</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2004/06/19#a683</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=683&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2004%2F06%2F19%23a683</comments>
|
||
|
|
</item>
|
||
|
|
<item>
|
||
|
|
<title>Proposed clarification for RSS 2.0 spec (revised)</title>
|
||
|
|
<link>http://blogs.law.harvard.edu/tech/2004/06/15#a648</link>
|
||
|
|
<description><P>Here's a revised proposal for a clarification to the RSS 2.0 spec.</P>
|
||
|
|
<P>Under <A href="http://blogs.law.harvard.edu/tech/rss#hrelementsOfLtitemgt">Elements of &lt;item></A>, replace the lead paragraph with the following.<BR></P>
|
||
|
|
<BLOCKQUOTE>
|
||
|
|
<P>A channel may contain any number of &lt;item>s. An item may represent a "story" -- much like a story in a newspaper or magazine; if so its description is a synopsis of the story, and the link points to the full story. An item may also be complete in itself, if so, the description contains the text (entity-encoded HTML is allowed<FONT color=green><B>; see <A style="COLOR: green" href="http://blogs.law.harvard.edu/tech/encodingDescriptions">examples</A></B></FONT>), and the link and title may be omitted. All elements of an item are optional, however at least one of title or description must be present.</P></BLOCKQUOTE>
|
||
|
|
<P><STRONG>Notes</STRONG>: The new text is in green. The word examples links to a <A href="http://blogs.law.harvard.edu/tech/encodingDescriptions">page</A> of examples of encodings. We'd like to make the changes to the spec early next week.&nbsp;&nbsp;If you have concerns about this change, please post a comment below, and we will review them before making the change. Thanks to everyone who has participated in the discussion thus far.</P></description>
|
||
|
|
<dc:creator>Andrew Grumet</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2004/06/15#a648</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=648&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2004%2F06%2F15%23a648</comments>
|
||
|
|
</item>
|
||
|
|
<item>
|
||
|
|
<title>Proposed clarification for RSS 2.0 spec</title>
|
||
|
|
<link>http://blogs.law.harvard.edu/tech/2004/06/04#a553</link>
|
||
|
|
<description><P>Requesting comments on a couple of proposed clarifications to the <A href="http://blogs.law.harvard.edu/tech/rss#hrelementsOfLtitemgt">RSS 2.0 spec</A>.</P>
|
||
|
|
<P>1. Under Elements of &lt;item>, replace the lead paragraph with the following. The new text is highlighted in green.</P>
|
||
|
|
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
|
||
|
|
<P>A channel may contain any number of &lt;item>s. An item may represent a "story" -- much like a story in a newspaper or magazine; if so its description is a synopsis of the story, and the link points to the full story. An item may also be complete in itself, if so, the description contains the text, and the link and title may be omitted. <B><FONT color=green>Either way, &lt;description> contains entity-encoded HTML</FONT>.</B> All elements of an item are optional, however at least one of title or description must be present.</P></BLOCKQUOTE>
|
||
|
|
<P>2. Immediately following that section, a link to a <A href="http://blogs.law.harvard.edu/tech/encodingDescriptions">page of examples</A>, authored by Nick Bradbury, author of the FeedDemon aggregator.</P>
|
||
|
|
<P><STRONG>Notes: </STRONG>We believe aggregators already assume the&nbsp;item-level description contains entity-encoded HTML.&nbsp; We'd like to make the changes to the spec early next week and if there are no deal-stoppers, we will. Please comment below. Off-topic and personal comments will be deleted.</P>
|
||
|
|
<P><STRONG>Thanks to:</STRONG> Nick Bradbury, Brent Simmons, Greg Reinacker, Jake Savin, Dare Obasanjo, Matt Mullenweg for their help working out this proposed clarification.</P></description>
|
||
|
|
<dc:creator>Dave Winer</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2004/06/04#a553</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=553&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2004%2F06%2F04%23a553</comments>
|
||
|
|
</item>
|
||
|
|
<item>
|
||
|
|
<title>RSS documentation updates</title>
|
||
|
|
<link>http://blogs.law.harvard.edu/tech/2004/05/31#a550</link>
|
||
|
|
<description>If you're not tracking this site's <A href="http://blogs.law.harvard.edu/tech/rssChangeNotes">change notes page</A>, you might have missed a few minor edits to the documentation for RSS 2.0:<BR>
|
||
|
|
<UL>
|
||
|
|
<LI>The <A href="http://cyber.law.harvard.edu/blogs/gems/tech/rss2sample.xml">RSS 2.0 sample file</A> has been updated.
|
||
|
|
<LI>An <A href="http://blogs.law.harvard.edu/tech/rssChangeNotes#53104Dw">encoding issue</A> has been fixed on the <A href="http://blogs.law.harvard.edu/tech/skipHoursDays">skipHours and skipDays</A> page. </LI></UL>Suggestions for further improvements to the documentation are encouraged.<BR><BR></description>
|
||
|
|
<dc:creator>Rogers Cadenhead</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2004/05/31#a550</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=550&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2004%2F05%2F31%23a550</comments>
|
||
|
|
</item>
|
||
|
|
<item>
|
||
|
|
<title>The role of the advisory board</title>
|
||
|
|
<link>http://blogs.law.harvard.edu/tech/2004/05/18#a540</link>
|
||
|
|
<description>There's been some confusion about the role of the advisory board. The purpose of this post to try to clear it up.<BR><BR>1. It's got a very conservative mission, to answer questions about RSS, to help people use it, to promote its use. It's basically a support function. <BR><BR>2. Anyone can extend RSS through namespaces. We suggest that people look first to see if there is a core element that already does what they need to do, and if so, use that instead of inventing a new one. That will keep the work of aggregator developers to a minimum, keep the barriers to entry low, help keep the market competitive. Competition should be based on features, performance and price, not compatibility. Compatibility should be easy.<BR><BR>3. Emphatically, this group is not a standards organization. It does not own RSS, or the spec, it has no more or less authority than any other group of people who wish to promote RSS.</description>
|
||
|
|
<dc:creator>Dave Winer</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2004/05/18#a540</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=540&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2004%2F05%2F18%23a540</comments>
|
||
|
|
</item>
|
||
|
|
<item>
|
||
|
|
<title>Why are dates RFC 822?</title>
|
||
|
|
<link>http://blogs.law.harvard.edu/tech/2004/05/16#a534</link>
|
||
|
|
<description><P>Gene Saunders writes: "Why does RSS 2.0 use RFC 822 instead of the (infinitely more modern) RFC 2822?"</P>
|
||
|
|
<P>Here's why we went with RFC 822:</P>
|
||
|
|
<P>1. Any scripting software that was used in Internet applications would already have to deal with RFC 822 dates, since that was the format used in email. For most app developers, I imagined, they already had library routines that dealt with 822 format dates. The script environment I was using certainly did. Over the years I've never heard a complaint that people were unable to process 822 dates. <img src="http://static.userland.com/shortcuts/images/qbullets/sidesmiley.gif"></P>
|
||
|
|
<P>2. 822 dates are not only machine readable, they are also human readable. One of the <A href="http://davenet.scripting.com/2000/09/02/whatToDoAboutRss#rssIsAboutSimplicity">goals</A> of RSS was to be non-intimidating for non-technical users -- they should be able to look at a file and make sense of what's there, where ever possible. </P>
|
||
|
|
<P>3. Believe it or not, the decision was made in 1997, seven years ago. RSS is a venerable institution, so its anachronisms should be appreciated&nbsp;as one respects a fine wine or an elder statesman, or a format that spawned an incredible market.</P></description>
|
||
|
|
<dc:creator>Dave Winer</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2004/05/16#a534</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=534&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2004%2F05%2F16%23a534</comments>
|
||
|
|
</item>
|
||
|
|
<item>
|
||
|
|
<title>Speed Meets Feed in Download Tool</title>
|
||
|
|
<link>http://blogs.law.harvard.edu/tech/2004/03/15#a519</link>
|
||
|
|
<description><A href="http://www.wired.com/news/infostructure/0,1377,62651,00.html">Wired</A>: "A demo publishing system launched Friday by a popular programmer and blogger merges two of this season's hottest tech fads -- RSS news syndication and BitTorrent file sharing -- to create a cheap publishing system for what its author calls 'big media objects.' The hybrid system is meant to eliminate both the publisher's need for fat bandwidth, and the consumer's need to wait through a grueling download."</description>
|
||
|
|
<dc:creator>Dave Winer</dc:creator>
|
||
|
|
<guid>http://blogs.law.harvard.edu/tech/2004/03/15#a519</guid>
|
||
|
|
<comments>http://blogs.law.harvard.edu/tech/comments?u=tech&amp;p=519&amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Ftech%2F2004%2F03%2F15%23a519</comments>
|
||
|
|
</item>
|
||
|
|
</channel>
|
||
|
|
</rss>
|