<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Dear Gary Bloom,<div class=""><br class=""></div><div class="">you are the CEO of MarkLogic, and you are in cc of this message to those two esteemed XML-related mailing lists: xquery-talk and xml-dev.</div><div class=""><br class=""></div><div class="">To be honest, given the marketing screaming that Marklogic did recently about your JSON support (geez, must have been expensive !!!), plus my messages</div><div class="">on those esteemed mailing lists, plus the amount of time and efforts that me and my Zorba team put into designing JSONiq (3 years)</div><div class=""><br class=""></div><div class=""><a href="http://www.jsoniq.org" class="">http://www.jsoniq.org</a></div><div class="">……...</div><div class=""><br class=""></div><div class="">…...I was obviously slightly disappointed to see that nobody from MarkLogic had the intellectual honesty to give ME (and the others on the mailing lists)</div><div class=""> one of the possible answers about MarkLogic’s JSON support:</div><div class=""><br class=""></div><div class="">(a) yes, we, MarkLogic, we inspired ourselves and adapt as much as we could from JSONiq, but we had no balls to admit it, and give proper scientific references to JSONiq</div><div class=""><br class=""></div><div class="">(b) no, we. MarkLogic, we designed everything from scratch without looking at JSONiq (but then, I would ask… Why !?….just curious...)</div><div class=""><br class=""></div><div class="">(c) yes, the language we, MarkLogic, support is exactly the same language as JSONiq, but again, we lack the balls to admit it in front of the wholeXML/JSON industry.</div><div class=""><br class=""></div><div class="">or any other such variation of such answer….. pick your choice.</div><div class=""><br class=""></div><div class="">=============</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">I am asking you personally, Gary Bloom, CEO of MarkLogic, which one it is !?</div><div class=""><br class=""></div><div class="">Do you have any idea !?</div><div class=""><br class=""></div><div class="">No shame in stealing, Gary. After all, you come from Oracle, and Oracle was built on Ellison stealing IBM’s research, and Larry Ellison just bought an island….</div><div class="">while IBM isn’t doing great…..</div><div class=""><br class=""></div><div class="">… so I wouldn’t blame you if your plan is the same (small detail, I don’t have the kindness of character that Don Chamberlin from IBM had…just keep this in mind</div><div class="">for your future plans, though…..)</div><div class=""><br class=""></div><div class="">=============</div><div class=""><br class=""></div><div class="">Looking forward to your answer, Gary Bloom.</div><div class=""><br class=""></div><div class="">And in the meantime, yes, I admit, I was lazy. I could have gotten my own answer to that question about the technical differences between MarkLogic support of JSON</div><div class="">and JSONiq (except that was looking forward to some intellectual honesty from MarkLogic, in vain, alas)</div><div class=""><br class=""></div><div class="">I will do my own own investigation about the technical differences between the two, and write a report.</div><div class=""><br class=""></div><div class="">Thanks for your (very telling, I am afraid….) silence.</div><div class=""><br class=""></div><div class="">MarkLogic has no scientific strength, nor political and economical “balls" (and sorry, I am afraid that’s a technical term).</div><div class=""><br class=""></div><div class="">Best regards</div><div class="">Dana</div><div class=""><br class=""></div><div class="">P.S,. I’ll teach you a very useful Romanian saying : “If you want to kill a cat, you can always say she has rabies”. </div><div class="">Yep, tell anyone you want that I have rabies :-))))))</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 28, 2015, at 10:15 AM, daniela florescu <<a href="mailto:dflorescu@me.com" class="">dflorescu@me.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Dear Kurt (Cagle) <div class=""><br class=""></div><div class="">on linkedin to the same answer bellow you answered me:</div><div class=""><br class=""></div><div class=""><span style="color: rgb(51, 51, 51); font-family: Helvetica, Arial, sans-serif; font-size: 16px; line-height: 18px; background-color: rgb(255, 255, 255);" class="">"As I said, first glance says it's close, but I'm not completely up to date on the JSONIQ spec. I know when I talked to a key developer of mutual acquaintance, he indicated that he followed JSONIQ, but that was still while it was under development."</span></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Kurt, do you have now a better idea about the technical differences between the two JSOn query languages: JSONiq designed and supported by Zorba</div><div class="">and the one supported by MarkLogic ? </div><div class=""><br class=""></div><div class="">Or does someone else ?</div><div class=""><br class=""></div><div class="">What is the technical rationale for making the two languages different ? Any strong technical reasons ?</div><div class=""><br class=""></div><div class="">If there are no strong technical reasons, and the two are different just for the sake of being different, that's very sad. </div><div class=""><br class=""></div><div class="">Relational databases survived for 30 years because those guys were brilliant business people and </div><div class=""> understood the power of a standard/common language and common APIs for all vendors.</div><div class=""><br class=""></div><div class="">It strengthens the (entire) community to the point that, even 30 years later, it is almost impossible to get SQL out of their hands....</div><div class=""><br class=""></div><div class="">It's very unfortunate that the NoSQL community, and especially MarkLogic who considers themselves the "leaders" in this market,</div><div class="">don't get that simple fact....and they had to twist JSONiq here and there in order to avoid admitting they use the language designed by the</div><div class="">Zorba community and avoid calling it JSONiq....</div><div class=""><br class=""></div><div class="">Such a lack of vision is sad.</div><div class=""><br class=""></div><div class=""> But I digress.</div><div class=""><br class=""></div><div class="">I am still curious if someone compiled a list of technical differences.</div><div class=""><br class=""></div><div class="">Thanks, best regards</div><div class="">Dana</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Apr 23, 2015, at 5:24 PM, daniela florescu <<a href="mailto:dflorescu@me.com" class="">dflorescu@me.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">I heard that MarkLogic will be using JSONiq for processing JSON.<br class=""><a href="http://www.jsoniq.org/" class="">http://www.jsoniq.org</a><br class=""><br class="">Sounds like wonderful news to me.<br class=""><br class="">Hope it’s true.<br class=""><br class="">Best<br class="">Dana<br class=""><br class=""><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class=""><a href="mailto:talk@x-query.com" class="">talk@x-query.com</a><br class="">http://x-query.com/mailman/listinfo/talk</div></blockquote></div><br class=""></div></body></html>