Chameleon components

A couple of recent threads have indicated support for a sort of
chameleon component that I'd just assumed we wouldn't touch with a ten
foot pole.

If

  <p:step type="validate">...</p:step>

can do one of several different kinds of validation (XSD, RNG, SCH)
and

  <p:step type="xslt">...</p:step>

can perform either XSLT 1.0 or XSLT 2.0 transformations, then I
think we have a clear need for two different types of parameters
(which I'd been hoping, perhaps naively, that we could avoid).

If we're going to go this way, I wonder if it's worth revisiting the
names of components. Using the types as the GIs would give us two
places to put parameters: on the element or in a p:parameter.

  <p:validate language="http://www.w3.org/2001/XMLSchema">
    ...
  </p:validate>

and

  <p:xslt version="2.0">
    <p:param version="1.2"/>
    ...
  </p:xslt>

would be unambiguous.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.