Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

rss-profile => rss-profile-1

git-svn-id: http://feedvalidator.googlecode.com/svn/trunk@838 34a10a33-d82d-0410-ba40-81c901463ecc
  • Loading branch information...
commit ba058ef848e27d7967ad6a8c3ad92e944975d54d 1 parent 49af4b9
@rubys authored
Showing with 240 additions and 30 deletions.
  1. +1 −1  docs-xml/error/InvalidContact.xml
  2. +1 −1  docs-xml/error/UseZeroForUnknown.xml
  3. +2 −2 docs-xml/warning/CharacterData.xml
  4. +1 −1  docs-xml/warning/ContainsHTML.xml
  5. +1 −1  docs-xml/warning/DuplicateEnclosure.xml
  6. +1 −1  docs-xml/warning/EmailFormat.xml
  7. +1 −1  docs-xml/warning/ImageTitleDoesntMatch.xml
  8. +1 −1  docs-xml/warning/ImplausibleDate.xml
  9. +1 −1  docs-xml/warning/MisplacedItem.xml
  10. +1 −1  docs-xml/warning/MissingAtomSelfLink.xml
  11. +1 −1  docs-xml/warning/MissingRealName.xml
  12. +1 −1  docs-xml/warning/NeedDescriptionBeforeContent.xml
  13. +1 −1  docs-xml/warning/SlashDate.xml
  14. +1 −1  docs/error/InvalidContact.html
  15. +1 −1  docs/error/UseZeroForUnknown.html
  16. +2 −2 docs/warning/CharacterData.html
  17. +1 −1  docs/warning/ContainsHTML.html
  18. +70 −0 docs/warning/Deprecated.html
  19. +70 −0 docs/warning/DeprecatedRootHref.html
  20. +1 −1  docs/warning/DuplicateEnclosure.html
  21. +1 −1  docs/warning/EmailFormat.html
  22. +1 −1  docs/warning/ImageTitleDoesntMatch.html
  23. +1 −1  docs/warning/ImplausibleDate.html
  24. +70 −0 docs/warning/InvalidKmlMediaType.html
  25. +1 −1  docs/warning/MisplacedItem.html
  26. +1 −1  docs/warning/MissingAtomSelfLink.html
  27. +1 −1  docs/warning/MissingRealName.html
  28. +1 −1  docs/warning/NeedDescriptionBeforeContent.html
  29. +1 −1  docs/warning/SlashDate.html
  30. +1 −1  news/archives/2007/10/15/rss_best_practices.html
  31. +1 −1  news/index.html
