- From: Robert Leif <rleif@rleif.com>
- Date: Wed, 12 Oct 2011 11:18:19 -0700
- To: "'Noah Mendelsohn'" <nrm@arcanedomain.com>, "'Henri Sivonen'" <hsivonen@iki.fi>
- Cc: <public-html-xml@w3.org>
Noah, Henri et al. I believe that the concern about the lack of interoperability between HTML5 and XML is of great significance. This should have been a major requirement for the development of HTML5. The inability to use XML elements in HTML5 will result in very significant costs. An HTML5-XML interface could be a very important part of the informatics backbone of Obama Care. The data entry for personal healthcare records would be simplified by the use of HTML5 forms that filled in the XML records. The creation of structured reports in Radiology and Pathology would simplified is one could directly use the XML data and the formatting via CSS that is available with HTML5. I am sure that this same situation holds for engineering documentation. I can see where it would be useful for the creation of education tools, scientific articles, and textbooks. In short, there is a great need to retrofit HTML5 to work with XML. Bob Leif -----Original Message----- From: public-html-xml-request@w3.org [mailto:public-html-xml-request@w3.org] On Behalf Of Noah Mendelsohn Sent: Wednesday, October 12, 2011 8:50 AM To: Henri Sivonen Cc: public-html-xml@w3.org Subject: Re: HTML/XML TF report introductory text On 10/12/2011 7:49 AM, Henri Sivonen wrote: > I think this list of specific concerns looks rather odd in the middle > of the intro. I'd rather not include this list in the intro and > instead say something generic about reusing HTML content in XML > content or with XML tooling or vice versa. I think that concern makes sense, especially regarding the form of the list. Still, I think is helpful to have a few specific "or instances" at that point in the introduction, to give a sense of why anyone would even consider going to significant trouble to change the specifications. Thank you. Noah
Received on Wednesday, 12 October 2011 18:18:48 UTC