Altova Mailing List Archives

Re: [xsl] RELAX NG validator

From: Colin Paul Adams <colin@------------------>
Date: 9/27/2005 9:29:00 AM
>>>>> "Dimitre" == Dimitre Novatchev <dnovatchev@xxxxxxxxx> writes:

    Eric> XSLT 2.0 would help if you wanted to support W3C XML Schema
    Eric> datatypes which would be tough to support with XSLT 1.0.

Note that this would require a schema-aware processor for the full
datatype library - a basic XSLT processor must only support a subset.

    Dimitre> Of course, a function, which takes a list of grammar
    Dimitre> rules and returns another function, which is a parser for
    Dimitre> this grammar -- such parser generator *is* of very high
    Dimitre> importance.

    Dimitre> People have done this in Haskell -- look for example for
    Dimitre> Erik Meijer's PARSEC -- yes, the same Erik Meijer, who
    Dimitre> was the mind behind XLINQ.

What's XLINQ?
I know of Erik from PARSEC.
I had some bad experiences trying to figure out how to do things with
parsec (I was trying to add namespace support to HaXML in order to
write an XSLT processor in Glasgow Parallel Haskell - I'll try this
again one day in Eiffel).
Colin Adams
Preston Lancashire


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 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.