[whatwg] DOM3 Load and Save for simple parsing/serialization?

Brett Zamir brettz9 at yahoo.com
Wed May 20 01:55:41 PDT 2009

Brett Zamir wrote:
> Brett Zamir wrote:
>> Jonas Sicking wrote:
>>> On Wed, May 20, 2009 at 12:49 AM, Maciej Stachowiak<mjs at apple.com>  wrote:
>>>> On May 19, 2009, at 11:49 PM, Jonas Sicking wrote:
>>>>> On Mon, May 18, 2009 at 5:45 AM, Brett Zamir<brettz9 at yahoo.com>  wrote:
>>>>>> Has any thought been given to standardizing on at least a part of DOM
>>>>>> Level
>>>>>> 3 Load and Save in HTML5?
>>>>> The Load and Save APIs in DOM 3 are much too complicated IMHO so I'd
>>>>> like to see something simpler standardized.
>>>>> We've had parsing and serializing APIs in Firefox for ages. Would be
>>>>> very exited to see someone put in effort to get their API cleaned up
>>>>> and standardized.
>>>>> https://developer.mozilla.org/En/DOMParser
>>>>> https://developer.mozilla.org/En/XMLSerializer
>>>> WebKit actually implements most of these. I think it would make sense to
>>>> publish these as a WebApps spec. But these classes don't do any loading or
>>>> saving, just parsing and serializing.
>>> Doesn't XMLHttpRequest do all the load/save that is needed? I don't
>>> know how would could standardize save beyond that without relying on
>>> something like WebDAV.
>>>> Document.load would be the simplified
>>>> load/save method that it would make sense to standardize IMO, since Firefox
>>>> has it and it is needed for Web compatibility. I am concerned though that
>>>> Document.load() allows for synchronous network loads.
>>> I'm certainly no fan of Document.load() and wish it would go away. In
>>> fact we have decided not to add any additional features such as CORS
>>> or progress event support in order to discourage its use and move
>>> people to XHR instead.
>>> / Jonas
>> Does Ajax at least have theoretical support for loading entities from 
>> an external DTD, as I presume a DOM method must? (Would be nice to 
>> hear from some others on that separate "External document subset 
>> support" thread too, especially to know whether all the browsers are 
>> just not inclined to ever implement this (despite all of the off-web 
>> documents that use them...))
> Sorry, guess I can answer the first part of my question, yes it is 
> theoretically possible... Per 
> http://www.w3.org/TR/XMLHttpRequest/#responsexml , "Return the XML 
> response entity body." -> "Parse the response entity body into a 
> document tree following the rules from the XML specifications."
> But I'm still holding out hope that the ability to at least parse an 
> external DTD for entities alone would be considered...

Argh... Didn't read far enough... "resources referenced will not be 
loaded"... So now I'm having to hold out hope on both counts...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090520/4b758524/attachment-0002.htm>

More information about the whatwg mailing list