At 09:32 AM 11/9/2004, Jeni wrote:
I'd like to see the above mechanisms provide a "strict" level of
auto-completion and static checking, in which programmers are actually
limited to only generating legal paths and result trees. But I'd also
like to see editors and processors providing a "lax" level of
checking. Under the lax mode, the processor would, as George
suggested, use the union of the possibilities to offer hints and
provide warnings, but still allow the programmer to name elements that
aren't actually permitted according to the schema. An editor or
processor could offer this support without the stylesheet actually
importing any schemas (with <xsl:import-schema>), which would help
writers of non-schema-aware XSLT 2.0 as well.
This "lax" level is particularly important since another emerging trend is
the use of different schemas for the same document at different points in
its lifecycle (as Mike has sometimes remarked in other contexts). The
schema you are using may not be the schema for which the stylesheet was
designed, and loose coupling still has advantages.
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================