View
2  docs-xml/error/InvalidContact.xml
@@ -18,7 +18,7 @@ addresses:</p>
</ul>
<p>Alternately, if the intent is to credit authorship without revealing
e-mail addresses, consider using the
-<a href="http://www.rssboard.org/rss-profile#namespace-elements-dublin-creator">dc:creator</a> element instead.</p>
+<a href="http://www.rssboard.org/rss-profile-1#namespace-elements-dublin-creator">dc:creator</a> element instead.</p>
</div>
</div>
</fvdoc>
View
2  docs-xml/error/UseZeroForUnknown.xml
@@ -7,7 +7,7 @@
<p>This value must be an integer greater than or equal to zero. It can not be negative, or a decimal, or a fraction, or a string, or blank.</p>
</div>
<div id='solution'>
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#element-channel-item-enclosure">Best Practices Profile</a>, when an enclosure's size cannot be determined, a publisher <span class="rfc2119">should</span> use a length of 0.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#element-channel-item-enclosure">Best Practices Profile</a>, when an enclosure's size cannot be determined, a publisher <span class="rfc2119">should</span> use a length of 0.</p>
</div>
</div>
</fvdoc>
View
4 docs-xml/warning/CharacterData.xml
@@ -4,9 +4,9 @@
<p>Encode "&amp;" and "&lt;" in plain text using hexadecimal character references.</p>
</div>
<div id='explanation'>
-<p>The specification has lacked clarity regarding whether HTML is permitted in elements other than an item's <a href="http://www.rssboard.org/rss-profile#element-channel-item-description">description</a>, leading to wide variance in how aggregators treat character data in other elements. This makes it especially difficult for a publisher to determine how to encode the characters "&lt;" and "&gt;", which must be encoded in XML.</p>
+<p>The specification has lacked clarity regarding whether HTML is permitted in elements other than an item's <a href="http://www.rssboard.org/rss-profile-1#element-channel-item-description">description</a>, leading to wide variance in how aggregators treat character data in other elements. This makes it especially difficult for a publisher to determine how to encode the characters "&lt;" and "&gt;", which must be encoded in XML.</p>
<p>In elements that contain plain text, the form of encoding that works in the widest number of aggregators is using the hexadecimal character reference &amp;#x26; to represent "&amp;" and &amp;#x3C; to represent "&lt;".</p>
-<p>See <a href="http://www.rssboard.org/rss-profile#data-types-characterdata">Character Data</a> in the <a href="http://www.rssboard.org/rss-profile">RSS Advisory Board's Best Practices Profile (Proposed)</a> for additional requirements and recommendations.</p>
+<p>See <a href="http://www.rssboard.org/rss-profile-1#data-types-characterdata">Character Data</a> in the <a href="http://www.rssboard.org/rss-profile">RSS Advisory Board's Best Practices Profile (Proposed)</a> for additional requirements and recommendations.</p>
</div>
<div id='solution'>
<p>A publisher <span class="rfc2119">should</span> encode "&amp;" and "&lt;" in plain text using hexadecimal character references. When encoding the "&gt;" character, a publisher <span class="rfc2119">should</span> use the hexadecimal reference &amp;#x3E;.</p>
View
2  docs-xml/warning/ContainsHTML.xml
@@ -21,7 +21,7 @@ For example:</p>
<p>Encoding of the characters <code>"&amp;"</code> and <code>"&lt;"</code>
are especially problematic in places like RSS 2.0 titles.&#160; For the widest
interop, the
-<a href="http://www.rssboard.org/rss-profile#data-types-characterdata">RSS Profile</a>
+<a href="http://www.rssboard.org/rss-profile-1#data-types-characterdata">RSS Profile</a>
recommends the use of the hexadecimal character reference
"<code>&amp;#x26;</code>" to represent "<code>&amp;</code>" and
"<code>&amp;#x3C;</code>" to represent "<code>&lt;</code>".</p>
View
2  docs-xml/warning/DuplicateEnclosure.xml
@@ -4,7 +4,7 @@
<p><code>item</code> contains more than one <code>enclosure</code></p>
</div>
<div id='explanation'>
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#element-channel-item-enclosure">Best Practices Profile</a>, support for the enclosure element in RSS software varies significantly because of disagreement over whether the specification permits more than one enclosure per item. Although the author intended to permit no more than one enclosure in each item, this limit is not explicit in the specification.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#element-channel-item-enclosure">Best Practices Profile</a>, support for the enclosure element in RSS software varies significantly because of disagreement over whether the specification permits more than one enclosure per item. Although the author intended to permit no more than one enclosure in each item, this limit is not explicit in the specification.</p>
<p>For best support in the widest number of aggregators, an item <span class="rfc2119">should not</span> contain more than one enclosure.</p>
<!--
<p>Here are a few links to prior discussions on the topic:</p>
View
2  docs-xml/warning/EmailFormat.xml
@@ -4,7 +4,7 @@
<p>Email address is not in recommended format</p>
</div>
<div id='explanation'>
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#data-types-email">Best Practices Profile</a>, the <span class="rfc2119">recommended</span> format for e-mail addresses in RSS elements is <span class="template">username@hostname.tld (Real Name)</span>, as in the following example:</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#data-types-email">Best Practices Profile</a>, the <span class="rfc2119">recommended</span> format for e-mail addresses in RSS elements is <span class="template">username@hostname.tld (Real Name)</span>, as in the following example:</p>
<blockquote><pre>&lt;managingEditor&gt;luksa@dallas.example.com (Frank Luksa)&lt;/managingEditor&gt;</pre></blockquote>
</div>
View
2  docs-xml/warning/ImageTitleDoesntMatch.xml
@@ -4,7 +4,7 @@
<p>Image title doesn't match channel title</p>
</div>
<div id='explanation'>
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#element-channel-image-title">Best Practices Profile</a>, this element <span class="rfc2119">should</span> have the same text as the channel's <a href="#element-channel-title">title</a> element</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#element-channel-image-title">Best Practices Profile</a>, this element <span class="rfc2119">should</span> have the same text as the channel's <a href="#element-channel-title">title</a> element</p>
</div>
<div id='solution'>
<p>Repeat the channel's title element in the image.</p>
View
2  docs-xml/warning/ImplausibleDate.xml
@@ -10,7 +10,7 @@ in the future, or far enough in the past to indicate that there might either be
<a href="http://blogs.law.harvard.edu/tech/rss#ltpubdategtSubelementOfLtitemgt">anticipated</a>
that some aggregators may chose to ignore items with pubDates in the future,
this practice
-<a href="http://www.rssboard.org/rss-profile#element-channel-item-pubdate">never seemed to catch on</a>.</p>
+<a href="http://www.rssboard.org/rss-profile-1#element-channel-item-pubdate">never seemed to catch on</a>.</p>
<p>Instead, many clients sort by dates, either by default, or as an option. For this reason, it is important that date values are as accurate as possible.</p>
</div>
<div id='solution'>
View
2  docs-xml/warning/MisplacedItem.xml
@@ -4,7 +4,7 @@
<p>Misplaced Item</p>
</div>
<div id='explanation'>
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#element-channel">Best Practices Profile</a>, all item elements <span class="rfc2119">should</span> appear after all of the other elements in a channel.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#element-channel">Best Practices Profile</a>, all item elements <span class="rfc2119">should</span> appear after all of the other elements in a channel.</p>
</div>
<div id='solution'>
<p>Move all <code>item</code> elements to the bottom of the channel.</p>
View
2  docs-xml/warning/MissingAtomSelfLink.xml
@@ -4,7 +4,7 @@
<p>Missing <code>atom:link</code> with <code>rel="self"</code></p>
</div>
<div id='explanation'>
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#namespace-elements-atom-link">Best Practices Profile</a>, identifying a feed's URL within the feed makes it more portable, self-contained, and easier to cache. For these reasons, a feed <span class="rfc2119">should</span> contain an <span class="element">atom:link</span> used for this purpose.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#namespace-elements-atom-link">Best Practices Profile</a>, identifying a feed's URL within the feed makes it more portable, self-contained, and easier to cache. For these reasons, a feed <span class="rfc2119">should</span> contain an <span class="element">atom:link</span> used for this purpose.</p>
</div>
<div id='solution'>
<p>Insert a fully qualified <code>atom:link</code> to your feed using <code>rel="self"</code>.</p>
View
2  docs-xml/warning/MissingRealName.xml
@@ -4,7 +4,7 @@
<p>Email address is missing real name</p>
</div>
<div id='explanation'>
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#data-types-email">Best Practices Profile</a>, the <span class="rfc2119">recommended</span> format for e-mail addresses in RSS elements is <span class="template">username@hostname.tld (Real Name)</span>, as in the following example:</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#data-types-email">Best Practices Profile</a>, the <span class="rfc2119">recommended</span> format for e-mail addresses in RSS elements is <span class="template">username@hostname.tld (Real Name)</span>, as in the following example:</p>
<blockquote><pre>&lt;managingEditor&gt;luksa@dallas.example.com (Frank Luksa)&lt;/managingEditor&gt;</pre></blockquote>
</div>
View
2  docs-xml/warning/NeedDescriptionBeforeContent.xml
@@ -8,7 +8,7 @@
<p>Publishers who employ summaries <span class="rfc2119">should</span> store the summary in <span class="element">description</span> and the full content in <span class="element">content:encoded</span>, ordering <span class="element">description</span> first within the item. On items with no summary, the full content <span class="rfc2119">should</span> be stored in <span class="element">description</span>.</p>
-<p>See the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#namespace-elements-content-encoded">Best Practices Profile</a> for additional requirements and recommendations.</p>
+<p>See the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#namespace-elements-content-encoded">Best Practices Profile</a> for additional requirements and recommendations.</p>
</div>
<div id='solution'>
View
2  docs-xml/warning/SlashDate.xml
@@ -4,7 +4,7 @@
<p>Ensure <code>lastBuildDate</code> is present when <code>slash:comments</code> is used</p>
</div>
<div id='explanation'>
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#namespace-elements-slash-comments">Best Practices Profile</a>, because the Slash namespace lacks an element to indicate when the comment counts were compiled, publishers who use this element also should include a lastBuildDate element.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#namespace-elements-slash-comments">Best Practices Profile</a>, because the Slash namespace lacks an element to indicate when the comment counts were compiled, publishers who use this element also should include a lastBuildDate element.</p>
</div>
<div id='solution'>
<p>Add a lastBuildDate element to your channel.</p>
View
2  docs/error/InvalidContact.html
@@ -41,7 +41,7 @@
</ul>
<p>Alternately, if the intent is to credit authorship without revealing
e-mail addresses, consider using the
-<a href="http://www.rssboard.org/rss-profile#namespace-elements-dublin-creator">dc:creator</a> element instead.</p>
+<a href="http://www.rssboard.org/rss-profile-1#namespace-elements-dublin-creator">dc:creator</a> element instead.</p>
</div>
<h2>Not clear? Disagree?</h2>
<div class="docbody">
View
2  docs/error/UseZeroForUnknown.html
@@ -30,7 +30,7 @@
</div>
<h2>Solution</h2>
<div class="docbody">
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#element-channel-item-enclosure">Best Practices Profile</a>, when an enclosure's size cannot be determined, a publisher <span class="rfc2119">should</span> use a length of 0.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#element-channel-item-enclosure">Best Practices Profile</a>, when an enclosure's size cannot be determined, a publisher <span class="rfc2119">should</span> use a length of 0.</p>
</div>
<h2>Not clear? Disagree?</h2>
<div class="docbody">
View
4 docs/warning/CharacterData.html
@@ -26,9 +26,9 @@
<h2>Explanation</h2>
<div class="docbody">
-<p>The specification has lacked clarity regarding whether HTML is permitted in elements other than an item's <a href="http://www.rssboard.org/rss-profile#element-channel-item-description">description</a>, leading to wide variance in how aggregators treat character data in other elements. This makes it especially difficult for a publisher to determine how to encode the characters "&lt;" and "&gt;", which must be encoded in XML.</p>
+<p>The specification has lacked clarity regarding whether HTML is permitted in elements other than an item's <a href="http://www.rssboard.org/rss-profile-1#element-channel-item-description">description</a>, leading to wide variance in how aggregators treat character data in other elements. This makes it especially difficult for a publisher to determine how to encode the characters "&lt;" and "&gt;", which must be encoded in XML.</p>
<p>In elements that contain plain text, the form of encoding that works in the widest number of aggregators is using the hexadecimal character reference &amp;#x26; to represent "&amp;" and &amp;#x3C; to represent "&lt;".</p>
-<p>See <a href="http://www.rssboard.org/rss-profile#data-types-characterdata">Character Data</a> in the <a href="http://www.rssboard.org/rss-profile">RSS Advisory Board's Best Practices Profile (Proposed)</a> for additional requirements and recommendations.</p>
+<p>See <a href="http://www.rssboard.org/rss-profile-1#data-types-characterdata">Character Data</a> in the <a href="http://www.rssboard.org/rss-profile">RSS Advisory Board's Best Practices Profile (Proposed)</a> for additional requirements and recommendations.</p>
</div>
<h2>Solution</h2>
<div class="docbody">
View
2  docs/warning/ContainsHTML.html
@@ -44,7 +44,7 @@
<p>Encoding of the characters <code>"&amp;"</code> and <code>"&lt;"</code>
are especially problematic in places like RSS 2.0 titles.&#160; For the widest
interop, the
-<a href="http://www.rssboard.org/rss-profile#data-types-characterdata">RSS Profile</a>
+<a href="http://www.rssboard.org/rss-profile-1#data-types-characterdata">RSS Profile</a>
recommends the use of the hexadecimal character reference
"<code>&amp;#x26;</code>" to represent "<code>&amp;</code>" and
"<code>&amp;#x3C;</code>" to represent "<code>&lt;</code>".</p>
View
70 docs/warning/Deprecated.html
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<title>foo has been superceded by foo.</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="icon" href="http://www.feedvalidator.org/favicon.ico" />
+<link rel="shortcut icon" href="http://www.feedvalidator.org/favicon.ico" />
+<style type="text/css" media="screen">@import "../../css/common.css";
+@import "../../css/documentation.css";</style>
+<script type="text/javascript"><!-- --></script>
+<link rel="start" href="http://feedvalidator.org/docs/" title="Home" />
+</head>
+<body>
+<div id="logo">
+<h1><a href="../../"><span id="feed"><span id="f">F</span><span id="e1">E</span><span id="e2">E</span></span><span id="d">D</span> Validator</a></h1>
+<p>Documentation</p>
+<a class="skip" href="#startnavigation">Jump to navigation</a>
+</div> <!--logo-->
+
+<div id="main">
+<h2>Message</h2>
+<div class="docbody">
+<p><code>foo</code> has been superceded by <code>foo</code>.</p>
+</div>
+<h2>Explanation</h2>
+
+<div class="docbody">
+<p>XXX</p>
+</div>
+<h2>Solution</h2>
+<div class="docbody">
+<p>XXX</p>
+</div>
+<h2>Not clear? Disagree?</h2>
+<div class="docbody">
+<p>You might be able to find help in one of <a href="../howto/resources.html">these fine resources</a>.</p>
+</div>
+
+</div><!--main-->
+<div class="centered">
+<a name="startnavigation" id="startnavigation"></a>
+<div class="navbarWrapper">
+ <div class="navbarContent">
+ <img class="borderTL" src="../../images/borderTL.gif" alt="" width="14" height="14" />
+ <img class="borderTR" src="../../images/borderTR.gif" alt="" width="14" height="14" />
+
+<p>
+<a href="../../">Home</a> &middot;
+<a href="../../about.html">About</a> &middot;
+<a href="../../news/">News</a> &middot;
+<a href="../../docs/">Docs</a> &middot;
+<a href="../../terms.html">Terms</a>
+</p>
+
+ <div class="roundedCornerSpacer">&nbsp;</div>
+ </div><!-- .content -->
+ <div class="bottomCorners">
+ <img class="borderBL" src="../../images/borderBL.gif" alt="" width="14" height="14" />
+ <img class="borderBR" src="../../images/borderBR.gif" alt="" width="14" height="14" />
+ </div><!-- .bottomCorners -->
+</div><!-- .contentWrapper -->
+</div><!-- .centered -->
+
+<div class="centered">
+<address>Copyright &copy; 2002-4 <a href="http://diveintomark.org/">Mark Pilgrim</a> and <a href="http://www.intertwingly.net/blog/">Sam Ruby</a></address>
+</div>
+
+</body>
+</html>
View
70 docs/warning/DeprecatedRootHref.html
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<title>root:// URLs have been superceded by full http:// URLs</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="icon" href="http://www.feedvalidator.org/favicon.ico" />
+<link rel="shortcut icon" href="http://www.feedvalidator.org/favicon.ico" />
+<style type="text/css" media="screen">@import "../../css/common.css";
+@import "../../css/documentation.css";</style>
+<script type="text/javascript"><!-- --></script>
+<link rel="start" href="http://feedvalidator.org/docs/" title="Home" />
+</head>
+<body>
+<div id="logo">
+<h1><a href="../../"><span id="feed"><span id="f">F</span><span id="e1">E</span><span id="e2">E</span></span><span id="d">D</span> Validator</a></h1>
+<p>Documentation</p>
+<a class="skip" href="#startnavigation">Jump to navigation</a>
+</div> <!--logo-->
+
+<div id="main">
+<h2>Message</h2>
+<div class="docbody">
+<p>root:// URLs have been superceded by full http:// URLs</p>
+</div>
+<h2>Explanation</h2>
+
+<div class="docbody">
+<p>XXX</p>
+</div>
+<h2>Solution</h2>
+<div class="docbody">
+<p>XXX</p>
+</div>
+<h2>Not clear? Disagree?</h2>
+<div class="docbody">
+<p>You might be able to find help in one of <a href="../howto/resources.html">these fine resources</a>.</p>
+</div>
+
+</div><!--main-->
+<div class="centered">
+<a name="startnavigation" id="startnavigation"></a>
+<div class="navbarWrapper">
+ <div class="navbarContent">
+ <img class="borderTL" src="../../images/borderTL.gif" alt="" width="14" height="14" />
+ <img class="borderTR" src="../../images/borderTR.gif" alt="" width="14" height="14" />
+
+<p>
+<a href="../../">Home</a> &middot;
+<a href="../../about.html">About</a> &middot;
+<a href="../../news/">News</a> &middot;
+<a href="../../docs/">Docs</a> &middot;
+<a href="../../terms.html">Terms</a>
+</p>
+
+ <div class="roundedCornerSpacer">&nbsp;</div>
+ </div><!-- .content -->
+ <div class="bottomCorners">
+ <img class="borderBL" src="../../images/borderBL.gif" alt="" width="14" height="14" />
+ <img class="borderBR" src="../../images/borderBR.gif" alt="" width="14" height="14" />
+ </div><!-- .bottomCorners -->
+</div><!-- .contentWrapper -->
+</div><!-- .centered -->
+
+<div class="centered">
+<address>Copyright &copy; 2002-4 <a href="http://diveintomark.org/">Mark Pilgrim</a> and <a href="http://www.intertwingly.net/blog/">Sam Ruby</a></address>
+</div>
+
+</body>
+</html>
View
2  docs/warning/DuplicateEnclosure.html
@@ -26,7 +26,7 @@
<h2>Explanation</h2>
<div class="docbody">
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#element-channel-item-enclosure">Best Practices Profile</a>, support for the enclosure element in RSS software varies significantly because of disagreement over whether the specification permits more than one enclosure per item. Although the author intended to permit no more than one enclosure in each item, this limit is not explicit in the specification.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#element-channel-item-enclosure">Best Practices Profile</a>, support for the enclosure element in RSS software varies significantly because of disagreement over whether the specification permits more than one enclosure per item. Although the author intended to permit no more than one enclosure in each item, this limit is not explicit in the specification.</p>
<p>For best support in the widest number of aggregators, an item <span class="rfc2119">should not</span> contain more than one enclosure.</p>
<!--
<p>Here are a few links to prior discussions on the topic:</p>
View
2  docs/warning/EmailFormat.html
@@ -26,7 +26,7 @@
<h2>Explanation</h2>
<div class="docbody">
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#data-types-email">Best Practices Profile</a>, the <span class="rfc2119">recommended</span> format for e-mail addresses in RSS elements is <span class="template">username@hostname.tld (Real Name)</span>, as in the following example:</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#data-types-email">Best Practices Profile</a>, the <span class="rfc2119">recommended</span> format for e-mail addresses in RSS elements is <span class="template">username@hostname.tld (Real Name)</span>, as in the following example:</p>
<blockquote><pre>&lt;managingEditor&gt;luksa@dallas.example.com (Frank Luksa)&lt;/managingEditor&gt;</pre></blockquote>
</div>
View
2  docs/warning/ImageTitleDoesntMatch.html
@@ -26,7 +26,7 @@
<h2>Explanation</h2>
<div class="docbody">
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#element-channel-image-title">Best Practices Profile</a>, this element <span class="rfc2119">should</span> have the same text as the channel's <a href="#element-channel-title">title</a> element</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#element-channel-image-title">Best Practices Profile</a>, this element <span class="rfc2119">should</span> have the same text as the channel's <a href="#element-channel-title">title</a> element</p>
</div>
<h2>Solution</h2>
<div class="docbody">
View
2  docs/warning/ImplausibleDate.html
@@ -32,7 +32,7 @@
<a href="http://blogs.law.harvard.edu/tech/rss#ltpubdategtSubelementOfLtitemgt">anticipated</a>
that some aggregators may chose to ignore items with pubDates in the future,
this practice
-<a href="http://www.rssboard.org/rss-profile#element-channel-item-pubdate">never seemed to catch on</a>.</p>
+<a href="http://www.rssboard.org/rss-profile-1#element-channel-item-pubdate">never seemed to catch on</a>.</p>
<p>Instead, many clients sort by dates, either by default, or as an option. For this reason, it is important that date values are as accurate as possible.</p>
</div>
<h2>Solution</h2>
View
70 docs/warning/InvalidKmlMediaType.html
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<title>foo is an invalid KML media type. Use application/vnd.google-earth.kml+xml or application/vnd.google-earth.kmz</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="icon" href="http://www.feedvalidator.org/favicon.ico" />
+<link rel="shortcut icon" href="http://www.feedvalidator.org/favicon.ico" />
+<style type="text/css" media="screen">@import "../../css/common.css";
+@import "../../css/documentation.css";</style>
+<script type="text/javascript"><!-- --></script>
+<link rel="start" href="http://feedvalidator.org/docs/" title="Home" />
+</head>
+<body>
+<div id="logo">
+<h1><a href="../../"><span id="feed"><span id="f">F</span><span id="e1">E</span><span id="e2">E</span></span><span id="d">D</span> Validator</a></h1>
+<p>Documentation</p>
+<a class="skip" href="#startnavigation">Jump to navigation</a>
+</div> <!--logo-->
+
+<div id="main">
+<h2>Message</h2>
+<div class="docbody">
+<p><code>foo</code> is an invalid KML media type. Use application/vnd.google-earth.kml+xml or application/vnd.google-earth.kmz</p>
+</div>
+<h2>Explanation</h2>
+
+<div class="docbody">
+<p>XXX</p>
+</div>
+<h2>Solution</h2>
+<div class="docbody">
+<p>XXX</p>
+</div>
+<h2>Not clear? Disagree?</h2>
+<div class="docbody">
+<p>You might be able to find help in one of <a href="../howto/resources.html">these fine resources</a>.</p>
+</div>
+
+</div><!--main-->
+<div class="centered">
+<a name="startnavigation" id="startnavigation"></a>
+<div class="navbarWrapper">
+ <div class="navbarContent">
+ <img class="borderTL" src="../../images/borderTL.gif" alt="" width="14" height="14" />
+ <img class="borderTR" src="../../images/borderTR.gif" alt="" width="14" height="14" />
+
+<p>
+<a href="../../">Home</a> &middot;
+<a href="../../about.html">About</a> &middot;
+<a href="../../news/">News</a> &middot;
+<a href="../../docs/">Docs</a> &middot;
+<a href="../../terms.html">Terms</a>
+</p>
+
+ <div class="roundedCornerSpacer">&nbsp;</div>
+ </div><!-- .content -->
+ <div class="bottomCorners">
+ <img class="borderBL" src="../../images/borderBL.gif" alt="" width="14" height="14" />
+ <img class="borderBR" src="../../images/borderBR.gif" alt="" width="14" height="14" />
+ </div><!-- .bottomCorners -->
+</div><!-- .contentWrapper -->
+</div><!-- .centered -->
+
+<div class="centered">
+<address>Copyright &copy; 2002-4 <a href="http://diveintomark.org/">Mark Pilgrim</a> and <a href="http://www.intertwingly.net/blog/">Sam Ruby</a></address>
+</div>
+
+</body>
+</html>
View
2  docs/warning/MisplacedItem.html
@@ -26,7 +26,7 @@
<h2>Explanation</h2>
<div class="docbody">
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#element-channel">Best Practices Profile</a>, all item elements <span class="rfc2119">should</span> appear after all of the other elements in a channel.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#element-channel">Best Practices Profile</a>, all item elements <span class="rfc2119">should</span> appear after all of the other elements in a channel.</p>
</div>
<h2>Solution</h2>
<div class="docbody">
View
2  docs/warning/MissingAtomSelfLink.html
@@ -26,7 +26,7 @@
<h2>Explanation</h2>
<div class="docbody">
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#namespace-elements-atom-link">Best Practices Profile</a>, identifying a feed's URL within the feed makes it more portable, self-contained, and easier to cache. For these reasons, a feed <span class="rfc2119">should</span> contain an <span class="element">atom:link</span> used for this purpose.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#namespace-elements-atom-link">Best Practices Profile</a>, identifying a feed's URL within the feed makes it more portable, self-contained, and easier to cache. For these reasons, a feed <span class="rfc2119">should</span> contain an <span class="element">atom:link</span> used for this purpose.</p>
</div>
<h2>Solution</h2>
<div class="docbody">
View
2  docs/warning/MissingRealName.html
@@ -26,7 +26,7 @@
<h2>Explanation</h2>
<div class="docbody">
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#data-types-email">Best Practices Profile</a>, the <span class="rfc2119">recommended</span> format for e-mail addresses in RSS elements is <span class="template">username@hostname.tld (Real Name)</span>, as in the following example:</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#data-types-email">Best Practices Profile</a>, the <span class="rfc2119">recommended</span> format for e-mail addresses in RSS elements is <span class="template">username@hostname.tld (Real Name)</span>, as in the following example:</p>
<blockquote><pre>&lt;managingEditor&gt;luksa@dallas.example.com (Frank Luksa)&lt;/managingEditor&gt;</pre></blockquote>
</div>
View
2  docs/warning/NeedDescriptionBeforeContent.html
@@ -30,7 +30,7 @@
<p>Publishers who employ summaries <span class="rfc2119">should</span> store the summary in <span class="element">description</span> and the full content in <span class="element">content:encoded</span>, ordering <span class="element">description</span> first within the item. On items with no summary, the full content <span class="rfc2119">should</span> be stored in <span class="element">description</span>.</p>
-<p>See the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#namespace-elements-content-encoded">Best Practices Profile</a> for additional requirements and recommendations.</p>
+<p>See the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#namespace-elements-content-encoded">Best Practices Profile</a> for additional requirements and recommendations.</p>
</div>
<h2>Solution</h2>
View
2  docs/warning/SlashDate.html
@@ -26,7 +26,7 @@
<h2>Explanation</h2>
<div class="docbody">
-<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile#namespace-elements-slash-comments">Best Practices Profile</a>, because the Slash namespace lacks an element to indicate when the comment counts were compiled, publishers who use this element also should include a lastBuildDate element.</p>
+<p>According to the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#namespace-elements-slash-comments">Best Practices Profile</a>, because the Slash namespace lacks an element to indicate when the comment counts were compiled, publishers who use this element also should include a lastBuildDate element.</p>
</div>
<h2>Solution</h2>
<div class="docbody">
View
2  news/archives/2007/10/15/rss_best_practices.html
@@ -28,7 +28,7 @@
<p class="dateheader">Monday, October 15, 2005</a></p>
<div class="newsbody">
-<p>The <a href="http://www.rssboard.org/rss-profile">RSS Best Practices
+<p>The <a href="http://www.rssboard.org/rss-profile-1">RSS Best Practices
Profile</a> contains a set of recommendations for how to
create RSS 2.0 documents that work best in the wide and diverse audience
of client software that supports this format. The Feed
View
2  news/index.html
@@ -20,7 +20,7 @@
<h2>RSS Profile Support Added</h2>
<p class="dateheader"><a title="permanent link to &quot;RSS Profile support added&quot;" href="archives/2007/10/15/rss_best_practices.html">Monday, October 15, 2005</a></p>
<div class="newsbody">
-<p>The <a href="http://www.rssboard.org/rss-profile">RSS Best Practices
+<p>The <a href="http://www.rssboard.org/rss-profile-1">RSS Best Practices
Profile</a> contains a set of recommendations for how to
create RSS 2.0 documents that work best in the wide and diverse audience
of client software that supports this format. The Feed
Please sign in to comment.
Something went wrong with that request. Please try again.