W3C home > Mailing lists > Public > www-xml-xinclude-comments@w3.org > March 2002

Re: What does 'ignored' mean?

From: Martin Gudgin <marting@develop.com>
Date: Wed, 13 Mar 2002 11:35:10 -0000
Message-ID: <025801c1ca83$23d25d00$8601a8c0@greyarea>
To: "Jonathan Marsh" <jmarsh@microsoft.com>, <www-xml-xinclude-comments@w3.org>

Thanks for the clarification, that will help me get my implementation


----- Original Message -----
From: "Jonathan Marsh" <jmarsh@microsoft.com>
To: "Martin Gudgin" <marting@develop.com>;
Sent: Tuesday, March 12, 2002 10:51 PM
Subject: RE: What does 'ignored' mean?

They both are correct :-).

The XInclude processor replaces the include element, and all it's
content, so any children of the include element disappear from the
result infoset.

However, this does not mean that the content cannot be useful for a
higher level application prior to include processing, or made available
through infoset extensions after include processing.  The XInclude spec
doesn't describe how this might be done but is careful not to preclude
the possibility.

- Jonathan

> -----Original Message-----
> From: Martin Gudgin [mailto:marting@develop.com]
> Sent: Tuesday, March 12, 2002 10:38 AM
> To: www-xml-xinclude-comments@w3.org
> Subject: What does 'ignored' mean?
> In updating my XInclude implementations to support the latest spec I
> notice
> the following phrase in Section 3.1[1]
> ' The content of the xi:include element may include an xi:fallback
> element.
> Other content is not constrained by this specification and is ignored
> the
> XInclude processor.'
> What does 'ignored' mean in this context? I can think of two possible
> interpretations;
> 1.    XInclude processor drops all content apart from xi:fallback on
> floor
> 2.    XInclude processor passes all content apart from xi:fallback to
> higher
> level application
> Which is correct?
> Martin Gudgin
Received on Wednesday, 13 March 2002 06:35:37 UTC

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