- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Tue, 29 Jan 2013 08:49:16 -0500
- To: www-tag@w3.org
- Message-ID: <5107D35C.9070501@openlinksw.com>
On 1/29/13 8:40 AM, John Kemp wrote: > On 01/29/2013 08:03 AM, Kingsley Idehen wrote: >> FWIW -- We've already been through the hell I am trying to prevent >> others from embarking upon. We have more than a 100+ transformers for a >> variety of XML based data sources (including XHTML, XHTML, HTML5) and I >> know that what we've been through isn't something others will embark >> upon. >> >> My fundamental concern: most (X)HTML5 is published without appropriate >> hints to processors. Thus, you have to sniff on the content. >> >> If you haven't attempted to extract a Microdata, RDFa, Microformats data >> island from an (X)HTML5 document you won't be aware of these problems >> out in the field. In addition, beyond schema.org, most online retailers >> (as a consequence of Schema.org) are producing the kind of problematic >> (X)HTML5 that I describe. >> > > It sounds like you are exactly aware of the problem then. People try > to do something they want to do, and they all do it in different ways. > A consumer is unable to know, reliably, what to do with this data, > since the problem you mention is completely undocumented without a > "polyglot specification". > > Is your advice "don't do this"? If so, what would you have them do > instead? If your advice is "do it this way", where is the > specification that shows this way? > > JohnK > > > In an ideal world, it would simply be a case of (X)HTML5 enforcing the DOCTYPE and xml namespace requirements. In the real world, we already know -- as exemplified by schema.org -- that it won't happen. I believe XHTML5 and HTML5 should have distinct content-types, which they are. Thus, if anyone seeks to publish polyglot (X)HTML5 they MUST adhere to the specs re. DOCTYPE and xml related namespace declarations. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Tuesday, 29 January 2013 13:49:39 UTC