I feel, if XSLT 2.0 spec provides an accurate XML
schema for the language, it is a very useful thing. It
can server as a grammer checker for the XSLT
language(for e.g to XSLT processor writers). It would
also be very useful for providing intellisense support
in XSLT editors. I have named 2 uses.. There may be
more..
Regards,
Mukul
--- Peter Gerstbach <peter(_at_)gerstbach(_dot_)at> wrote:
Quoting Dimitre Novatchev <dnovatchev(_at_)gmail(_dot_)com>:
So why not have two schemas from the XSLT 2.0 WG:
the current one with
all bells and whistles and a much simpler one that
will be easily and
immediately dropable in most of today's not so
clever schema-oriented
text editors?
What is the intended purpose of the schema in
current XSLT 2.0 Draft? Is it
validation of stylesheets? Or is it providing a
simple way to implement entry
helpers for XML editors? Or feeding as an input for
source generators
(XML Data
Binding)?
There are numerous products which are great although
the Schema support is not
complete. Complete support is good of course, but
mostly not the main focus of
development.
In my opinion a much simpler schema would be great.
But it would be
difficult to
decide what to leave out. But the thing with
complexContent inside a
SimpleType
might be a good candidat. ;)
Regards,
Peter Gerstbach
--~------------------------------------------------------------------
XSL-List info and archive:
http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to:
http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--