http://www.librarywebchic.net/wordpress/2009/12/16/modularizing-our-code-and-making-it-reusable/ Resources for librarians who are interested in the application of web design and technologies in libraries Sun, 18 Jul 2010 12:06:06 +0000 hourly 1 http://wordpress.org/?v=3.0 http://www.librarywebchic.net/wordpress/2009/12/16/modularizing-our-code-and-making-it-reusable/comment-page-1/#comment-65961 Brad Czerniak Fri, 18 Dec 2009 00:02:27 +0000 http://www.librarywebchic.net/wordpress/?p=1425#comment-65961 I think a common specification is the goal of <a href="http://www.jangle.org/" rel="nofollow">Jangle</a>. To me, though, it is symptomatic of any project that tries to be a catch-all: it introduces too much overhead to be truly useful. I'd rather just have a multi-format API (whether by screenscraping or other means) that lets me get catalog information in JSON, RSS, and the various OpenSearch formats. The exact format of the output data isn't all that important -- I just want it yesterday. I think a common specification is the goal of Jangle. To me, though, it is symptomatic of any project that tries to be a catch-all: it introduces too much overhead to be truly useful. I’d rather just have a multi-format API (whether by screenscraping or other means) that lets me get catalog information in JSON, RSS, and the various OpenSearch formats. The exact format of the output data isn’t all that important — I just want it yesterday.

]]>