Comments on: Successful parsing ! http://blog.stadil.com/successful-parsing/ Strategies for Accelerating Technology Change by Sebastian Stadil Mon, 21 Feb 2011 19:28:19 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Administrator http://blog.stadil.com/successful-parsing/comment-page-1/#comment-1164 Administrator Mon, 19 Sep 2005 09:52:11 +0000 http://swophit.com/blog/?p=70#comment-1164 Parsing allows for flexible arrangement of data, depending on circumstances (DVD, CD, Game). XSLT allows for one arrangement of data. For many different kinds of arrangements, one would need many stylesheets, or the ability to generate XSLT stylesheets on-the-fly, which I'm not quite sure is doable. This way, once parsed, the server only takes relevant information, like price, ASIN, Title or whatever. Parsing allows for flexible arrangement of data, depending on circumstances (DVD, CD, Game). XSLT allows for one arrangement of data. For many different kinds of arrangements, one would need many stylesheets, or the ability to generate XSLT stylesheets on-the-fly, which I’m not quite sure is doable.

This way, once parsed, the server only takes relevant information, like price, ASIN, Title or whatever.

]]> By: Bjorn http://blog.stadil.com/successful-parsing/comment-page-1/#comment-1163 Bjorn Sun, 18 Sep 2005 22:51:36 +0000 http://swophit.com/blog/?p=70#comment-1163 I don't understand why you switched from XSLT to server side parsing on our end. Are you planning to stick the "inventory" info in our DB rather than getting it on the fly based on ASINs? I don’t understand why you switched from XSLT to server side parsing on our end.
Are you planning to stick the “inventory” info in our DB rather than getting it on the fly based on ASINs?

]]>