- From: Erik Taubeneck via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 May 2022 19:58:47 +0000
- To: public-patcg@w3.org
@michaelkleber - I don't disagree with any of that. However, looking at the original conversation on #50, the impetus for this agenda item stems from @ekr's [comment](https://github.com/patcg/meetings/issues/50#issuecomment-1121095886): > We should spend at least one of the days of the next meeting on features and requirements and then trying to get an understanding of the capabilities of each design. It don't understand how we get from that to spending the entire hour on the optimization use case. I'm am in support of talking about the optimization use case, but I want to make sure that we also make progress on building some consensus on what the Working Group should be producing. > We don't want to wait until after we've painted ourselves into a corner to ask the question that helps us pick which corner we should paint towards. Yes on scoping down, but in a fully informed way. I agree with this sentiment, but wouldn't this be more in relation to a specific solution for a use case, rather than scoping the use case of the first standardization effort? Reporting generally seems like a prerequisite for the optimization use case, so I don't see the attempt to reach consensus on reporting as the first sub-use case to tackle as painting us into a corner. We could then use the next meeting (as well as Github) to try and reach consensus around the other important sub-use cases that should be in consideration of the standard. -- GitHub Notification of comment by eriktaubeneck Please view or discuss this issue at https://github.com/patcg/meetings/issues/51#issuecomment-1129263186 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 May 2022 19:58:48 UTC