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

Re: standard components edits

From: Alessandro Vernet <avernet@orbeon.com>
Date: Fri, 13 Apr 2007 14:19:23 -0700
Message-ID: <4828ceec0704131419s2e8f1666pd665bf31920b8a4a@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

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"?

> 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, or having multiple components, or
having the component do the right thing based on the content of its
input, whatever is the most appropriate. I don't see this as being
much different from the cases where a component could take different
XML applications as input.

Orbeon Forms - Web 2.0 Forms for the Enterprise
Received on Friday, 13 April 2007 21:35:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:42 UTC