- From: Adam <adamsobieski@hotmail.com>
- Date: Wed, 12 Feb 2014 20:30:18 +0000
- To: "public-htmail@w3.org" <public-htmail@w3.org>
- Message-ID: <SNT405-EAS15760B9BEB386C7CCEDD3F3C5920@phx.gbl>
Joshua Cranmer, Thanks for your points of view. XHTML is a superset of HTML, and facilitates XML-based processing (http://wiki.whatwg.org/wiki/HTML_vs._XHTML). ​ Many content management systems, e.g. Drupal, Joomla and Wordpress, utilize PHP and PHP has functionality for processing message header fields, multiple parts, and XML-based content. The processing cost difference between email header fields and XHTML content processing exists only for systems where the content would not be processed otherwise and scales per the number of messages. The indexing, search and retrieval of email messages is an example of a scenario where the contents of emails would already be processed by systems. Numerous new features’ functionalities require user interfaces on email authoring software and the processing on website systems and standardization can facilitate interoperability between the software. Solutions could utilize email header fields, content for parts of multipart messages, for example RDF and RFC2392 (https://www.ietf.org/rfc/rfc2392.txt), or data objects and metadata in the XHTML content. Utilizing data objects and metadata in the XHTML facilitates portability of messages and data across protocols and formats, such as NNTP (http://www.ietf.org/mail-archive/web/p2prg/current/msg01756.html , http://www.ietf.org/mail-archive/web/p2prg/current/msg01759.html) and web syndication. Kind regards, Adam Sobieski
Received on Wednesday, 12 February 2014 23:20:22 UTC