[Home] [By Thread] [By Date] [Recent Entries]

  • To: xml-dev@l...
  • Subject: Re: [newbie] Mapping a Map 101?
  • From: PA <petite.abeille@g...>
  • Date: Mon, 13 Dec 2004 18:53:43 +0100
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=XZpiO7IVo61UUYyYm9vYQnDckKF+tBuOxdShVdEY+9gtUgjSilFpAxnrqszz2jQ+eBpjSKsO4cFuI0i4YjFePQWW9LS2o3gAgIlaDW1LEcEPr8wbRBNP0a6JQfn2MWbFrBKUiFrAV0OPOXtrWKQemYl4s92chYeRfIJe2NnXbUs=
  • In-reply-to: <E1CdtQZ-0004DY-00@u...>
  • References: <E1CdtQZ-0004DY-00@u...>


On Dec 13, 2004, at 17:51, Michael Kay wrote:

> If the data type really can vary from one instance to another, then you
> might possibly need something like this. I would tend to use the XML  
> Schema
> syntax:
>
>  <dict>
>       <entry>
>  	    <key xsi:type="xs:string">aKey</key>
>  	    <value xsi:type="xs:integer">101</value>
>       </entry>
>  </dict>
>
> In practice I think it's much more common that the data types are  
> implicit.

In the specific case I'm dealing with, both keys and values can be of  
any type.

One of the usage scenario is to serialized any type of object [1] [2]  
along the line of what JSX [3], XMLEncoder [4] or XStream [5] does  
while keeping the resulting XML more or less readable.

Cheers,

PA.

[1] http://java.sun.com/j2se/1.4.2/docs/api/java/io/Serializable.html
[2]  
http://developer.apple.com/documentation/Cocoa/Conceptual/Archiving/ 
index.html
[3] http://jsx.org/
[4] http://java.sun.com/j2se/1.4.2/docs/api/java/beans/XMLEncoder.html
[5] http://xstream.codehaus.org/


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member