[Part 2] Assets, Atom Feeds, and AspectXML - The Triple Threat of Web Development?
I've just added the second part of the 'Assets, Atom Feeds, and AspectXML' series to my O'Reilly Weblog.
As the post starts:
In developing this post I realized there needs to be a separation of concepts; The first concept covers the idea of weaving together separate data, layout, and layout definition files into a final output. Once this concept is understood is then much easier to understand how implementing AOP-based concepts can take things to the next level, bringing incredible power with very little additional code with each new project.
In realizing the time I decided to post the first part of this, which is basically just the code base I will be working with to introduce the general concepts of data weaving using XML for both data and layout definition and XSLT to combine the various files together into various output types.
I plan to follow-up a bit later this evening with an explanation as to how the transformation file works to then extend into the concept of accessing an external Atom feed to be used as a way of creating a drop down menu that contains various links, images, and other related files bringing a much more powerful and robust linking system that turns a typical link within a page into an 'Asset' that can be managed through various tools and publication methods and used as part of our build process to ensure that each and every time we reference an asset the most up to date links, images, and related files are available to visitors to our sites.
Cheers :)