[
Lists Home |
Date Index |
Thread Index
]
"Bob Foster" <bob@objfac.com> wrote in message
4022ACDD.4020304@objfac.com">news:4022ACDD.4020304@objfac.com...
> Dimitre Novatchev wrote:
> >>I found such a schema for XSLT 2.0, but not for XSLT 1.0. Even a
> >>correct-as-far-as-it-goes unofficial one would probably be adequate for
my
> >>needs.
> >
> > Such a schema wouldn't be too-useful, as XSLT allows any result nodes
and
> > any global-scope elements (and their descendents) that belong to a
non-XSLT
> > namespace.
>
> Yes but why wouldn't it be useful? Such a schema validates what it
> specifically describes and validates that what it doesn't specifically
> describe still operates within certain constrains.
What I mean is that the same result can be obtained by simply trying to
perform a transformation -- the XSLT processor performs this validation and
more.
>
> Beyond validation, I know that editor users are quite happy to have
> schema-driven assist/completion for XSLT elements and attributes, and
> even some level of schema-driven assistance can be provided for non-XSLT
> nodes, though they aren't always even locally valid. Not perfect, but
> useful.
Yes, an XSLT IDE can use such a schema.
However, the question was about validation and not about schema-driven XSLT
editors.
Apart from this I share completely your opinion.
Cheers,
Dimitre Novatchev
FXSL developer,
http://fxsl.sourceforge.net/ -- the home of FXSL
Resume: http://fxsl.sf.net/DNovatchev/Resume/Res.html
|
