Altova Mailing List Archives
>xml-dev Archive Home
>Recent entries
>Thread Prev - Re: [xml-dev] CSS does not use the XML syntax. Why not?
[Thread Next]
RE: [xml-dev] CSS does not use the XML syntax. Why not?
To: "'Thomas Lord'" <lord@---.--->,"'Micah Dubinko'" <Micah.Dubinko@---------.--->
Date: 6/23/2008 6:29:00 PM
I've been working with the XML/XPath/XSLT/CSS combination for applying styling since 2007, starting with my first ideas about it in this post: http://lists.w3.org/Archives/Public/www-style/2002Dec/0074.html I would recommend it; It's simple to create, simple to edit, simple to maintain, simple to read, and simple to share. You'll have to make a mix of applying it inline and through regular CSS selectors. Inline isn't pretty for SEO, so some 'intelligence' would be nice (though I hadn't the time and motivation to build this). I'll consider sharing my framework, but there's no really need to cause you can create it in just a few hours depending on what language you use. PHP is very simple using the default DOM-modules+XSL(T). Good luck! -----Original Message----- From: Thomas Lord [mailto:lord@e...] Sent: maandag 23 juni 2008 21:05 To: Micah Dubinko Cc: Costello, Roger L.; xml-dev@l... Subject: Re: [xml-dev] CSS does not use the XML syntax. Why not? Micah Dubinko wrote: > You could put a slight twist on the question and ask > > "Why don't any of the versions of CSS selectors use any of the versions of > XPath?" > History, again. CSS precedes XPath by two years. > (Not advocating any position, just interested in the discussion) > Does it need advocacy? A subset of XPath is surely isomorophic to selectors. The parsimony of sharing syntaxes, semantics, and implementations would likely work well. How could anyone seriously object, were it practical to make that change? (The impracticality is serious, though: we'll have browsers standardized on the current syntax for quite a while to come I'm sure. Changes that cause more browsers to implement CSS *correctly* are surely a higher priority :-) Were one to attempt an XML syntax for stylesheets (and XSLT transform to ordinary CSS syntax) it would be interesting to see if the XML version could use XPath. (Having XPath <-> XML transforms as primitive operations or a standard library in XSLT and XQuery would be handy for this and many purposes.) An XML/XPath solution could (this is quite speculative) be a very interesting tool. For example, given an XML database, libraries of styles could be associated with various parts of some of the schema present in the database. Then, pages could be synthesized on the fly -- along with customized style sheets for those pages. One can imagine systems that let users program up new queries interactively, on the fly, and then then render reports from those queries very smartly - composing various XML-ized style sheet fragments into a complete stylesheet which, as a final step, gets transformed to the syntax browsers like. Micro-formats on steroids, so to speak. -t _______________________________________________________________________ XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support XML implementation and development. To minimize spam in the archives, you must subscribe before posting. [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ Or unsubscribe: xml-dev-unsubscribe@l... subscribe: xml-dev-subscribe@l... List archive: http://lists.xml.org/archives/xml-dev/ List Guidelines: http://www.oasis-open.org/maillists/guidelines.php smime.p7s
Disclaimer
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

