[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Grand Unification Theory (XSL/XPointer)
Hi, Still continuing to think on XPointer and XSL relationship. Here is a concrete example of two expressions with the same meaning that should in the best world be re-united. Document <doc> <element1> <element2>element1 data</element2> <element2>element1 data</element2> </element1> </doc> XPointer: descendant(all,element2) XSL: "/element2" Both terms means that we obtain all element2 contained in the XML document. The first notation is procedural (or looks procedural), the second is more functional. The descendant relationship is implicit in the notation where each context is delimited by a "/" like found in hierarchical file systems. Two world, same meaning, two kingdoms, two languages :-) I spent some time reading the proposals and postings on XQL from the last workshop on Queries. If we look at what XPointer, XSL and XQL try to resolve is "get me this or these objects based on this or these criteria". All have to deal with class based queries and instance based queries. We should be able to leverage our knowledge from one world to the other. In fact, all these worlds should be set or subset of the same world. But today, we have three different worlds and ways of saying things. regards Didier PH Martin mailto:martind@xxxxxxxxxxxxx http://www.netfolder.com XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|