103 | | ''Well, but Markup '''is''' mostly about Markup, just not exclusively. So we'd have to use something like XAJM (XAJM Ain't Just Markup) :-P[[BR]] -- cmlenz'' |
| 103 | > ''Well, but Markup '''is''' mostly about Markup, just not exclusively. So we'd have to use something like XAJM (XAJM Ain't Just Markup) :-P[[BR]] -- cmlenz'' |
| 104 | Well, the ''Not'' in X__N__M has to be interpreted in the same spirit as the ''Not'' in G__N__U: ''Not'' xyz but mostly about xyz anyway... [[br]] |
| 105 | - cboos |
| 106 | |
| 107 | By the way, exploring the '''X'''YX line, I came up with: |
| 108 | |
| 109 | == “XSTL” == |
| 110 | |
| 111 | Which would stand for '''e__X__tensible __S__tream-based __T__emplate __L__anguage''', which seems to describe Markup quite accurately. |
| 112 | The name is of course close to ''XSLT'', and that's fine because Markup is conceptually close to XSLT, only that it does things in the ''correct order'' (data → transform → xml, as opposed to data → xml → transform → xml). Plus, there's the connection introduced by XPath, used by both. |
| 113 | Finally, imagine the number of people who would stumble upon Markup by mistyping xslt ;) |
| 114 | [[br]] |
| 115 | - cboos |
| 116 | |