That's sort of correct. However, the w3c validator ignores xmlns
attribute declarations - thereby avoiding the issue. It is ALSO
possible to declare the additional ATTLIST values in your internal
subset, should you actually care.
Johannes Koch wrote:
Ben,
Ben Adida schrieb:
Since we use the word "SHOULD" with respect to DTDs, we believe this
leaves enough wiggle room for document authors to stop using DTDs
once a schema-based W3C-endorsed validator becomes available. We're
all in strong favor of schema-based validation, but until
validator.w3.org supports it (which depends on another REC-track
document), we can't leave our users without a complete validation story.
one problem with DTD validation here is that somewhere you have to
declare prefix mappings used in CURIEs throughout the document. But
the XHTML DTD for RDFa doesn't support additional xmlns "attributes"
without changing ATTLIST declarations.
So a document starting with
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";
xmlns:dbp="http://dbpedia.org/property/"; xml:lang="en">
will not be DTD valid.
--
Shane P. McCarron Phone: +1 763 786-8160 x120
Managing Director Fax: +1 763 786-8180
ApTest Minnesota Inet: [EMAIL PROTECTED]
