Add Audience section #25
Conversation
Closes w3ctag#13
| * **User agent developers** who want to align implementations with design and privacy principles that prioritize their users. | ||
| * **Regulators and policymakers** who need criteria to assess whether user agents fulfill their duties to users. | ||
| * **Technical authors** who want to reuse or reference these concepts in their own specifications or documentation. |
There was a problem hiding this comment.
I think the last sentence is overstepping:
| * **User agent developers** who want to align implementations with design and privacy principles that prioritize their users. | |
| * **Regulators and policymakers** who need criteria to assess whether user agents fulfill their duties to users. | |
| * **Technical authors** who want to reuse or reference these concepts in their own specifications or documentation. | |
| * **Spec writers**, who need to normatively or informatively reference the concept herein in their own specifications or documentation. | |
| * **User agent developers**, who want to align implementations with design and privacy principles as described in the manner described in this document. | |
| * **Regulators and policymakers**, who need understand what constitutes a user agent. |
There was a problem hiding this comment.
"Technical authors" is intentional. It covers both spec writers as well as anyone generally contributing to specification development. But it also includes anyone that is writing a document (not necessarily a "spec") that needs to refer to these concepts.
| * **User agent developers** who want to align implementations with design and privacy principles that prioritize their users. | ||
| * **Regulators and policymakers** who need criteria to assess whether user agents fulfill their duties to users. | ||
| * **Technical authors** who want to reuse or reference these concepts in their own specifications or documentation. | ||
|
|
There was a problem hiding this comment.
| * **Web developers**, who need to understand why certain choices are made in standardizing technology (particularly as to why certain features prioritize user privacy, security, over developer need). |
There was a problem hiding this comment.
I also think Web Developers are third on this list. There are orders of magnitude more web developers reading specs than regulators (and there are lots more web developers than regulators).
There was a problem hiding this comment.
But those web developers are not implementing or using the concepts in this document. Regulators/policymakers on the other hand get a canonical reference to what constitutes a user agent.
Anyone in theory can read this document but I don't think we are writing it in a way that web (platform) developers can have direct use. At least that's my understanding of what's expected here thus far.
Closes #13
Adding this section after the Abstract because it doesn't fit elsewhere at the moment. If we introduce an Introduction section, the contents of this section can be moved there.
Preview | Diff