W3C home > Mailing lists > Public > www-xml-xinclude-comments@w3.org > January 2003

RE: Non-defined elements in XInclude namespace

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Wed, 8 Jan 2003 12:48:29 -0800
Message-ID: <330564469BFEC046B84E591EB3D4D59C08D1D288@red-msg-08.redmond.corp.microsoft.com>
To: "Elliotte Rusty Harold" <elharo@metalab.unc.edu>
Cc: <www-xml-xinclude-comments@w3.org>

Thank you for bringing this problem to our attention.  We resolved the
issue as follows:

An xi:include element can contain any content EXCEPT elements in the
XInclude namespace other than a single optional xi:fallback element.

A related problem was also addressed:  attributes on xi:fallback
elements are now explicitly treated consistently with attributes on
xi:include - additional attributes are allowed, but unprefixed ones are
reserved for future versions of XInclude.

If you do not agree with this resolution, please let us know.  If we
don't hear from you by Jan 20th, we'll assume that you are satisfied
with this resolution.

Thanks again for your attention to detail in reviewing the XInclude
spec!

Jonathan


> -----Original Message-----
> From: Elliotte Rusty Harold [mailto:elharo@metalab.unc.edu]
> Sent: Thursday, October 10, 2002 6:27 AM
> To: www-xml-xinclude-comments@w3.org
> Subject: Non-defined elements in XInclude namespace
> 
> 
> The 2nd candidate rec specifies what should be done with unrecognized,
> unqualified attributes on an include element. (Ignore them.) However,
it
> does not appear to say anything about what a processor shoudl do if it
> encounters an undefined element in the XInclude namespace; that is,
one
> whose local name is not include or fallback.
> 
> I'm not sure whether this should generate a fatal error or simply be
> ginored and treated like any other element from a different namespace
or
> perhaps even dropped out of the document completely. I suggest the
spec
> address this point explicitly.
> 
> --
> Elliotte Rusty Harold
Received on Wednesday, 8 January 2003 15:49:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:56 UTC