Clark Evans suggested a distinct Script initiative to coordinate the
distinct script elements in XHTML, SVG and XSLT 1.1. Jon Ferraiolo
thought that might be the best long term solution
guess my question is what is the short term solution.
Would it be possible to execute a distinct XML Script effort (possibly
as part of XHTML modularization?) that SVG and XSLT 1.1 could use
without disrupting SVG's march to recommendation?
Maybe we could at least informally collect the requirements:
1. Must be usable in XHTML, SVG and XSLT
2. Should be compatible with XHTML 1.0 script.
3. Syntax must support behavior implemented in major scripting languages.
4. Syntax must support behavior implemented in major component
technologies (Java, COM, CORBA, .NET).
5. Behavior may be identified with a namespace URI
6. Specification of multiple implementations for a specific behavior
namespace must be allowed.
7. Processor must be allowed to choose preferred implementation.
8. Processor may resolve behavior through RDDL, Classpaths, COM
registry, CORBA naming servers, etc and ignore script declarations.
9. Spec must address under what conditions script names must or must not
be qualified with a namespace prefix when referenced from outside the
10. An XML application (that is SVG or XSLT) must be able to either
require or forbid namespace identification of behavior and prefix
qualification of script names.
11. A document must be able to indicate whether failure to locate a
script resource should prevent a document from being displayed.