- From: <bugzilla@jessica.w3.org>
- Date: Mon, 25 Mar 2013 06:15:08 +0000
- To: www-validator-cvs@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21383 --- Comment #1 from Art McBain <mcbain.asm@gmail.com> --- is the detected doctype or that forced* Also, the JSON output for validator.nu in a roundabout way it does provide the "schema" it used to validate a document. http://validator.nu/?doc=http%3A%2F%2Fwww.iana.org%2Fdomains%2Fexample&out=json Produces the following: {"url":"http://www.iana.org/domains/example","messages":[{"type":"info","message":"The Content-Type was “text/htmlâ€. Using the HTML parser."},{"type":"info","message":"Using the schema for HTML5 + SVG 1.1 + MathML 3.0 + RDFa Lite 1.1."}]} Which indicates what it validated against in the last message. Though I much prefer the shorter more programmatic output of the W3's SOAP 1.2 doctype tag. Earlier I had indicated the format was intended to match validator.nu's (which I found at http://validator.w3.org/docs/users.html ), but it seems this only applies to the existence of the "url" and "message" properties and the format of messages listed in the latter. Thus the doctype used for validation could be included in the extra source block, or as a property of the root (like "url") without harming this compatibility. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 25 March 2013 06:15:09 UTC