OK
Let me try:
Two documents doc1 and doc2. Each document is represented by an repectively
InfoSet i1 and i2. InfoSet i1 has a reference to InfoSet i2 via a key or
XPointer.
In a reference or linking case there are 2 infosets i1 and i2. In XInclude,
wouldn't there be just one InfoSet ib which
Jim Tivy wrote:
> I would suggest that XInclude is an entirely different technology - more
> like an entity expansion.
It is fine to suggest this, but your suggestion provides no guidance to the
characteristics of this "entirely different technology". If you read my
reply to Paul, you should note
Paul Rabin wrote:
>
> At 10:11 AM 7/25/01 -0400, Jonathan Borden wrote:
>
> >Ok I understand that the attribute has a different name (that is one
> >difference). I still don't understand how it functions in a different
way.
> >In specific an implementation of XInclude acts _as if_ the included
docu
I would suggest that XInclude is an entirely different technology - more
like an entity expansion.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Jonathan Borden
> Sent: Wednesday, July 25, 2001 7:11 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Preparing
Jonathan,
At 10:11 AM 7/25/01 -0400, Jonathan Borden wrote:
Ok I understand that the attribute has a different name (that is one
difference). I still don't understand how it functions in a different way.
In specific an implementation of XInclude acts _as if_ the included document
was in the inclu
Paul Rabin wrote:
> At 11:36 PM 7/24/01 -0400, Jonathan Borden wrote:
>
> >Well assuming the attribute is "xml:include" then this is identical to
> >XInclude isn't it? Seriously, what is the essential difference between
this
> >'experimental linking facility' and XInclude?
>
> Jonathan,
>
> Actuall
On Mon, 23 Jul 2001 09:10:32 -0700
Kimbro Staken <[EMAIL PROTECTED]> wrote:
>
> On Monday, July 23, 2001, at 08:59 AM, Lars Martin wrote:
> >
> > Do you mean the discussion with the Jochen Wiedman (Software AG) here
>
> This is from the thread XPath Queries: Resources without ID
Ok. What was
Hi
While testing my stuff I stumbled across a bug in SetContentHandler. It
does not work properly with default namespaces ( 0) {
newContent.append(":");
newContent.append(key);
}
newContent.append("=");
newContent.append("\"");
newContent
At 11:36 PM 7/24/01 -0400, Jonathan Borden wrote:
Well assuming the attribute is "xml:include" then this is identical to
XInclude isn't it? Seriously, what is the essential difference between this
'experimental linking facility' and XInclude?
Jonathan,
Actually, the attribute is xlnlink:href. An
Paul Rabin wrote:
>
> At 06:15 PM 7/23/01 -0700, you wrote:
> >dbXML has autolinking which is pretty much a combination between
> XInclude
> >and XLink. It's just an experimental feature though and has issues in
> >relation to the current API. It's also of course specific to dbXML and
> >ties the i
10 matches
Mail list logo
