- From: Martin Thomson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jun 2022 07:18:31 +0000
- To: public-patcg@w3.org
@timcowen, I understand the desire to be precise here, but I don't think that we need to be too careful here. Any decision we make about whether something is in-charter or out is going to be made on the basis of consensus. If you want to equate "personal information" to the GDPR "personal data" (i.e., data about a person), that is entirely reasonable; that's approximately what I do. We each come to this work with a different understanding of the constraints on the problem and that is part of what makes the process valuable. A little ambiguity on the edges is fine. That gives us a tiny bit of flexibility to discuss things within that ambiguity. My experience with charters is that while there is sometimes an issue that leads to a lengthy discussion over the meaning of words and the intent of those who drafted and agreed to the text, those are rare. More often, the text in a charter is pointed to and that curtails discussion on a topic because there is no disagreement that the topic is out of scope. Those cases where disagreements over scope occur are rough, I can't pretend otherwise. I will observe that this is frequently because our understanding of the problem space evolves and the assumptions made at chartering time are no longer a good fit for everyone. Often the group has not yet developed a solid understanding of the subject matter and that can mean that the charter is not always perfect. However, we cannot insist on perfection or we'd never get anything done. No doubt, over time, we'll come to understand our scope better and we might be able to refine the charter using what we learn. Those disagreements might be difficult if they arise, but if they are, that might be for a good reason. -- GitHub Notification of comment by martinthomson Please view or discuss this issue at https://github.com/patcg/patwg-charter/issues/31#issuecomment-1170857845 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 June 2022 07:18:33 UTC