Hello,

perhaps it is also worthwhile to check how MarkLogic serializes maps.

Kind regards,

Hans-Juergen Rennau

PS: Here comes an example (representing a map containing map):

<map:map xmlns:map="http://marklogic.com/xdmp/map">

   <map:entry key="GlobalDates">
      <map:value xsi:type="map:map">
         <map:map>
            <map:entry key="Booking">
               <map:value xsi:type="xs:date">2012-03-22</map:value>
            </map:entry>
            <map:entry key="Duration">
               <map:value xsi:type="xs:integer">7</map:value>
        </map:entry>
        <map:entry key="CheckIn">
           <map:value xsi:type="xs:date">2012-06-04</map:value>
            </map:entry>
        <map:entry key="CheckOut">
           <map:value xsi:type="xs:date">2012-06-11</map:value>
      </map:entry>
     </map:map>
</map:value>
   </map:entry>

</map:map>

    Von: Charles Duffy <charles@dyfis.net>
 An: basex-talk@mailman.uni-konstanz.de 
 Gesendet: 2:05 Dienstag, 27.März
 2012
 Betreff: [basex-talk] Mechanism to serialize maps in output?
  

Howdy --

Right now, trying to inspect a map (ie. returning one from a query) results in FOTY0012. This is unfortunate from the perspective of allowing users to examine the objects their logic creates. Has thought been given to defining a serialization-friendly way of representing maps, perhaps as XML entities under their own namespace?