W3C home > Mailing lists > Public > xmlschema-dev@w3.org > March 2001

Re: webMethods' XML Schema for XSLT 1.0

From: Asir S Vedamuthu <asirv@webmethods.com>
Date: Fri, 30 Mar 2001 11:02:34 -0500
Message-ID: <018301c0b932$d523cb10$0846010a@webmethods.com>
To: "Eric van der Vlist" <vdv@dyomedea.com>, <xmlschema-dev@w3.org>
Of the 3 suggestions, this one is not valid as per Part 2 [1],

"We say that two non-group particles overlap if ...

- One is a wildcard and the other an element declaration, and the {target
namespace} of the element declaration, or of any member of its ?substitution
group, is ?valid with respect to the {namespace constraint} of the wildcard.

...

A content model will violate the unique attribution constraint if it
contains two particles which ?overlap and which either

- are both in the {particles} of a choice or all group "

Good catch and thank you. I will remove or fix it in the next iteration. The
processor I used is little more powerful and can handle this construct.

[1] http://www.w3.org/TR/2001/PR-xmlschema-1-20010316/#non-ambig

Regards, Asir
----- Original Message -----
From: "Eric van der Vlist" <vdv@dyomedea.com>
To: <xmlschema-dev@w3.org>
Sent: Friday, March 30, 2001 3:14 AM
Subject: Re: webMethods' XML Schema for XSLT 1.0


> Asir S Vedamuthu wrote:
> >
> > webMethods is pleased to announce the availability of an experimental
> > version of XML Schema for XSLT 1.0 More information on XSLT can be found
at
> > http://www.w3.org/TR/xslt
>
> Impressive work!
>
> I have a question about one of the ways you are suggesting to
> pre-validate the target documents, though.
>
> <quote source="comments from the schema">
> There are three ways that you can construct a schema for XSLT
> stylesheets that create instances of a particular result structure
> (a) Declare all your result elements as a member of xsl:result-element
> substitution group
> </quote>
>
> The substitution group is defined as:
>
>   <element name="result-element" abstract="true"/>
>
> and used in a group:
>
>   <group name="result-element">
>     <choice>
>       <element ref="xsl:result-element"/>
>       <any namespace="##other" processContents="skip"/>
>     </choice>
>   </group>
>
> that is referenced when needed.
>
> I have probably missed something, but won't the choice become ambiguous
> if I include elements from any namespace other than the target namespace
> (i.e. XSLT 1.0) that would also match "any" element ?
>
> Thanks
>
> Eric
> --
> See you in San Jose for SD West:
> http://cmp.bluedot.com/re/attendee/sdw/speakerPage.esp?speakerId=36534626
> ------------------------------------------------------------------------
> Eric van der Vlist       Dyomedea                    http://dyomedea.com
> http://xmlfr.org         http://4xt.org           http://examplotron.org
> ------------------------------------------------------------------------
Received on Friday, 30 March 2001 11:01:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:20 GMT