w3c / specberus Goto Github PK

View Code? Open in Web Editor NEW

67.0 30.0 43.0 7.54 MB

Checker used at W3C to validate the compliance of Technical Reports with publication rules

Home Page: https://www.w3.org/pubrules/

License: MIT License

JavaScript 14.68% HTML 83.80% CSS 0.15% Handlebars 1.37% Shell 0.01%

specberus's People

Contributors

Stargazers

Watchers

specberus's Issues

Include checking for new publication process

Need better detection for end of LC date

Existing checker properly detects http://www.w3.org/TR/2013/WD-html-longdesc-20130716/, but we don't.

Rule "The document's title MUST be in the title element and in an h1 element. "

Is it implemented?

CSS & HTML validation errors & warnings

I'm not getting the same error reports for CSS using the CSS Validator and .jit.su tools. See for example http://www.w3.org/TR/2014/WD-charmod-norm-20140715/ (no errors in jit.su but plenty at http://jigsaw.w3.org/css-validator/validator?profile=css21&warning=0&uri=http%3A%2F%2Fwww.w3.org%2FTR%2F2014%2FWD-charmod-norm-20140715%2FOverview.html

Btw, it would be good to make it clearer for CSS & HTML validation results which are warnings and which are errors. For any CSS warnings (and maybe html too) it might be good to have just "18 warnings" and then click on that to show the details, rather than show all immediately.

Expose as HTTP API

translation paragraph is not found in certain documents

check http://www.w3.org/TR/2014/REC-html5-20141028/

Rule "recursive All normative representations MUST validate as one of the following: HTML 4.x, or some version of XHTML or XHTML+RDFa that is a W3C Recommendation. HTML5 is also permitted with the following limitations: Inline markup for SVG 1.1 or MathML 2.0 is permitted but only with a (fallback) alternative. If the HTML5 validator issues content warnings, the publication request must include rationale why the warning is not problematic. Note: Please consider how your content will render in browsers that do not support HTML5. "

Is it implemented?

Rule "The document MUST include a link to the W3C logo identified below. The URI used to identify the logo MUST be absolute. Include this source code:<a href="http://www.w3.org/"><img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/></a> "

Is it implemented?

Put options in URL (using History API)

PR|PER|REC must include link to implementation report (or indication it was skipped)

Team-Subm must include the name of a mailing list for comments

Recursive validation on large multipart documents makes the app crash

Rule "At least one normative representation MUST be available for requests that use the "This Version" URI. More than one normative representation MAY be delivered in response to such requests. A "This Version" URI MUST NOT be used to identify a non-normative representation. "

Is it implemented?

Error and warning <ul>s ought to be labelled

Right now they are distinguished solely by colour, which is unhelpful.

No support for 2002 CPP

Is this needed?

CR must include link to preliminary implementation report

If we had standardised dl links for this, we could check.

Use h2 date to check copyright year, instead of current year

Rule "recursive Any internal style sheets MUST be cascaded before this link; i.e., the internal style sheets MUST NOT override the W3C tech report styles. "

Is it implemented?

markup validation should work with HTML4 and XHTML documents

REC when previous Rec, must indicate if it replaces/obsoletes/subsumes/edits and must link to previous Rec

Rule "recursive Each document MUST include the following absolute URI to identify a style sheet for this maturity level: http://www.w3.org/StyleSheets/TR/W3C-WD Include this source code: <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD"/> "

Is it implemented?

Write command-line client

CR must identify features at risk

Auto detect profile from URL

PR|PER must provide information to Advisory Committee Representatives about how to send their review comments

Support compound documents

SVG CSS properties are flagged as not existing

When pubrules-checking a document with inline SVG diagrams that use CSS (such as the CSS Media Queries or Syntax specs), all of the SVG-specific CSS properties are flagged as not existing. The checker should know about these properties.

headers/hr should check that there isn't an hr both at the end of div.head and right after it

Track whacko for better support for next/nextAll/prev/prevAll so that we can remove lots of nasty hacks

IPP exception

Leave room for IPP exceptions (ie: when the disclosure page is not following the usual pattern, example: TAG).

0

Is it implemented?

Offer help descriptions for all rules and all errors

There should be an affordance to show more information on both rules and errors/warnings.

Make rule checking more parallelised, notably for network IO

PR|PER must include the end date of the review period

add some checks for input url safety

see https://github.com/w3c/safe-url-input-checker

Extract information to know which group is producing the spec

Set up Gremlins testing

https://github.com/marmelab/gremlins.js

Improve detection of preliminary implementation/interoperability reports?

Evaluate @darobin's ideas about this: is it possible/acceptable to find links to preliminary implementation/interoperability reports (or a mention that such report doesn't exist) within the <dl> section at the top of the page?

Remove throttling in production

We should make sure the production server is whitelisted and throttling is disabled there.

Reset data model and output when checking a second spec

When checking twice without reloading the page, errors and warnings add up to the previous' check output.
All the messages, counters for errors and warnings, the summary of results, etc. — all should be reset before re-running.

Rule "At least one normative representation MUST be available for requests that use the "This Version" URI. More than one normative representation MAY be delivered in response to such requests. A "This Version" URI MUST NOT be used to identify a non-normative representation. "

Is it implemented?

Check against inconsistency when previous version URI ≠ redirected latest version URI.
This version URI ≠ previous version URI.

About the first one:

OK when Previous Version of the document to be published == the document behind the Latest Version
FAILURE otherwise.

Edge cases:

Once the document is published, this rule cannot return OK anymore.
PER: after publication, the Latest Version must not change (point to the REC rather than the published PER).

Hopefully I will come up with a PR someday, but I want to agree on a decision before anyway.

About no. 2:

Echidna has published (wrongly) already a spec with this version URI = previous version URI.

supersedable text is not found in certain document

check http://www.w3.org/TR/2014/REC-html5-20141028/

Rule "The front matter MUST appear at the beginning of the body of the document, within <div class="head">. There is one exception to that requirement: the hr element after the copyright MAY appear inside or after the div element. Editors SHOULD NOT include other information in this section. "

Is it implemented?

w3c / specberus Goto Github PK

specberus's People

Contributors

Stargazers

Watchers

Forkers

specberus's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs