Re: [w3c/charter-html] WebPlat charter: Focus on user research (#146)

> How can you write a specification without a clear understanding of all the possible use cases?

one solves for a limited set of problems. 

> You need to be able to say something like "As a web developer, I want to be able to directly read the clipboard of a user on my site, in order to..."

Right. Or, "users/developers are solving problem X with hack/heavy-weight/largely-used-solution Y. We should standardize that!"  

> Or, "As a visitor to a website, I want to know when a website tries to access my clipboard and grant or deny permission, so that I can be secure."

Or, "As a user, I just want to copy stuff! Get the hell out of my way, stupid browser.".

> Ideally, every use case should be backed up by research. 

Depends on your definition of "research" - but largely, agree. 

> Even if they're not, every part of the spec should clearly say how it addresses a use case.

Sometimes, yes... at least, it should point to some use cases and it should be obvious how those use cases are solved. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/charter-html/issues/146#issuecomment-319569365