{"action":"created","issue":{"url":"https://api.github.com/repos/validator/validator/issues/105","labels_url":"https://api.github.com/repos/validator/validator/issues/105/labels{/name}","comments_url":"https://api.github.com/repos/validator/validator/issues/105/comments","events_url":"https://api.github.com/repos/validator/validator/issues/105/events","html_url":"https://github.com/validator/validator/issues/105","id":88315445,"number":105,"title":"Achieve information parity in JSON API results with the W3 non-nu validator","user":{"login":"AMcBain","id":83529,"avatar_url":"https://avatars.githubusercontent.com/u/83529?v=3","gravatar_id":"","url":"https://api.github.com/users/AMcBain","html_url":"https://github.com/AMcBain","followers_url":"https://api.github.com/users/AMcBain/followers","following_url":"https://api.github.com/users/AMcBain/following{/other_user}","gists_url":"https://api.github.com/users/AMcBain/gists{/gist_id}","starred_url":"https://api.github.com/users/AMcBain/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AMcBain/subscriptions","organizations_url":"https://api.github.com/users/AMcBain/orgs","repos_url":"https://api.github.com/users/AMcBain/repos","events_url":"https://api.github.com/users/AMcBain/events{/privacy}","received_events_url":"https://api.github.com/users/AMcBain/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/validator/validator/labels/enhancement","name":"enhancement","color":"c7def8"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-06-15T04:51:52Z","updated_at":"2015-06-17T05:59:12Z","closed_at":null,"body":"I maintain the bot, Selvvir, for the #css IRC channel on Freenode. I've been using the existing (non-nu) validator interface to enable the bot to report on the results of validation for websites people explicitly ask the bot about.\r\n\r\nThat interface is now suggesting I use the nu interface to make my requests. However the nu interface is missing information present in the non-nu validator's JSON and SOAP 1.2 output.\r\n\r\nThe non-nu validator output:\r\nhttps://validator.w3.org/check?uri=google.com&output=json\r\nhttps://validator.w3.org/check?uri=google.com&output=soap12\r\n\r\nThe nu validator output:\r\nhttps://validator.w3.org/nu/?doc=http%3A%2F%2Fgoogle.com&out=json\r\n\r\nSpecially, the non-nu validator returns an explicit declaration of the content type (text/html, etc.) and encoding (utf-8, etc) of the document being validated. The SOAP response of the non-nu validator also returns the doctype. I believe this information is useful to display in my condensed output report.\r\n\r\nIt would be quite nice if the nu validator's output could be updated with a source block equivalent to the non-nu validator's JSON output including the content type, encoding, and doctype information."},"comment":{"url":"https://api.github.com/repos/validator/validator/issues/comments/112664234","html_url":"https://github.com/validator/validator/issues/105#issuecomment-112664234","issue_url":"https://api.github.com/repos/validator/validator/issues/105","id":112664234,"user":{"login":"AMcBain","id":83529,"avatar_url":"https://avatars.githubusercontent.com/u/83529?v=3","gravatar_id":"","url":"https://api.github.com/users/AMcBain","html_url":"https://github.com/AMcBain","followers_url":"https://api.github.com/users/AMcBain/followers","following_url":"https://api.github.com/users/AMcBain/following{/other_user}","gists_url":"https://api.github.com/users/AMcBain/gists{/gist_id}","starred_url":"https://api.github.com/users/AMcBain/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AMcBain/subscriptions","organizations_url":"https://api.github.com/users/AMcBain/orgs","repos_url":"https://api.github.com/users/AMcBain/repos","events_url":"https://api.github.com/users/AMcBain/events{/privacy}","received_events_url":"https://api.github.com/users/AMcBain/received_events","type":"User","site_admin":false},"created_at":"2015-06-17T05:59:12Z","updated_at":"2015-06-17T05:59:12Z","body":"In our case if someone is having issues and feed it to the bot to get back validation results, we can easily point to things like a missing or old doctype. Things that might cause quirksmode or other odd things. Encoding is similarly nice because if things aren't showing up right it's an easy pointer to say \"well, it's not [UTF-8]. That's your problem.\"\r\n\r\nThe people who join #css run the gamut from those who are pretty good and just got stuck on something complex (or had a brain fart and missed something obvious) to people who don't have the slightest about much of anything or even appear to have picked up web development yesterday. So to help us to help them, I think those two things would make a nicer condensed output.\r\n\r\nAs to content type, I can't defend that. :) If you know of a use, great. Otherwise I don't have one at the moment.\r\n\r\nThe old bot I replaced had the output \"« [truncated version of input URL] » markup • errors: [number of errors] • warnings: [number of warnings] • doctype: [doctype] • charset: [charset] • validation result: [shortened URL to the validator page with the full results]\"\r\n\r\nSince I didn't want to parse SOAP output to get the doctype, the current bot outputs \"« %s » markup • errors: %s • warnings: %s • charset: %s • validation result: %s\". The %s values are the same, I am just missing the doctype."}}