So I am trying to understand Peter Sefton’s mind toward Microsoft Word and how he has used tables for semantic markup. I am not being coy or am secretly carrying multiple meanings. In fact, I appreciate Peter’s reference to me, by name, in his recent Blog entry “More on Microsoft Word vs XML Schemas.”
The picture floating at left shows the XML Structure Task Pane. The hope here is that Peter Sefton will see almost instantly that most of the elements listed are semantic elements that cannot be expressed in WordProcessingML. Now, the screenshot below shows this Blog entry being composed in Microsoft Word.

I am almost sure that I am misunderstanding Dr. Sefton. But the assumption here is that he might have used tables where all of the magenta XML elements appear in this entry. Moreover, I would like to know what he thinks of the XML Structure Task Pane. I will make an effort to search his Blog for any remarks about it.
Now when I am ready to post my entry into WordPress, without any help from Google™ I run my “beta” version of CleanXHTML that produces output like the stuff shown below:

I see Dr. Sefton as a potential customer of this product and would like to know what the hell is so wrong with it. His detailed input into this matter is more than academic. I consider it invaluable.
This entry was posted on Wednesday, August 24th, 2005 at 11:44 am and is filed under .NET related, Data Management Solutions, Word, root. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
[...] My work on CleanXHTML is justified (again) as big-ass Google releases Blogger for Word. What I would like to do is have CleanXHTML connect to a Web service on the fly like InfoPath does to take it beyond the Clipboard stuff shown earlier. [...]
[...] CleanXHTML Test. Every Blog entry tests CleanXHTML output as shown here. Recent entries refined the XSLT-parameter-based configuration options. [...]
[...] My captive hope is that Blogger for Word will create the expectation that the Word Processor needs this “remote publishing” capability—so a more generic solution will evolve from this tool. The Word Processor needs to “discover” remote entry points and save them in the document metadata. These entry points are the publishing locations for that document. InfoPath already has a similar concept it calls “Submit Options” or “Data Connections.” As of now, my work allows me to use Copy and Paste… [...]
[...] In August of 2005 you would find me in agony over the distance I knew had to travel to get where I am today. Back then I was interacting with Peter Sefton about Microsoft Word and XHTML. I wanted so badly to point Dr. Sefton to a location on the Web where he could download actual bits that realize my vision. [...]