- From: B. Smedberg <bsmedberg@covad.net>
- Date: 08 Sep 2003 18:22:12 -0400
- To: www-dom@w3.org
Well, I'm afraid that I may be too late to alter DOM Load and Save, because I just discovered the issues, but I would like to raise two issues. 1) DOM Load supports sync/async loading, but DOM Save does not. I don't see why an async DOM Save to URI (http PUT or FTP upload, for example) should not be supported. 2) a simple extension to the DOM Load and Save interfaces would make the interface compatible with serializing non-XML formats. Of course, the XML format would be the only "required" format per the spec, but others could be supported by particular implementations. For example, mozilla contains a serializer that formats a DOM into a plain text representation (for multi-part emails, and "save as Text"). In addition, it contains an HTML serializer. I think the DOMImplementationLS interface could be modified with a single "contentType" parameter: DOMParser createDOMParser(in DOMSTring contentType, in unsigned short mode, in DOMString schemaType) raises(DOMException); DOMSerializer createDOMSerializer(contentType); The default content-type "text/xml" would be required... other content-types, such as "text/plain" or "text/html" would be optional implementation extensions. --BDS
Received on Monday, 8 September 2003 18:22:12 UTC