Re: Validator SOAP output

Hi Jens,

Jens Oliver Meiert <jens@meiert.com>, 2018-07-12 20:48 +0200:
> Archived-At: <https://www.w3.org/mid/CAJ0g8QSU=Yg8hxng2wBmudde7jxSUXkx9VUMq+ui3oY0ZXTyGA@mail.gmail.com>
> 
> Hi validator team—
> 
> if I’m not overlooking something then for a few weeks by now, the SOAP
> interface formerly available at
> https://validator.w3.org/check?uri=http://example.com/&charset=%28detect+automatically%29&output=soap12
> is gone. Do you know more, is this by accident, intended,—and could
> you bring it back?

It’s intentional if you give the legacy markup validator a document that
has a non-obsolete doctype — because in that case the document is just
handed off to the current HTML checker at https://validator.w3.org/nu/. And
the backend of https://validator.w3.org/nu/ very intentionally doesn’t
support that legacy SOAP API/format of the old validator.

Instead, the HTML Checker has its own HTTP interface/API, as documented at
https://github.com/validator/validator/wiki/Service-%C2%BB-HTTP-interface, and
as documented at https://github.com/validator/validator/wiki/Output-%C2%BB-XML,
it has its own XML output format — and even better it has a JSON output format,
documented at https://github.com/validator/validator/wiki/Output-%C2%BB-JSON

If you still want to use the legacy markup validator’s obsolete and no-
longer-maintained SOAP interface, you can by manually forcing it to check
against an obsolete HTML version; e.g.:

https://validator.w3.org/check?uri=http%3A%2F%2Fexample.com&doctype=XHTML+1.0+Strict&output=soap12

But if you want to check documents against the current HTML spec requirements,
then you need to use the current HTML checker at https://validator.w3.org/nu/
and the actively-maintained API that it provides.

  –Mike

-- 
Michael[tm] Smith https://people.w3.org/mike