W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > December 2006

RE: ISSUE-100: LC: Basic Profile Compliant Import

From: <paul.downey@bt.com>
Date: Tue, 12 Dec 2006 11:53:46 -0000
Message-ID: <2A7793353757DB4392DF4DFBBC9522550A2012EB@I2KM11-UKBR.domain1.systemhost.net>
To: <public-xsd-databinding@w3.org>, <public-xsd-databinding@w3.org>

OK, George pointed out to me (offline) that this 
isn't a chameleon import, it's the reverse 
- a no-namespace schema importing one with a targetNamespace
(i must be going daft or someting :-)

I also wonder if this pattern actually works as the 
scope of imported symbols aren't (AIUI) transitive.


I guess more investigation is required. 
I'll write an example.

FWIW this is exhibited by a number of different WSDLs 
in the wild, including WS-Trust:


-----Original Message-----
From: public-xsd-databinding-request@w3.org on behalf of Databinding Issue Tracker
Sent: Tue 12/12/2006 11:29 AM
To: public-xsd-databinding@w3.org
Subject: ISSUE-100: LC: Basic Profile Compliant Import

ISSUE-100: LC: Basic Profile Compliant Import


Raised by: Paul Downey
On product: Basic

it appears that the only way to import a schema and be 
able to reference the elements from a WSDL message 
and remain Basic Profile compliant is as follows:


That is, you have to use a chameleon schema which the 
Basic Patterns document preculudes due to known interoper
issues with tools.

Is this constrained pattern well enough supported by tools 
to be included in the "Basic" document?

Received on Tuesday, 12 December 2006 11:54:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:57 UTC