On Fri, Jun 17, 2005 at 10:10:55AM +0200, Jan Algermissen wrote: > Actually, I thought you meant that people would generally create such > libraries for each *MIME type* (or schema), Yes, that's what I meant, a library per media type, not one for each eBay or Google service. This would mean that for a very general media type like Atom, that most developers should be content to have a URI, HTTP, and Atom library in hand. Having more specific, possibly per-service libraries on top (even code-generated ones) may have some value in some cases, but as I mentioned before, I wouldn't want them to step on the toes of the URI/HTTP/Atom libs by defining things which were already handled in those libs... like operations, for instance. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Coactus; Web-inspired integration strategies http://www.coactus.comReceived on Friday, 17 June 2005 13:05:25 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:11 GMT