OK, folks - thank you all; you have given me what I was asking for,
and I now see clearly the potential impact on XSLT.
(As I wrote, this is not an XML list; therefore discussing basic XML
techniques was not my intent.)
-W
On 18 June 2010 13:06, Mukul Gandhi <gandhi(_dot_)mukul(_at_)gmail(_dot_)com>
wrote:
On Fri, Jun 18, 2010 at 1:49 PM, Andrew Welch
<andrew(_dot_)j(_dot_)welch(_at_)gmail(_dot_)com> wrote:
A less limiting approach is:
<map key=" " value=" "/>
If the value is an element only or mixed content, then having an
attribute for value is I think ruled-out.
Then in that case, either we select Joe's solution or perhaps
something like what I wrote :)
If values are atomic, then your solution is fine.
--
Regards,
Mukul Gandhi
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--