Author: as
Date: Fri Feb 22 16:32:34 2008
New Revision: 7439

Log:
- Added some more iTunes module documentation.

Modified:
    trunk/Feed/docs/specifications.txt

Modified: trunk/Feed/docs/specifications.txt
==============================================================================
--- trunk/Feed/docs/specifications.txt [iso-8859-1] (original)
+++ trunk/Feed/docs/specifications.txt [iso-8859-1] Fri Feb 22 16:32:34 2008
@@ -2110,6 +2110,17 @@
 `iTunes specifications`_
 
 
+Recommendations
+---------------
+
+- All values should be plain text (no markup or HTML)
+- Values are limited to 255 characters, except for *summary* which can be up
+  to 4000 characters
+- Whitespace in values is significant, i.e. it will show in `iTunes`_, so
+  don't add leading or trailing whitespace to your values
+- CDATA sections are strongly discouraged
+
+
 Feed elements
 -------------
 
@@ -2122,6 +2133,9 @@
 
 Can appear only once.
 
+If missing, `iTunes`_ will use the *author* / *managingEditor* element from
+the feed (|ezcFeed-author|_).
+
 
 iTunes-block
 ````````````
@@ -2172,6 +2186,9 @@
 
 The URL to the image is specified in the attribute *href*.
 
+If missing, `iTunes`_ will use the *image* element from the feed
+(|ezcFeed-image|_).
+
 
 iTunes-keywords
 ```````````````
@@ -2231,6 +2248,8 @@
 
 Can appear only once.
 
+If missing, `iTunes`_ will use the *description* element from the feed
+(|ezcFeed-description|_).
 
 
 Item elements
@@ -2294,12 +2313,12 @@
 
 The URL to the image is specified in the attribute *href*.
 
-NOTE: The `iTunes specifications` say that image is supported at podcast-level
-only, but there are many podcasts using image at podcast entry (item) level
-also, and there are software applications supporting that too. Use image at
-item-level at your own risk, as some software applications might not support
-it. The Feed component supports parsing and generating feeds with image at
-both podcast-level and item-level.
+NOTE: The `iTunes specifications`_ say that image is supported at
+podcast-level only, but there are many podcasts using image at podcast entry
+(item) level also, and there are software applications supporting that too.
+Use *image* at item-level at your own risk, as some software applications
+might not support it. The Feed component supports parsing and generating
+feeds with image at both podcast-level and item-level.
 
 
 iTunes-item-keywords
@@ -2334,6 +2353,8 @@
 
 Can appear only once.
 
+If missing, `iTunes`_ will use the *description* element from the feed
+(|ezcFeed-item-description|_).
 
 
 Resources
@@ -2372,6 +2393,7 @@
 .. _DCMI Type Vocabulary: http://dublincore.org/documents/dcmi-type-vocabulary/
 .. _RSS language codes: http://www.rssboard.org/rss-language-codes
 .. _iTunes categories: 
http://www.apple.com/itunes/store/podcaststechspecs.html#categories
+.. _iTunes: http://www.apple.com/itunes/
 
 .. |ezcFeed-author| replace:: author
 .. |ezcFeed-category| replace:: category


-- 
svn-components mailing list
svn-components@lists.ez.no
http://lists.ez.no/mailman/listinfo/svn-components

Reply via email to