W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > February 2007

Re: Chameleon components

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Wed, 07 Feb 2007 13:55:45 -0500
To: public-xml-processing-model-wg@w3.org
Message-ID: <87r6t123wu.fsf@nwalsh.com>
/ Innovimax SARL <innovimax@gmail.com> was heard to say:
| This is supposed to work for component defined by the WG (in core or elsewhere)
| But what about component used defined ?

As Alex said, I think we'd need to provide a way for users to declare
additional "component namespaces".

| This implies AFAIK that user defined components won't have access to
| "component parameters" (as opposed to "instance parameters" to pass
| trough to the component).

I don't follow. If I declare that http://nwalsh.com/xproc/compenents is
a component namespace, then I can say:

  <x:myFancyComponent xmlns:x="http://nwalsh.com/xproc/compenents"
      componentParam="foo">
    <p:parameter name="someName" value="5"/>
  </x:myFancyComponent>

The user-defined component will have access to both componentParam and
someName.

| This is from my point of vue a serious limitation for V.next.

Perhaps I didn't understand your concern.

| Moreover, is there really no use case for component to have complex
| (as opposed to simple, as simpleType) "component parameters" ? In
| those case, if they exists, and I supposed they do, the attribute will
| be a serious limitation.

I don't know of one. I don't think any of the standard components have
this requirement. That might require putting structure inside the
call, or it could be done by reference:

  <x:otherComponent paramRef="fribble">
     ...
  </x:otherComponent>

  <x:myData xml:id="fribble">
    <doc/>
  </x:myData>

| Then, it will look like <p:xslt, will have similar look as <p:for-each
| or <p:choose which is a bit annoying.

Yeah, but I can't decide if that's a bug or a feature.

| Furthermore, for authoring tool, it won't be so easy to move from a
| component call to another, especially from a core one (p:xslt) to a
| user defined one (p:step name="my:xslt") and vice versa.

The tool will have to know about the extension components, that's
true.

                                        Be seeing you,
                                          norm

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

Received on Wednesday, 7 February 2007 18:56:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:49 GMT