Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve detection of preliminary implementation/interoperability reports? #39

Open
tripu opened this issue Oct 3, 2014 · 2 comments
Open
Assignees

Comments

@tripu
Copy link
Member

tripu commented Oct 3, 2014

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?

@tripu tripu self-assigned this Oct 3, 2014
@tripu tripu added this to the post-tpac milestone Oct 3, 2014
@dontcallmedom dontcallmedom modified the milestones: Specberus ready to replace existing pubrules checker, Parity in automatic checks Nov 21, 2014
@deniak deniak added the v1.5 label Dec 18, 2014
@tripu
Copy link
Member Author

tripu commented May 14, 2015

This wouldn't be difficult to change. But iiuc, pubrules don't expect or even mention info about interoperability/implementation reports in the <dl> section of specs. eg, for recommendations, it expects those pieces of information in the SOTD section.

There are recommendations with that info there. But having that sometimes as an unofficial addition doesn't mean we should enforce it in Specberus, does it?

We can look for that in the <dl> section instead, but I think that is not what pubrules says.

Reassigning to @plehegar for clarification.

@tripu tripu assigned plehegar and unassigned tripu May 14, 2015
@deniak
Copy link
Member

deniak commented Sep 14, 2015

@plh is there any chance we can ask editors to use a specific id for these?
Another option would be to use a data- attribute but that would mean asking people to switch their documents to HTML5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants