Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] MatTS, an alternate syntax for XSLT

From: Colin Paul Adams <colin@------------------>
To:
Date: 4/1/2006 4:34:00 PM
>>>>> "Michael" == Michael Kay <mike@xxxxxxxxxxxx> writes:

    Michael> I find it mildly disappointing that you are still using
    Michael> long-winded names like "trackNbr" in your XML source
    Michael> documents, and that XPath function names still have
    Michael> long-winded names like, well, "name". Surely it's time we
    Michael> established a convention that all elements in user
    Michael> documents should be denoted by a single Kanji, and that
    Michael> function names should be written in Hebrew?

I think you are being unreasonable here:

1) Owing to han unification, it is impossible (in general) to
   distinguish between knaji and hanzi. Therefore validation would not
   be possible.
2) Since Hebrew is read backwards, it would be necessary to stand on
   your head in order to parse the XSLT. I suppose this is a valid
   transformation, but it is alittle hard on the casual user,
   especially for those of us who are not quite so agile as we were in
   our youth.
-- 
Colin Adams
Preston Lancashire


transparent
Print
Mail
Like It
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.

.
.

transparent

transparent