Comments on: Publishing XML to the web with XSLT: a replacement for the presentation layer http://stevenbenner.com/2010/02/publishing-xml-to-the-web-with-xslt-a-replacement-for-the-presentation-layer/ Random articles about programming, computing and the internet. Thu, 09 Sep 2010 03:23:45 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Steven Benner http://stevenbenner.com/2010/02/publishing-xml-to-the-web-with-xslt-a-replacement-for-the-presentation-layer/#comment-1291 Steven Benner Wed, 19 May 2010 03:02:28 +0000 http://stevenbenner.com/?p=184#comment-1291 Oh I see, yeah I guess I didn't quite understand how you were abstracting the content. That's an interesting approach. Thanks for the information! Oh I see, yeah I guess I didn’t quite understand how you were abstracting the content. That’s an interesting approach. Thanks for the information!

]]> By: Alejandro http://stevenbenner.com/2010/02/publishing-xml-to-the-web-with-xslt-a-replacement-for-the-presentation-layer/#comment-1258 Alejandro Mon, 17 May 2010 15:07:04 +0000 http://stevenbenner.com/?p=184#comment-1258 I have been misunderstood. In your example the XSLT stylesheet has embedded XHTML semantic. What I propose is to separate transformation (XSLT) from layout page (XHTML). So, do not lose any level of abstraction. In fact, we are adding a level: the connection by using XSLT. XML (data, preferably in a standard vocabulary and not one designed ad-hot) - XHTML (layout for browsers) - XSLT (bindding) - and of course, CSS (design) - and EmacScript (behavior, if necessary) In this way, the whole design of the page for browsers can be done without taking into account the type of linkage with the data, taking full advantage of WYSIWYG editing with any software (not tying to only those that allow the addition of XSLT ), and allowing the separation of concerns in the development team. Regarding IE6, for any XML document to be provided, the browser will remain in standard mode. In fact, the problem is with IE7. If the document resulting from the transformation does not have a DOCTYPE declaration, IE7 interprets the CSS stylesheet like IE6 (losing the ability to use the hover pseudoclass on any element, for example) Check out my site and see how all these minor problems are solved. I have been misunderstood. In your example the XSLT stylesheet has embedded XHTML semantic. What I propose is to separate transformation (XSLT) from layout page (XHTML).
So, do not lose any level of abstraction. In fact, we are adding a level: the connection by using XSLT.
XML (data, preferably in a standard vocabulary and not one designed ad-hot) – XHTML (layout for browsers) – XSLT (bindding) – and of course, CSS (design) – and EmacScript (behavior, if necessary)
In this way, the whole design of the page for browsers can be done without taking into account the type of linkage with the data, taking full advantage of WYSIWYG editing with any software (not tying to only those that allow the addition of XSLT ), and allowing the separation of concerns in the development team.
Regarding IE6, for any XML document to be provided, the browser will remain in standard mode. In fact, the problem is with IE7. If the document resulting from the transformation does not have a DOCTYPE declaration, IE7 interprets the CSS stylesheet like IE6 (losing the ability to use the hover pseudoclass on any element, for example)
Check out my site and see how all these minor problems are solved.

]]> By: Steven Benner http://stevenbenner.com/2010/02/publishing-xml-to-the-web-with-xslt-a-replacement-for-the-presentation-layer/#comment-1244 Steven Benner Sun, 16 May 2010 20:05:11 +0000 http://stevenbenner.com/?p=184#comment-1244 If you're building an XHTML document anyway I don't see the benefit of using XSLT to modify that document. You're loosing the abstractions between data and layout and risking backwards compatibility issues with IE6. Only XHTML 1.1 specifically allows (and requires) XML declarations, but IE6 does not support XHTML 1.1 because of the XML declaration. The first line of any HTML document must be a DOCTYPE statement or IE6 reverts to quirks mode. All modern browsers support XHTML 1.1, but IE6 is still too common to ignore especially for a business. (Granted, this site doesn't work with IE6) The only place XSLT can be reliably used if you need to support old browsers is on an XML document. If you’re building an XHTML document anyway I don’t see the benefit of using XSLT to modify that document. You’re loosing the abstractions between data and layout and risking backwards compatibility issues with IE6. Only XHTML 1.1 specifically allows (and requires) XML declarations, but IE6 does not support XHTML 1.1 because of the XML declaration. The first line of any HTML document must be a DOCTYPE statement or IE6 reverts to quirks mode.

All modern browsers support XHTML 1.1, but IE6 is still too common to ignore especially for a business. (Granted, this site doesn’t work with IE6)

The only place XSLT can be reliably used if you need to support old browsers is on an XML document.

]]> By: Alejandro http://stevenbenner.com/2010/02/publishing-xml-to-the-web-with-xslt-a-replacement-for-the-presentation-layer/#comment-1204 Alejandro Fri, 14 May 2010 19:48:13 +0000 http://stevenbenner.com/?p=184#comment-1204 Despite the fact that many deny the use of XSLT on the client, is a technology common to the vast majority of modern browsers. It is much more compatible than EmacScript between different browsers. For all tasks involving static modification of a DOM based on an XML document, XSLT is faster and easier than EmacsScript. The difficulty lies in learning the declarative programming approach. On the other hand, I would not recommend the use of the semantics of XHTML within the XSLT style sheet. It is better to provide separate XHTML page and data (in an XML document with standard vocabulary) allowing the XSLT stylesheet to make the connection. In example www.aranedabienesraices.com.ar Despite the fact that many deny the use of XSLT on the client, is a technology common to the vast majority of modern browsers. It is much more compatible than EmacScript between different browsers.
For all tasks involving static modification of a DOM based on an XML document, XSLT is faster and easier than EmacsScript. The difficulty lies in learning the declarative programming approach.
On the other hand, I would not recommend the use of the semantics of XHTML within the XSLT style sheet. It is better to provide separate XHTML page and data (in an XML document with standard vocabulary) allowing the XSLT stylesheet to make the connection.
In example http://www.aranedabienesraices.com.ar

]]>