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

Re: standard components edits

From: Innovimax SARL <innovimax@gmail.com>
Date: Sat, 14 Apr 2007 02:58:35 +0200
Message-ID: <546c6c1c0704131758y6054c1caqd109bf5e161874de@mail.gmail.com>
To: "Alessandro Vernet" <avernet@orbeon.com>
Cc: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

On 4/13/07, Alessandro Vernet <avernet@orbeon.com> wrote:
>
> On 4/13/07, Innovimax SARL <innovimax@gmail.com> wrote:
> > Ok I see two edge cases :
> > 1) we have to use XML Schema datatypes in XProc
>
> How is this an "edge case"?

You mandate to the user to use (and understand) XML Schema Datatype

>
> > 2) how do you inform the component that your input is an
> > *embedded-in-xml* one ? so how ,in case there could be embedded-in-xml
> > and natural-xml, do you make the difference (XQuery vs XQueryX,
> > RDF/XML vs Turtle, Relax NG Compact vs Relax NG, JSON vs XML, DTD vs
> > XML Schema, ...) ?
>
> For instance using a parameter,

that's a form of typing

> or having multiple components,

so you would ask for XSLT-xml and XSLT-html-or-text ?

> or
> having the component do the right thing based on the content of its
> input, whatever is the most appropriate.

The burden is very high for the implementor in that case.

> I don't see this as being
> much different from the cases where a component could take different
> XML applications as input.

Different applications as input is different than different form of
the same application because in that case one substitute to the other


>
> Alex
> --
> Orbeon Forms - Web 2.0 Forms for the Enterprise
> http://www.orbeon.com/
>
>


-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 8 72 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Saturday, 14 April 2007 00:58:44 GMT

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