-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editorial: Add Contacts API history note #58
Conversation
Related TAG discussion: w3ctag/tag.w3.org#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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, though I don't know if we should claim anything about the "rich history"... 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.
@rayankans, is that a fair assessment?
Thus, I'd personally be inclined to drop "and this API strives to learn from this rich history" and just acknowledge the past... maybe we can should move this into an Acknowledgments section?
Oh, I found this (in the README): #31 I wonder if we should just migrate that over from the README? |
Updated to explain what differentiates this proposal from the past. |
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.
+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. |
SHA: e27a608 Reason: push, by anssiko Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Fix https://tantek.com/2020/026/t2
Preview | Diff