- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Thu, 12 Jun 2003 16:48:46 -0700
- To: "Peter McCracken" <peterjm@ca.ibm.com>, <www-xml-xinclude-comments@w3.org>
I haven't heard that problem before, and it concerns me. XInclude adds xml:base attributes so that the [base URI] property and any xml:base attributes stay in sync. However, this could be considered the job of the serializer rather than XInclude, which already has to account for the possibility of [base URI] changes even if no xml:base attributes are present. Perhaps there should be a processor option for turning off the automatic insertion of xml:base attributes. Or maybe this is just a clue that schema writers should make allowances for xml:base attributes, which might be added by XInclude, or by [base URI]-aware serializers. > -----Original Message----- > From: www-xml-xinclude-comments-request@w3.org [mailto:www-xml-xinclude- > comments-request@w3.org] On Behalf Of Peter McCracken > Sent: Thursday, June 12, 2003 2:09 PM > To: www-xml-xinclude-comments@w3.org > Subject: xml:base attributes and Schema Validation > > > Hello, > > I'm implementing an XInclude processor, and one of my goals is to make the > processing transparent to the Schema validator, if the XInclude processing > is performed before the validation. > > However, in section 4.5.5 of the spec, it is specified that xml:base > attributes are added to the top level included items, if the [base URI] is > different than the include parent's [base URI]. This creates problems with > schema validation, unless the xml:base attribute is specifically allowed > in > the schema, which interferes with the transparency of the XInclude > processor. > > I'm wondering if anyone else has encountered this problem, and in hearing > any approaches they had to solving it. > > Thank you, > Peter McCracken > IBM Toronto Lab
Received on Thursday, 12 June 2003 19:49:06 UTC