search

w3c / contact-picker

Contact Picker API
https://www.w3.org/TR/contact-picker/
Other
74 stars 8 forks source link

Support sharing addresses #24

Closed rayankans closed 5 years ago

rayankans commented 5 years ago

Related to issue #12

beverloo commented 5 years ago

Please alphabetize. It seems odd to shadow PaymentAddress as ContactAddress but I guess it can work for future-proofing in case other fields would have to be added.

Is there sufficient (stated) implementation interest for this addition?

tomayac commented 5 years ago

The use case interest would definitely be ordering someone a gift.

/me has shipped chocolates I just ordered to you.

rayankans commented 5 years ago

Thanks Peter, I alphabetized the enum entries.

I extended PaymentAddress because ideally that's what we should be using, and this unblocks the spec until it's refactored into its own definition. If we ever decide to use our own thing at some point, it makes sense to name it ContactAddress from now, since it's an interface and will be web-exposed.

I've delayed resolving your concerns until after some TPAC discussions, and can confirm that there is enough interest to move forward with this.