OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: auto/embed is not node transclusion

[ Lists Home | Date Index | Thread Index ]
  • From: "Jonathan Borden" <jborden@mediaone.net>
  • To: "Paul Prescod" <paul@prescod.net>, <xsl-list@mulberrytech.com>, <xlxp-dev@fsc.fujitsu.com>, "xml-dev" <xml-dev@ic.ac.uk>
  • Date: Fri, 14 May 1999 09:33:13 -0400

Paul Prescod wrote:

> Now let demonstrate that XLink does not provide transclusion. First, it
> does not specify a data model for the result of a transformation. Second,
> the things it links to are not restricted to XML elements. In other words,
> XLink can embed JPEGs, MPEGs and other data that does not have a concept
> of nodes (unless we import the ISO concept of groves and property sets for
> them). Therefore we *cannot* in general interpret the grove mode in terms
> of a grove to grove transformation.

	This is an excellent point. In XSLT 6.2.2 the issue of doc(uri) pointing to
something other than an XML node is noted as an unresolved editorial point.

> You could argue that I am being a purist. Embedding PDFs or JPEGs would
> "probably" have the behavior of just *displaying* them inline but
> embedding an XML element would have the behavior of node-level
> transcluding it. Browsers would "probably" implement it compatibly.

	Would links to binary resources have the same status as NOTATION's in terms
of the XML information set? A set of notations could map to the returned
content-type and a browser would deal with such a 'notation' in the same
mechanism that a MIME content-type is dealt with (e.g. in-line, plug-in

> I am not very confident of interoperable implementations by the major
> browser vendors. Personally, I feel that I would rather wait for a real
> transclusion mechanism even if it means I have to wait for a W3C grove
> model and addressing mechanism that can differentiate a reference to an
> input document from a reference to the result document.

	Or, we can adopt the ISO grove model once the XML property set/information
set is defined. Is there any reason to reinvent the wheel in terms of

Jonathan Borden

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS