Closed anssiko closed 1 year ago
Related TAG discussion: https://github.com/w3ctag/tag.w3.org/issues/22
Further work on top of this would be to expand this note with a (brief) explanation on what differentiates this proposal from the past efforts that did not gain traction. The spec editors are in the best position to do so.
Oh, I found this (in the README): https://github.com/w3c/contact-picker/pull/31/
I wonder if we should just migrate that over from the README?
Updated to explain what differentiates this proposal from the past.
I think the community just generally got better at designing these things, even if those APIs didn't get any look at when this new API was designed.
Kind of, all of the previous attempts were designed with full & perpetual access (gated by a permission) in mind, which is far from ideal, and contact edit access, which is not a use-case we found any legitimate interest in. These fundamental differences made us decide to start a new proposal rather than build on top of the previous ones.
maybe we can should move this into an Acknowledgments section?
+1, that seems like a more appropriate place
Moved to an Acknowledgments section.
@tantek friendly ping. Do you think this PR will address your issue documented in https://tantek.com/2020/026/t2
Thanks @marcoscaceres for the improvements and review.
@tantek any last-minute suggestions before we merge this? I think it is helpful to have this text in the spec so future generations will find the prior work and can learn from it. Thanks for raising this issue in your blog to begin with.
I'll merge this Acknowledgments update and we will capture any additional feedback in subsequent PRs.
@tantek if this PR does not address your initial concern, please let us know.
Fix https://tantek.com/2020/026/t2
Preview | Diff