{
"attachments": [],
"comments_archived": true,
"date": "2003-10-02T15:52:00.000Z",
"layout": "post",
"title": "An example of an RSS 2.0 namespace versus RSS-Data usage",
"wordpress_id": 488,
"wordpress_slug": "rss-data-versus-namespace",
"wordpress_url": "http://www.decafbad.com/blog/?p=488",
"year": "2003",
"month": "10",
"day": "02",
"isDir": false,
"slug": "rss-data-versus-namespace",
"type": "entry",
"postName": "2003-10-02-rss-data-versus-namespace",
"html": "\nOkay, just for the sake of tinkering, I'm poking at embedding data\nfrom the\nAmazon Web Services\ninto an RSS 2.0 feed. On one hand, I just shoehorned the Amazon\nXML schema into an RSS 2.0 namespace, and on the other, I tried\ntransliterating the Amazon XML data into\nRSS-Data /\nXML-RPC serialized data\nstructures.\n
\n\nTo resolve my own love/hate of this RSS-Data idea,\nI'm planning to keep going from here and work up some simple Python\nscripts to produce and consume data along the lines of both examples,\nthen to comment on the experience. (This is assuming I don't run out\nof round tuits.) Some things to note:\n
\n\n- Your XML mojo is probably stronger than mine,\nso please feel free to correct me.
\n\n- Although I created the RSS-Data example by hand, it would\notherwise be completely produced and consumed by machine.
\n\n- Since it's at the root of a few things I'm thinking,\nit's worth restating: RSS-Data is intended to be produced and\nconsumed by machine, not by humans. This means that the XML\ndata needs not look pretty or elegant to you, but to your machine.
\n\n
\n\n\n\n\n\nSo, on with the XML. First, I\nrequested data\nfrom Amazon and got the following:\n
\n\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<ProductInfo\n xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n xsi:noNamespaceSchemaLocation=\"http://xml.amazon.com/schemas3/dev-lite.xsd\">\n <Details url=\"http://www.amazon.com/exec/obidos/ASIN/0439139597/0xdecafbad-20\">\n <Asin>0439139597</Asin>\n <ProductName>Harry Potter and the Goblet of Fire (Book 4)</ProductName>\n <Catalog>Book</Catalog>\n <Authors>\n <Author>J. K. Rowling</Author>\n <Author>Mary GrandPr?</Author>\n </Authors>\n <ReleaseDate>08 July, 2000</ReleaseDate>\n <Manufacturer>Scholastic</Manufacturer>\n <ImageUrlSmall>http://images.amazon.com/images/P/0439139597.01.THUMBZZZ.jpg</ImageUrlSmall>\n <ImageUrlMedium>http://images.amazon.com/images/P/0439139597.01.MZZZZZZZ.jpg</ImageUrlMedium>\n <ImageUrlLarge>http://images.amazon.com/images/P/0439139597.01.LZZZZZZZ.jpg</ImageUrlLarge>\n <Availability>Usually ships within 24 hours</Availability>\n <ListPrice>$25.95</ListPrice>\n <OurPrice>$18.16</OurPrice>\n <UsedPrice>$3.97</UsedPrice>\n </Details>\n</ProductInfo>
\n\n\nFrom this, I cooked up an example RSS feed with Amazon's XML\nschema shoehorned in as a namespace:\n
\n<rss version=\"2.0\"\n xmlns=\"http://blogs.law.harvard.edu/tech/rss\"\n xmlns:az=\"http://www.amazon.com/gp/aws/landing.html\"\n xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n xsi:schemaLocation=\"http://www.amazon.com/gp/aws/landing.html\n http://xml.amazon.com/schemas3/dev-lite.xsd\">\n <channel>\n <title>Testing Amazon Namespace</title> \n <item>\n <title>Harry Potter and the Goblet of Fire (Book 4)</title>\n <az:ProductInfo>\n <az:Details url=\"http://www.amazon.com/exec/obidos/ASIN/0439139597/0xdecafbad-20\">\n <az:Asin>0439139597</az:Asin>\n <az:ProductName>Harry Potter and the Goblet of Fire (Book 4)</az:ProductName>\n <az:Catalog>Book</az:Catalog>\n <az:Authors>\n <az:Author>J. K. Rowling</az:Author>\n <az:Author>Mary GrandPr?</az:Author>\n </az:Authors>\n <az:ReleaseDate>08 July, 2000</az:ReleaseDate>\n <az:Manufacturer>Scholastic</az:Manufacturer>\n <az:ImageUrlSmall>http://images.amazon.com/images/P/0439139597.01.THUMBZZZ.jpg</az:ImageUrlSmall>\n <az:ImageUrlMedium>http://images.amazon.com/images/P/0439139597.01.MZZZZZZZ.jpg</az:ImageUrlMedium>\n <az:ImageUrlLarge>http://images.amazon.com/images/P/0439139597.01.LZZZZZZZ.jpg</az:ImageUrlLarge>\n <az:Availability>Usually ships within 24 hours</az:Availability>\n <az:ListPrice>$25.95</az:ListPrice>\n <az:OurPrice>$18.16</az:OurPrice>\n <az:UsedPrice>$3.97</az:UsedPrice>\n </az:Details>\n </az:ProductInfo>\n </item> \n </channel> \n</rss>
\n\n\nThen, I transliterated things into what I understand of RSS-Data:\n
\n<rss version=\"2.0\"\n xmlns=\"http://blogs.law.harvard.edu/tech/rss\"\n xmlns:sdl=\"http://radio.weblogs.com/0113297/2003/10/01.html#a237\">\n <channel>\n <title>Testing Amazon Namespace</title> \n <item> \n <title>A Sample Item</title>\n <sdl:data>\n <sdl:struct>\n <sdl:member>\n <sdl:name>url</sdl:name>\n <sdl:value>\n <sdl:string>http://www.amazon.com/exec/obidos/ASIN/0439139597/0xdecafbad-20</sdl:string>\n </sdl:value>\n </sdl:member>\n <sdl:member>\n <sdl:name>Asin</sdl:name>\n <sdl:value><sdl:string>0439139597</sdl:string></sdl:value>\n </sdl:member>\n <sdl:member>\n <sdl:name>ProductName</sdl:name>\n <sdl:value>\n <sdl:string>\n Harry Potter and the Goblet of Fire (Book 4)\n </sdl:string>\n </sdl:value>\n </sdl:member>\n <sdl:member>\n <sdl:name>Catalog</sdl:name>\n <sdl:value><sdl:string>Book</sdl:string></sdl:value>\n </sdl:member> \n <sdl:member>\n <sdl:name>Authors</sdl:name>\n <sdl:value>\n <sdl:array>\n <sdl:data>\n <sdl:value>J. K. Rowling</sdl:value>\n <sdl:value>Mary GrandPr</sdl:value>\n </sdl:data>\n </sdl:array>\n </sdl:value> \n </sdl:member>\n <sdl:member>\n <sdl:name>ReleaseDate</sdl:name>\n <sdl:value>\n <sdl:dateTime.iso8601>2000-07-08T00:00:00</sdl:dateTime.iso8601>\n </sdl:value>\n </sdl:member> \n <sdl:member>\n <sdl:name>Manufacturer</sdl:name>\n <sdl:value><sdl:string>Scholastic</sdl:string></sdl:value>\n </sdl:member>\n <sdl:member>\n <sdl:name>ImageUrlSmall</sdl:name>\n <sdl:value>\n <sdl:string>http://images.amazon.com/images/P/0439139597.01.THUMBZZZ.jpg</sdl:string>\n </sdl:value>\n </sdl:member> \n <sdl:member>\n <sdl:name>ImageUrlMedium</sdl:name>\n <sdl:value>\n <sdl:string>http://images.amazon.com/images/P/0439139597.01.MZZZZZZZ.jpg</sdl:string>\n </sdl:value>\n </sdl:member> \n <sdl:member>\n <sdl:name>ImageUrlLarge</sdl:name>\n <sdl:value>\n <sdl:string>http://images.amazon.com/images/P/0439139597.01.LZZZZZZZ.jpg</sdl:string>\n </sdl:value>\n </sdl:member> \n <sdl:member>\n <sdl:name>Availability</sdl:name>\n <sdl:value><sdl:string>Usually ships within 24 hours</sdl:string></sdl:value>\n </sdl:member>\n <sdl:member>\n <sdl:name>ListPrice</sdl:name>\n <sdl:value><sdl:string>$25.95</sdl:string></sdl:value>\n </sdl:member>\n <sdl:member>\n <sdl:name>OurPrice</sdl:name>\n <sdl:value><sdl:string>$18.16</sdl:string></sdl:value>\n </sdl:member>\n <sdl:member>\n <sdl:name>UsedPrice</sdl:name>\n <sdl:value><sdl:string>$3.97</sdl:string></sdl:value>\n </sdl:member>\n </sdl:struct>\n </sdl:data>\n </item> \n </channel> \n</rss>
\n\n\n\n\n\nshortname=rss_data_versus_namespace
\n\n\n\n",
"body": "\r\nOkay, just for the sake of tinkering, I'm poking at embedding data\r\nfrom the\r\nAmazon Web Services\r\ninto an RSS 2.0 feed. On one hand, I just shoehorned the Amazon\r\nXML schema into an RSS 2.0 namespace, and on the other, I tried\r\ntransliterating the Amazon XML data into\r\nRSS-Data /\r\nXML-RPC serialized data\r\nstructures.\r\n
\r\n\r\nTo resolve my own love/hate of this RSS-Data idea,\r\nI'm planning to keep going from here and work up some simple Python\r\nscripts to produce and consume data along the lines of both examples,\r\nthen to comment on the experience. (This is assuming I don't run out\r\nof round tuits.) Some things to note:\r\n
\r\n\r\n- Your XML mojo is probably stronger than mine,\r\nso please feel free to correct me.
\r\n\r\n- Although I created the RSS-Data example by hand, it would\r\notherwise be completely produced and consumed by machine.
\r\n\r\n- Since it's at the root of a few things I'm thinking,\r\nit's worth restating: RSS-Data is intended to be produced and\r\nconsumed by machine, not by humans. This means that the XML\r\ndata needs not look pretty or elegant to you, but to your machine.
\r\n\r\n
\r\n\r\n\r\n\r\nSo, on with the XML. First, I\r\nrequested data\r\nfrom Amazon and got the following:\r\n
\r\n\r\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n<ProductInfo\r\n xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\r\n xsi:noNamespaceSchemaLocation=\"http://xml.amazon.com/schemas3/dev-lite.xsd\">\r\n <Details url=\"http://www.amazon.com/exec/obidos/ASIN/0439139597/0xdecafbad-20\">\r\n <Asin>0439139597</Asin>\r\n <ProductName>Harry Potter and the Goblet of Fire (Book 4)</ProductName>\r\n <Catalog>Book</Catalog>\r\n <Authors>\r\n <Author>J. K. Rowling</Author>\r\n <Author>Mary GrandPr?</Author>\r\n </Authors>\r\n <ReleaseDate>08 July, 2000</ReleaseDate>\r\n <Manufacturer>Scholastic</Manufacturer>\r\n <ImageUrlSmall>http://images.amazon.com/images/P/0439139597.01.THUMBZZZ.jpg</ImageUrlSmall>\r\n <ImageUrlMedium>http://images.amazon.com/images/P/0439139597.01.MZZZZZZZ.jpg</ImageUrlMedium>\r\n <ImageUrlLarge>http://images.amazon.com/images/P/0439139597.01.LZZZZZZZ.jpg</ImageUrlLarge>\r\n <Availability>Usually ships within 24 hours</Availability>\r\n <ListPrice>$25.95</ListPrice>\r\n <OurPrice>$18.16</OurPrice>\r\n <UsedPrice>$3.97</UsedPrice>\r\n </Details>\r\n</ProductInfo>
\r\n\r\n\r\nFrom this, I cooked up an example RSS feed with Amazon's XML\r\nschema shoehorned in as a namespace:\r\n
\r\n<rss version=\"2.0\"\r\n xmlns=\"http://blogs.law.harvard.edu/tech/rss\"\r\n xmlns:az=\"http://www.amazon.com/gp/aws/landing.html\"\r\n xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\r\n xsi:schemaLocation=\"http://www.amazon.com/gp/aws/landing.html\r\n http://xml.amazon.com/schemas3/dev-lite.xsd\">\r\n <channel>\r\n <title>Testing Amazon Namespace</title> \r\n <item>\r\n <title>Harry Potter and the Goblet of Fire (Book 4)</title>\r\n <az:ProductInfo>\r\n <az:Details url=\"http://www.amazon.com/exec/obidos/ASIN/0439139597/0xdecafbad-20\">\r\n <az:Asin>0439139597</az:Asin>\r\n <az:ProductName>Harry Potter and the Goblet of Fire (Book 4)</az:ProductName>\r\n <az:Catalog>Book</az:Catalog>\r\n <az:Authors>\r\n <az:Author>J. K. Rowling</az:Author>\r\n <az:Author>Mary GrandPr?</az:Author>\r\n </az:Authors>\r\n <az:ReleaseDate>08 July, 2000</az:ReleaseDate>\r\n <az:Manufacturer>Scholastic</az:Manufacturer>\r\n <az:ImageUrlSmall>http://images.amazon.com/images/P/0439139597.01.THUMBZZZ.jpg</az:ImageUrlSmall>\r\n <az:ImageUrlMedium>http://images.amazon.com/images/P/0439139597.01.MZZZZZZZ.jpg</az:ImageUrlMedium>\r\n <az:ImageUrlLarge>http://images.amazon.com/images/P/0439139597.01.LZZZZZZZ.jpg</az:ImageUrlLarge>\r\n <az:Availability>Usually ships within 24 hours</az:Availability>\r\n <az:ListPrice>$25.95</az:ListPrice>\r\n <az:OurPrice>$18.16</az:OurPrice>\r\n <az:UsedPrice>$3.97</az:UsedPrice>\r\n </az:Details>\r\n </az:ProductInfo>\r\n </item> \r\n </channel> \r\n</rss>
\r\n\r\n\r\nThen, I transliterated things into what I understand of RSS-Data:\r\n
\r\n<rss version=\"2.0\"\r\n xmlns=\"http://blogs.law.harvard.edu/tech/rss\"\r\n xmlns:sdl=\"http://radio.weblogs.com/0113297/2003/10/01.html#a237\">\r\n <channel>\r\n <title>Testing Amazon Namespace</title> \r\n <item> \r\n <title>A Sample Item</title>\r\n <sdl:data>\r\n <sdl:struct>\r\n <sdl:member>\r\n <sdl:name>url</sdl:name>\r\n <sdl:value>\r\n <sdl:string>http://www.amazon.com/exec/obidos/ASIN/0439139597/0xdecafbad-20</sdl:string>\r\n </sdl:value>\r\n </sdl:member>\r\n <sdl:member>\r\n <sdl:name>Asin</sdl:name>\r\n <sdl:value><sdl:string>0439139597</sdl:string></sdl:value>\r\n </sdl:member>\r\n <sdl:member>\r\n <sdl:name>ProductName</sdl:name>\r\n <sdl:value>\r\n <sdl:string>\r\n Harry Potter and the Goblet of Fire (Book 4)\r\n </sdl:string>\r\n </sdl:value>\r\n </sdl:member>\r\n <sdl:member>\r\n <sdl:name>Catalog</sdl:name>\r\n <sdl:value><sdl:string>Book</sdl:string></sdl:value>\r\n </sdl:member> \r\n <sdl:member>\r\n <sdl:name>Authors</sdl:name>\r\n <sdl:value>\r\n <sdl:array>\r\n <sdl:data>\r\n <sdl:value>J. K. Rowling</sdl:value>\r\n <sdl:value>Mary GrandPr</sdl:value>\r\n </sdl:data>\r\n </sdl:array>\r\n </sdl:value> \r\n </sdl:member>\r\n <sdl:member>\r\n <sdl:name>ReleaseDate</sdl:name>\r\n <sdl:value>\r\n <sdl:dateTime.iso8601>2000-07-08T00:00:00</sdl:dateTime.iso8601>\r\n </sdl:value>\r\n </sdl:member> \r\n <sdl:member>\r\n <sdl:name>Manufacturer</sdl:name>\r\n <sdl:value><sdl:string>Scholastic</sdl:string></sdl:value>\r\n </sdl:member>\r\n <sdl:member>\r\n <sdl:name>ImageUrlSmall</sdl:name>\r\n <sdl:value>\r\n <sdl:string>http://images.amazon.com/images/P/0439139597.01.THUMBZZZ.jpg</sdl:string>\r\n </sdl:value>\r\n </sdl:member> \r\n <sdl:member>\r\n <sdl:name>ImageUrlMedium</sdl:name>\r\n <sdl:value>\r\n <sdl:string>http://images.amazon.com/images/P/0439139597.01.MZZZZZZZ.jpg</sdl:string>\r\n </sdl:value>\r\n </sdl:member> \r\n <sdl:member>\r\n <sdl:name>ImageUrlLarge</sdl:name>\r\n <sdl:value>\r\n <sdl:string>http://images.amazon.com/images/P/0439139597.01.LZZZZZZZ.jpg</sdl:string>\r\n </sdl:value>\r\n </sdl:member> \r\n <sdl:member>\r\n <sdl:name>Availability</sdl:name>\r\n <sdl:value><sdl:string>Usually ships within 24 hours</sdl:string></sdl:value>\r\n </sdl:member>\r\n <sdl:member>\r\n <sdl:name>ListPrice</sdl:name>\r\n <sdl:value><sdl:string>$25.95</sdl:string></sdl:value>\r\n </sdl:member>\r\n <sdl:member>\r\n <sdl:name>OurPrice</sdl:name>\r\n <sdl:value><sdl:string>$18.16</sdl:string></sdl:value>\r\n </sdl:member>\r\n <sdl:member>\r\n <sdl:name>UsedPrice</sdl:name>\r\n <sdl:value><sdl:string>$3.97</sdl:string></sdl:value>\r\n </sdl:member>\r\n </sdl:struct>\r\n </sdl:data>\r\n </item> \r\n </channel> \r\n</rss>
\r\n\r\nshortname=rss_data_versus_namespace\r\n\r\n\r\n ",
"parentPath": "./content/posts/archives/2003",
"path": "2003/10/02/rss-data-versus-namespace",
"summary": "Okay, just for the sake of tinkering, I'm poking at embedding data\nfrom the\nAmazon Web Services\ninto an RSS 2.0 feed. On one hand, I just shoehorned the Amazon\nXML schema into an RSS 2.0 namespace, and on the other, I tried\ntransliterating the Amazon XML data into\nRSS-Data /\nXML-RPC serialized data\nstructures.\n\n\nTo resolve my own love/hate of this RSS-Data idea,\nI'm planning to keep going from here and work up some simple Python\nscripts to produce and consume data along the lines of both examples,\nthen to comment on the experience. (This is assuming I don't run out\nof round tuits.) Some things to note:\n\n\nYour XML mojo is probably stronger than mine,\nso please feel free to correct me.\n\nAlthough I created the RSS-Data example by hand, it would\notherwise be completely produced and consumed by machine.\n\nSince it's at the root of a few things I'm thinking,\nit's worth restating: RSS-Data is intended to be produced and\nconsumed by machine, not by humans. This means that the XML\ndata needs not look pretty or elegant to you, but to your machine.\n\n\n\n\n\n\n\nSo, on with the XML. First, I\nrequested data\nfrom Amazon and got the following:\n\n\n\n\n \n 0439139597\n Harry Potter and the Goblet of Fire (Book 4)\n Book\n \n J. K. Rowling\n Mary GrandPr?\n \n 08 July, 2000\n Scholastic\n http://images.amazon.com/images/P/0439139597.01.THUMBZZZ.jpg\n http://images.amazon.com/images/P/0439139597.01.MZZZZZZZ.jpg\n http://images.amazon.com/images/P/0439139597.01.LZZZZZZZ.jpg\n Usually ships within 24 hours\n $25.95\n $18.16\n $3.97\n \n\n\n\nFrom this, I cooked up an example RSS feed with Amazon's XML\nschema shoehorned in as a namespace:\n\n\n \n Testing Amazon Namespace \n - \n Harry Potter and the Goblet of Fire (Book 4)\n \n \n 0439139597\n Harry Potter and the Goblet of Fire (Book 4)\n Book\n \n J. K. Rowling\n Mary GrandPr?\n \n 08 July, 2000\n Scholastic\n http://images.amazon.com/images/P/0439139597.01.THUMBZZZ.jpg\n http://images.amazon.com/images/P/0439139597.01.MZZZZZZZ.jpg\n http://images.amazon.com/images/P/0439139597.01.LZZZZZZZ.jpg\n Usually ships within 24 hours\n $25.95\n $18.16\n $3.97\n \n \n
\n \n\n\n\nThen, I transliterated things into what I understand of RSS-Data:\n\n\n \n Testing Amazon Namespace \n - \n A Sample Item\n \n \n \n url\n \n http://www.amazon.com/exec/obidos/ASIN/0439139597/0xdecafbad-20\n \n \n \n Asin\n 0439139597\n \n \n ProductName\n \n \n Harry Potter and the Goblet of Fire (Book 4)\n \n \n \n \n Catalog\n Book\n \n \n Authors\n \n \n \n J. K. Rowling\n Mary GrandPr\n \n \n \n \n \n ReleaseDate\n \n 2000-07-08T00:00:00\n \n \n \n Manufacturer\n Scholastic\n \n \n ImageUrlSmall\n \n http://images.amazon.com/images/P/0439139597.01.THUMBZZZ.jpg\n \n \n \n ImageUrlMedium\n \n http://images.amazon.com/images/P/0439139597.01.MZZZZZZZ.jpg\n \n \n \n ImageUrlLarge\n \n http://images.amazon.com/images/P/0439139597.01.LZZZZZZZ.jpg\n \n \n \n Availability\n Usually ships within 24 hours\n \n \n ListPrice\n $25.95\n \n \n OurPrice\n $18.16\n \n \n UsedPrice\n $3.97\n \n \n \n
\n \n",
"needsBuild": true,
"prevPostPath": "2003/10/01/rss-data",
"prevPostTitle": "RSS-Data: XML-RPC encoding in RSS 2.0",
"nextPostPath": "2003/10/02/rss-data-versus-namespace-2",
"nextPostTitle": "RSS 2.0 namespace versus RSS-Data, Part 2: First impressions"
} ![](\"http://www.gravatar.com/avatar.php?gravatar_id=2d3d8732d4a17d4ad7513b127ce055e7&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Zoe\r\n Hehe... :) Good work. \r\n\r\nThis demonstration should put this RSS-Data nonsense to rest.\r\n\r\nNothing like a good example...\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=9c8bd9e7e240a5917219fba15f0a10f4&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Jay Fienberg\r\n Thanks for building a good example comparison--very useful and helpful to the discussion\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=79d809dc2d0441ef44efc6ad1a1429eb&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Phillip Pearson\r\n Here's code to parse the RSS-Data version:\r\n\r\nhttp://www.myelin.co.nz/post/2003/10/3/#200310031\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=30d76b8340ace48320c3cc24927543aa&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n David Galbraith\r\n Heh - nothing like actually seeing something. And surely if you use a schema version of RSS you would get the extra information about the metadata without having to put it inline with the feed itself?\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=ac0d01ebb5e438c029c0764064f70827&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Danny\r\n I've done a first-shot at this in RDF/XML :\r\n\r\nhttp://dannyayers.com/archives/001908.html\r\n\r\nCompare and contrast with the RSS-Data version (especially in terms of readibility, simplicity etc ;-)\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=8f8684b971819df3daca507573d78894&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Michael Thorne\r\n Just started looking into the RSS-Data format and lightly read over your samples. What I noticed first off was there was no currency definition. I believe this would be a critical component of international business. mxt\r\n \r\n \r\n \r\n
Archived Comments
\n\n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=2d3d8732d4a17d4ad7513b127ce055e7&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nZoe\n \n\n\n \n\n\nHehe... :) Good work. \nThis demonstration should put this RSS-Data nonsense to rest.\nNothing like a good example... \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=9c8bd9e7e240a5917219fba15f0a10f4&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nJay Fienberg\n \n\n\n \n\n\nThanks for building a good example comparison--very useful and helpful to the discussion \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=79d809dc2d0441ef44efc6ad1a1429eb&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nPhillip Pearson\n \n\n\n \n\n\nHere's code to parse the RSS-Data version:\nhttp://www.myelin.co.nz/post/2003/10/3/#200310031 \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=30d76b8340ace48320c3cc24927543aa&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nDavid Galbraith\n \n\n\n \n\n\nHeh - nothing like actually seeing something. And surely if you use a schema version of RSS you would get the extra information about the metadata without having to put it inline with the feed itself? \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=79d809dc2d0441ef44efc6ad1a1429eb&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nPhillip Pearson\n \n\n\n \n\n\nAnd here's code to parse the namespace version:\nhttp://www.myelin.co.nz/post/2003/10/3/#200310032 \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=ac0d01ebb5e438c029c0764064f70827&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nDanny\n \n\n\n \n\n\nI've done a first-shot at this in RDF/XML :\nhttp://dannyayers.com/archives/001908.html\nCompare and contrast with the RSS-Data version (especially in terms of readibility, simplicity etc ;-) \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=8f8684b971819df3daca507573d78894&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nMichael Thorne\n \n\n\n \n\n\nJust started looking into the RSS-Data format and lightly read over your samples. What I noticed first off was there was no currency definition. I believe this would be a critical component of international business. mxt \n\n\n \n
\n\n\n\n
\n
\n
\n
\n
\n
\n