Reply to thread

Message

<blockquote data-quote="pezagent" data-source="post: 1263968" data-attributes="member: 15568">Which &quot;old subject&quot; are you referring to here? XSL is a declaritive programming language, currently evolving, which uses other languages such as XPath. SGML, the parent of all markup, is as old as I am, and that's a bit more than two decades. Try three and a half. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink&nbsp; &nbsp; ;)"&nbsp; data-smilie="2"data-shortname=";)" />It would be interesting to see you try and run that statement by the Mulberry list and see what sort of response you get there--if anyone would actually bother to respond to it.I'm not&nbsp; sure what you mean here by &quot;pointless.&quot; And when it comes to computers I'm not sure I like the idea of &quot;roughly the same information,&quot; or &quot;very close data structure.&quot; There's no room for approximations when developing applications. We're not rearranging furniture or putting up curtains here. Different applications require different data structures. The application isn't built around the data format.Transformation allows two applications to retain control over a proprietary data structure and easily share that information with other applications without others having to write a new parser for each transformation. Furthermore, XSL not only transforms the data but can parse it, merge it, sort it, group it--most anything you need to be done to the data can all be done with stylesheets. The whole point of transformation is so XML documents don't have to have a common, or &quot;standard&quot; format. So application developers can build data structures and change them later as needs dictate. That's the whole point of using XML as an extensible markup language./johnny <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" /></blockquote>

[QUOTE="pezagent, post: 1263968, member: 15568"] Which "old subject" are you referring to here? XSL is a declaritive programming language, currently evolving, which uses other languages such as XPath. SGML, the parent of all markup, is as old as I am, and that's a bit more than two decades. Try three and a half. ;) It would be interesting to see you try and run that statement by the Mulberry list and see what sort of response you get there--if anyone would actually bother to respond to it. I'm not sure what you mean here by "pointless." And when it comes to computers I'm not sure I like the idea of "roughly the same information," or "very close data structure." There's no room for approximations when developing applications. We're not rearranging furniture or putting up curtains here. Different applications require different data structures. The application isn't built around the data format. Transformation allows two applications to retain control over a proprietary data structure and easily share that information with other applications without others having to write a new parser for each transformation. Furthermore, XSL not only transforms the data but can parse it, merge it, sort it, group it--most anything you need to be done to the data can all be done with stylesheets. The whole point of transformation is so XML documents [b]don't[/b] have to have a common, or "standard" format. So application developers can build data structures and change them later as needs dictate. That's the whole point of using XML as an [b]extensible[/b] markup language. /johnny :) [/QUOTE]

Verification