W3C home > Mailing lists > Public > www-validator-cvs@w3.org > July 2013

[Bug 22741] validator.w3.org does not give an option to validate HTML+RDFa

From: <bugzilla@jessica.w3.org>
Date: Sun, 21 Jul 2013 16:18:59 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-22741-169-Y3P5JYhEoX@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22741

Gregg Kellogg <gregg@kellogg-assoc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gregg@kellogg-assoc.com

--- Comment #3 from Gregg Kellogg <gregg@kellogg-assoc.com> ---
It's true that much of the ReSpec output could be rewritten in plain RDFa Lite,
but not the critical ordering of authors and editors; this requires using the
@inlist attribute.

It seems rather arbitrary to naturally validate RDFa 1.1 Lite, and call other
RDFa content invalid. This perpetuates the notion that one is "better" than the
other, which just isn't the case. Ideally, when seeing an RDFa 1.1 attribute,
or combination of attributes, the validator could automatically switch to 1.1
mode, or at least signal that the content might be valid RDFa 1.1 and make it
easy to redirect to the proper validator mode.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 21 July 2013 16:19:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:55 UTC