Personally, I tend to avoid attributes unless it is for meta data. So
I would go for
<map>
<entry>
<key>abc</key>
<value representation='float'>123.456</value>
</entry>
</map>
On Fri, Jun 18, 2010 at 9:19 AM, Andrew Welch
<andrew(_dot_)j(_dot_)welch(_at_)gmail(_dot_)com> wrote:
On 18 June 2010 07:28, Wolfgang Laun
<wolfgang(_dot_)laun(_at_)gmail(_dot_)com> wrote:
Every now and then, people (not me) want to represent a Map<K,V> in XML by
using
s.th. like
<map>
<k1>v1</k1>
<k2>v2</k2>
...
</map>
with ki from K and vi from V. Apart from the obvious limitation for K's
values,
A less limiting approach is:
<map key=" " value=" "/>
I feel that this is somehow violating the spirit of XML.
I know what you mean.... but for name/value pairs its fine.
So, more specifically: Doesn't such a "structure" complicate the writing
of XSLT constructs? Aren't there any statements or expressions that
won't be usable at all? (I don't need an exhaustive list of what isn't
possible - I'm more interested in a general judgment.)
Not really. The only issue is with the QName limitation on the K
values, which you can avoid easily enough.
There was talk of "sequences of sequences" in 2.1... I don't know
whether that has made it.
--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/
--~------------------------------------------------------------------
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>
--~--
--
Nick
--~------------------------------------------------------------------
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>
--~--