RE: [xml-dev] Blog post on limitations of import/include in W3C XML Sche

[noah_mendelsohn@us.ibm.com]

I think it's also important to point out that one of the reasons that the 
core composition mechanisms of W3C XML Schema give a great deal of 
latitude as to how schemas are assembled.  Speaking for myself, I believe 
this has been done in part so that others can create schema repositories 
for various purposes.  It's my intuition that different sorts of 
repositories will be needed according to the circumstance.  For example, 
IBM's DB2 product has particular mechanisms that it uses to store schemas 
in its relational/XML store, and to decide which ones to use for 
particular validations.  So, it's not clear to me that there is one 
particular repository that the Schema WG "should" have defined in the core 
recommendation. Still, I believe there are few architetural impediments to 
layering on such repositories if they're needed, much as various different 
code repositories can be integrated to support the build and runtime 
environments of languages like Java.

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------








"Michael Kay" <mike@saxonica.com>
10/16/2007 02:14 PM
 
        To:     <abcoatesecure-xmldev@yahoo.co.uk>, "'XML-dev list'" 
<xml-dev@lists.xml.org>
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        RE: [xml-dev] Blog post on limitations of 
import/include in W3C XML Schemas


Useful input. We're doing some work on schema composition in the Schema WG
right now. I don't think it will include any kind of concept of
repositories, but it does aim to achieve a better balance between
interoperable/predictable behaviour and extensible/customizable behaviour
than we have now. At present there's enough abstraction built in to meet 
the
needs of most scenarios, I think, but too much abstraction to achieve
interoperable behaviour in all but the most simple cases.

Michael Kay
http://www.saxonica.com/


> -----Original Message-----
> From: Anthony B. Coates (XML-Dev) 
> [mailto:abcoatesecure-xmldev@yahoo.co.uk] 
> Sent: 16 October 2007 18:20
> To: XML-dev list
> Subject: [xml-dev] Blog post on limitations of import/include 
> in W3C XML Schemas
> 
> I've just published a blog post on limitations that I've 
> found in practice with the import/include mechanisms that W3C 
> XML Schemas provide.  See
> 
> http://kontrawize.blogs.com/kontrawize/2007/10/the-trouble-wit.html
> 
> Comments are welcome.
> 
> Cheers, Tony.
> --
> Anthony B. Coates
> Senior Partner
> Miley Watts LLP
> Experts In Data
> UK: +44 (20) 8816 7700, US: +1 (239) 344 7700
> Mobile/Cell: +44 (79) 0543 9026
> Data standards participant: genericode, ISO 20022 (ISO 15022 
> XML), UN/CEFACT, MDDL, FpML, UBL.
> http://www.mileywatts.com/
> 
> ______________________________________________________________
> _________
> 
> XML-DEV is a publicly archived, unmoderated list hosted by 
> OASIS to support XML implementation and development. To 
> minimize spam in the archives, you must subscribe before posting.
> 
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org List archive: 
> http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> 


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php