Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Re: Output validation with XSLT 2.0

From: "Dimitre Novatchev" <dnovatchev@--------->
To:
Date: 5/4/2008 3:30:00 PM
> >  >  > Just read the relevant W3 Specs and any good XSLT book.
> >
> >  You could reply with that to any question...
> >
>  not really, the relevant W3 specs are not meant to be read by users
> of the language but implementors.

While user-friendliness is often not a goal, no such specification
forbids anyone from reading it, and users with a grain of curiosity
usually do.

Shouldn't users report bugs? How can we report a bug in an
implementation, without having read the spec?

And what if there are two good books that say different things about a
feature? Isn't then the spec the "true source" to be used in resolving
any such ambiguities?



-- 
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play


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