Subject: Re: [xsl] use cases for d-o-e From: David Carlisle <davidc@xxxxxxxxx> Date: Thu, 10 Jan 2002 22:47:09 GMT |
> I mean, you > can create processing instructions, elements, attributes and comments; why > leave entities out of the mix? entities are designed to be author shortcut facility, the whole point is thatyou can use an entity to give a shorthand and any XML application essentially won't see it, it's just a syntactic variation like using " or ' around attribute values. If it wasn't this way you'd have to be worried about whether it was ever "safe" to make an entity or whetehr you always need to enter th efully expanded version. This is completely different to pis and elements which don't expand to anything they are just data items (aka nodes aka infoset items). So Xpath arranges this by fully expanding entities as the first thing it does and never "seeing" them at all. This model is almost allways what you want on input, although it does sometimes complicate the issue of generating the entity refs on output. David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] use cases for d-o-e, KIENLE, STEVEN C [IT | Thread | RE: [xsl] use cases for d-o-e, Bryan Rasmussen |
Re: [xsl] use cases for d-o-e, David Carlisle | Date | [xsl] xsl:variable, Jennifer Hochgesang |
Month |