Updated for alpha 3 release.

README.txt

@@ -9,9 +9,16 @@ Current Version
 
 Release Notes
 -------------
+Fixed:
+ http://drupal.org/node/557282
+ http://drupal.org/node/307223
+ http://drupal.org/node/306066
+
 Added Atom renderer to views_xml. Added SIOC renderer to views_rdf. Added 
 hCalendar renderer to views_xhtml. Removed dependency of all plugins on 
-the 'unformatted' row plugin.
+the 'unformatted' row plugin. To upgrade from the previous version you should
+first disable the module, delete the previous version's files, place the new
+ver into the directry, then re-enable the mdule
 
 About
 -----
@@ -21,32 +28,34 @@ formats allow content in a Drupal site to be easily used as data sources for
 Semantic Web clients and web mash-ups. Views Datasource plugins output content 
 from node lists created in Drupal Views as:
   1)XML data documents using schemas like OPML and Atom;
-  2)RDF/XML and RDF/N3 data documents using a vocabulary like FOAF;
-  3)JSON data documents in a format like MIT Simile/Exhibit JSON;
-  4)XHTML data documents using a microformat like hCard
+  2)RDF/XML data documents using vocabularies like FOAF and SIOC;
+  3)JSON data documents in plain JSON or in a format like MIT Simile/Exhibit;
+  4)XHTML data documents using microformat like hCard and hCalendar
   
-The project consists of 4 Views style plugins (and related row plugins):
+The project consists of 4 Views style plugins:
   1)views_xml - Output as raw XML, OPML, and Atom;
-  2)views_json - Output as simple JSON or Simile/Exhibit JSON;
-  3)views_rdf - Output as FOAF or SIOC;
-  4)views_xhtml - Output as hCard or hCalendar.
+  2)views_json - Output as simple JSON and Simile/Exhibit JSON;
+  3)views_rdf - Output as FOAF and SIOC;
+  4)views_xhtml - Output as hCard and hCalendar.
   
 In Drupal 6.x, to use these plugins you should:
 1) Enable the module containing the format you want to render your views as. 
 2) In the Views UI set the view style (in Basic Settings) to one of:
-   i)  JSON data document (render as Simple JSON and Simile/Exhibit JSON)
+   i)  JSON data document (render as Simple JSON or Simile/Exhibit JSON)
    ii) XML data document (render as raw XML, OPML, and Atom)
    iii) RDF data document (render as FOAF or SIOC RDF)
    iv) XHTML data document (render as hCard or hCalendar XHTML)
 3) In view style options choose the options or vocabulary for your format (like 
    raw or the OPML or Atom vocabulary for XML rendering.)
 4) Add the fields to your view that contain the information you want to be 
-pulled into the format renderer. For example, for the Atom format you should add
-the fields (More docs on this to come)   
-4. That's it! The rendered view will be visible in the preview and at your 
-view's path. No Drupal markup is emitted, just the data for the particular 
-content type with the proper Content-Type HTTP header (like text/xml or
-application/rdf+xml)
+   pulled into the format renderer:
+   The Atom format requires the fields: node nid, title, posted date, 
+   and updated date.
+   The SIOC format requires the fields: node nid, type, title, body, posted date
+5) That's it! The rendered view will be visible in the preview and at your 
+   view's path. No Drupal markup is emitted, just the data for the particular 
+   content type with the proper Content-Type HTTP header (like text/xml or
+   application/rdf+xml)
 
 A JSON data document will render the nodes generated by a view as a 
 serialization of an array of Javascript objects with each object's properties 
@@ -70,16 +79,15 @@ properties defined in the view. For example to create an <email> element inside
 the <div class="hcard"> root element, just have one or more fields in the view
 containing the text 'email'.
 
-The FOAF and vCard renderers are most useful with view based on user profiles 
+The FOAF and \hCard renderers are most useful with view based on user profiles 
 where you can create profile fields corresponding to properties defined in the 
 FOAF (http://xmlns.com/foaf/spec/) or hCard 
 (http://microformats.org/wiki/hcard-cheatsheet) spec. However any node type 
 (like those created with nodeprofile or Bio or Advanced Profile or Content
 Profile) can be used in the view. It doesn't matter what data table the view
-is base on, only what fields are exposed. See http://soc2008.hotdrupal.com for
-ways to use the plugins, and http://groups.drupal.org/node/11387 for more
-docs.
+is base on, only what fields are exposed.
    
-nid
-title, node_title -> title
-updated, updated_date, node_changed ->   
\ No newline at end of file
+TODO
+----
+Proper theming
+Use field labels instead of internal field  names