{ "attachments": [], "comments_archived": true, "date": "2003-10-01T20:21:23.000Z", "layout": "post", "title": "RSS-Data: XML-RPC encoding in RSS 2.0", "wordpress_id": 487, "wordpress_slug": "rss-data", "wordpress_url": "http://www.decafbad.com/blog/?p=487", "year": "2003", "month": "10", "day": "01", "isDir": false, "slug": "rss-data", "type": "entry", "postName": "2003-10-01-rss-data", "html": "

\nA few months ago I approached Dave Winer and a few other people with a very simple idea.? Why not use XML-RPC's data serialization format to create a simple data language for object meta-data in RSS (and other!) applications.? Interestingly, if you subtract the message envelop from XML-RPC, add Unicode and time-zone support to the standard, you've actually got WDDX, quite literally.? Dave really liked the idea, and we came up with the idea of RSS-Data.\n

\n

\nWhy use RSS-Data?? Pragmatism.? Because of the rapid growth of blogging software, XML-RPC parsers are already implemented in dozens of languages and platforms.? As a result, a simple data language based on XML-RPC's data model could emerge in a matter of days or weeks, as developers quickly refactor their parsers to simply provide data serialization/deserialization components.\n

\n\n
Source: Jeremy Allaire's Radio (via Silicon Valley - Dan Gillmor's eJournal - Expanding the Scope of RSS)\n\n
\n\n

Grr. I can’t decide whether I hate this idea or can live with it. On the one hand, I have benefitted from XML-RPC and it’s quick integration between disparate scripting environments. But on the other hand, the tendency to use adhoc data structures in scripting has given me numerous headaches and plenty of inexplicable bugs.

The further I get, the less I want quick and dirty, and the more I want thoughtful chaos and at least some documentation. I’d like some schemas, rather than reverse engineering from example. But sometimes it’s nice to short circuit over-designed processes and take expedient shortcuts, even if there lies the road to madness. Sleep is good sometimes.

\n\n\n\n\n\n

shortname=rss_data

\n", "body": "

\r\nA few months ago I approached Dave Winer and a few other people with a very simple idea.? Why not use XML-RPC's data serialization format to create a simple data language for object meta-data in RSS (and other!) applications.? Interestingly, if you subtract the message envelop from XML-RPC, add Unicode and time-zone support to the standard, you've actually got WDDX, quite literally.? Dave really liked the idea, and we came up with the idea of RSS-Data.\r\n

\r\n

\r\nWhy use RSS-Data?? Pragmatism.? Because of the rapid growth of blogging software, XML-RPC parsers are already implemented in dozens of languages and platforms.? As a result, a simple data language based on XML-RPC's data model could emerge in a matter of days or weeks, as developers quickly refactor their parsers to simply provide data serialization/deserialization components.\r\n

Source: Jeremy Allaire's Radio (via Silicon Valley - Dan Gillmor's eJournal - Expanding the Scope of RSS)
\t

Grr. I can’t decide whether I hate this idea or can live with it. On the one hand, I have benefitted from XML-RPC and it’s quick integration between disparate scripting environments. But on the other hand, the tendency to use adhoc data structures in scripting has given me numerous headaches and plenty of inexplicable bugs.

The further I get, the less I want quick and dirty, and the more I want thoughtful chaos and at least some documentation. I’d like some schemas, rather than reverse engineering from example. But sometimes it’s nice to short circuit over-designed processes and take expedient shortcuts, even if there lies the road to madness. Sleep is good sometimes.

\r\n\r\nshortname=rss_data\r\n", "parentPath": "./content/posts/archives/2003", "path": "2003/10/01/rss-data", "summary": "A few months ago I approached Dave Winer and a few other people with a very simple idea.? Why not use XML-RPC's data serialization format to create a simple data language for object meta-data in RSS (and other!) applications.? Interestingly, if you subtract the message envelop from XML-RPC, add Unicode and time-zone support to the standard, you've actually got WDDX, quite literally.? Dave really liked the idea, and we came up with the idea of RSS-Data.\n\n\nWhy use RSS-Data?? Pragmatism.? Because of the rapid growth of blogging software, XML-RPC parsers are already implemented in dozens of languages and platforms.? As a result, a simple data language based on XML-RPC's data model could emerge in a matter of days or weeks, as developers quickly refactor their parsers to simply provide data serialization/deserialization components.\n\n\nSource: Jeremy Allaire's Radio (via Silicon Valley - Dan Gillmor's eJournal - Expanding the Scope of RSS)\n\n\n\nGrr. I can’t decide whether I hate this idea or can live with it. On the one hand, I have benefitted from XML-RPC and it’s quick integration between disparate scripting environments. But on the other hand, the tendency to use adhoc data structures in scripting has given me numerous headaches and plenty of inexplicable bugs.The further I get, the less I want quick and dirty, and the more I want thoughtful chaos and at least some documentation. I’d like some schemas, rather than reverse engineering from example. But sometimes it’s nice to short circuit over-designed processes and take expedient shortcuts, even if there lies the road to madness. Sleep is good sometimes.", "needsBuild": true, "prevPostPath": "2003/10/01/comment-icons", "prevPostTitle": "Comment Icons drawn from author's RSS or FOAF files", "nextPostPath": "2003/10/02/rss-data-versus-namespace", "nextPostTitle": "An example of an RSS 2.0 namespace versus RSS-Data usage" }