<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Jun 22, 2013 at 5:19 AM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug.hellmann@dreamhost.com" target="_blank">doug.hellmann@dreamhost.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Fri, Jun 21, 2013 at 3:46 PM, Vishvananda Ishaya <span dir="ltr"><<a href="mailto:vishvananda@gmail.com" target="_blank">vishvananda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div><div>On Jun 21, 2013, at 12:38 PM, Doug Hellmann <<a href="mailto:doug.hellmann@dreamhost.com" target="_blank">doug.hellmann@dreamhost.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 20, 2013 at 2:00 PM, Vishvananda Ishaya <span dir="ltr"><<a href="mailto:vishvananda@gmail.com" target="_blank">vishvananda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div><div>On Jun 20, 2013, at 10:22 AM, Brant Knudson <<a href="mailto:blk@acm.org" target="_blank">blk@acm.org</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div><div><div>How about a mapping of JSON concepts to XML like:<br><br>collections:<br></div><object> <pair name="pair-name"> the-value </pair> ... </object><br>
</div><array> <element> the-value </element> ... </array><br><br></div><div>values:<br></div><string>text</string><br></div><true/><br></div><false/><br></div><null/><br>
</div><number>number</number><br><br></div>This type of mapping would remove any ambiguities. Ambiguities and complexity are problems I've seen with the XML-JSON mapping in Keystone. Plus the fact that it's so not-XML would convince users to switch to JSON. With a simple mapping, I don't think it would be necessary to test all the interfaces for both XML and JSON, just test the mapping code.<br>
</div></blockquote><div><br></div></div>+1 for something like this. JSON primary + autgenerated XML. I think the ideal version would be autogeneration of xml from jsonschema and some method for prettifying the xml representation via jsonschema tags. The jsonschema + tags approach is probably a bit further off (maybe for v4?), so having an auto conversion which is ugly but functional seems better than no XML support at all.</div>
<div><br></div><div>Vish</div></div></blockquote><div><br></div><div>Let's please not invent something new for this. We're building a high level platform. We shouldn't have to screw around with making so many low level frameworks to do things for which tools already exist. WSME will handle serialization, cleanly, in both XML and JSON already. Let's just use that.</div>
<div><br>Doug</div></div></div></div></blockquote><div><br></div></div>Doug,</div><div><br></div><div>Switching to WSME for v3 is out of scope at this point I think. Definitely worth considering for v4 though.</div><div>
<br></div><div>Vish</div></div></blockquote><div><br></div></div><div>Absolutely - we agreed about that weeks ago. I assumed, however, that decision meant we would just continue to use the existing serialization code. I thought this discussion was moving toward writing something new, and I wanted to head that off.</div>
<span><font color="#888888">
<div><br></div></font></span></div></div></div></blockquote><div><br></div><div>Don't worry we don't have time/resources to invent something new :-) <br><br>In the end given the amount of resources and time we have during Havana if we want XML support (which it looks like we will have to continue to support) we are going to have to decide to concentrate the test effort on primarily JSON or attempt to cover both JSON and XML, but obviously not be able to do it as well as just concentrating on one format.<br>
<br></div>Regards,<br><br></div><div class="gmail_quote">Chris<br></div></div></div>