Skip to content
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

Confining the definition of user agents to browsers #34

Closed
msporny opened this issue Dec 16, 2015 · 2 comments
Closed

Confining the definition of user agents to browsers #34

msporny opened this issue Dec 16, 2015 · 2 comments

Comments

@msporny
Copy link
Member

msporny commented Dec 16, 2015

The Web Payments WG charter currently states that we're to work on deliverables for "user agents":

http://www.w3.org/Payments/WG/charter-201510.html#deliverables

It is clear that one of these user agents is a browser and the payment request work strongly binds to that concept by pulling in requirements like HTML5, DOM4, and ECMA-262 6th Edition:

http://wicg.github.io/paymentrequest/specs/paymentrequest.html#dependencies

There are many other types of user agents than just browsers. It could be argued that we're not fulfilling our charter if we deliver only the interfaces as defined in paymentRequest. To put this another way, if the charter stated that the WG is confined to just 'browsers', I expect that there would have been multiple formal objections to the charter.

I'm asserting that we need to consider an API that works for user agents that are not browsers (and instead demonstrate bindings to something more common across user agents like an HTTP API):

http://web-payments.github.io/web-payments-http-api/

This is not to say that we shouldn't also have APIs for browsers, but browsers are not the only deployment targets here. Is an HTTP API in scope for this WG?

@ianbjacobs
Copy link
Contributor

Is this the same as issue 17?
#17

@msporny
Copy link
Member Author

msporny commented Dec 16, 2015

Yes, it is. Closing it. Thanks @ianbjacobs

@msporny msporny closed this as completed Dec 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants