- From: David Lee <David.Lee@marklogic.com>
- Date: Thu, 26 Jul 2012 05:50:26 -0700
- To: Michael Sokolov <sokolov@falutin.net>, Dave Pawson <dave.pawson@gmail.com>
- CC: David Carlisle <davidc@nag.co.uk>, "public-microxml@w3.org" <public-microxml@w3.org>
> the iPhone app developer who is choosing a preference file format: XML > may not be suitable for use in a memory-constrained environment if it > requires loading a large library to parse and/or build an object model, > but a smaller lightweight one could open up this arena perhaps. > > -Mike Side note <personal Rant> the iPhone OS comes with a full XML parser and not a JSON parser (for running in Objective C) You need to add a JSON library to use JSON (in OC). Yet a large number of iPhone developers choose to use JSON instead (in OC). Dont ask me why ... I doubt a MicroXML parser would convert them. <another example> At one point (possibly still true) the Android OS came with both a JSON and XML parser in the native code. At one point (possibly still true) the XML parser was about 5x faster than the JSON parser. This is a single point exemplifying that smaller specs dont necessarily produce faster parsers. <end rant> SO point well taken, perhaps on some future devices a micro xml parser might make a good substitute. This technique is commonly done even without a specification on embedded and older mobile device OS's. ( e.g. http://www.calldei.com/pubs/XML2006/index.html ) In fact many an argument has been fought (but no winners) why a simplified spec is actually bad because different use cases benefit from different subsets so can be optimized for just what they want. ----------------------------------------------------------------------------- David Lee Lead Engineer MarkLogic Corporation dlee@marklogic.com Phone: +1 650-287-2531 Cell: +1 812-630-7622 www.marklogic.com This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of this e-mail communication by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender and delete all copies. Thank you for your cooperation.
Received on Thursday, 26 July 2012 12:50:55 UTC