Skip to content
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.

Descriptive vs. prescriptive document (Michael Cooper) #47

Closed
darthcav opened this issue Aug 25, 2014 · 1 comment
Closed

Descriptive vs. prescriptive document (Michael Cooper) #47

darthcav opened this issue Aug 25, 2014 · 1 comment

Comments

@darthcav
Copy link

Reference

http://lists.w3.org/Archives/Public/public-wai-ert-tools/2014Aug/0008

Original Comment

I'm having a hard time determining whether the document is meant to be descriptive or prescriptive - is it describing what eval tools are, as a background to another resource, or is it suggesting what eval tool developers should consider as they work on their tool? I think the doc has more value if it's prescriptive, so some things in it should be strengthened.

@darthcav
Copy link
Author

Resolution

No change - As a Working Group Note, this document is designed to be a descriptive document. The working group is not in the position to prescribe particular features or implementations. We will consider making this more clear, in particular in the earlier parts of the document.

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

No branches or pull requests

1 participant