This is the mail archive of the xsl-list@mulberrytech.com mailing list .

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: keys and idrefs - XSLT2 request?

To: <xsl-list at lists dot mulberrytech dot com>
Subject: Re: [xsl] keys and idrefs - XSLT2 request?
From: "Evan Lenz" <elenz at xyzfind dot com>
Date: Wed, 10 Oct 2001 10:23:55 -0700
References: <9B66BBD37D5DD411B8CE00508B69700FE7A580@pborolocal.rnib.org.uk><9412977570.20011010123014@jenitennison.com><200110101200.NAA24398@penguin.nag.co.uk> <m3k7y32yuq.fsf@colina.demon.co.uk>
Reply-To: xsl-list at lists dot mulberrytech dot com

Colin Paul Adams wrote:
> But they ARE required to read the internal subset, so people can
> always declare attributes as ID attributes there.

That's right. This means that XSLT 1.0's data model, at least, has the
desirable property that all potential source tree information can be
serialized in the instance.

The only missing pieces of closure are the inability to construct arbitrary
namespace nodes and the inability to construct ID-typed attributes in the
result.

Evan Lenz
XYZFind Corp.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

References:
- RE: keys and idrefs - XSLT2 request?
  - From: DPawson
- Re: keys and idrefs - XSLT2 request?
  - From: Jeni Tennison
- Re: keys and idrefs - XSLT2 request?
  - From: David Carlisle
- Re: keys and idrefs - XSLT2 request?
  - From: Colin Paul Adams

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]