Skip to content
This repository has been archived by the owner on Aug 27, 2021. It is now read-only.

Clarify this specification is intended to become a W3C Note #27

Closed
ianbjacobs opened this issue Mar 22, 2017 · 4 comments
Closed

Clarify this specification is intended to become a W3C Note #27

ianbjacobs opened this issue Mar 22, 2017 · 4 comments
Assignees

Comments

@ianbjacobs
Copy link
Contributor

It is my understanding this spec is intended to become a W3C Note (and that the WPWG has the same intentions for other payment method specs). The status section does not indicate clearly that this spec is NOT expected to become a recommendation.

@zkoch
Copy link
Contributor

zkoch commented Apr 19, 2017

@ianbjacobs during the F2F, we decided to keep this a note, correct? Or did we get closure here?

@ianbjacobs
Copy link
Contributor Author

Yes, we decided to keep it a NOTE. Please update the status section (via respec flags I believe) accordingly.

Thanks!

Ian

@marcoscaceres
Copy link
Member

I'm still of two minds about this because we need this for the PR API (and possibly for the Payment Handler API too). That is, in both those aforementioned specs, these objects MAY be returned - putting conformance requirements on this particular spec.

Even if this spec is not mentioned in the PR spec, user agents still need to produce objects that conform to this specification when "basic-card" is used.

Thus, I I feel this spec needs to be on the Rec track.

@ianbjacobs
Copy link
Contributor Author

@adrianba, I recall that you were a proponent of Note. Can you weigh in on this topic and whether this perspective from @marcoscaceres is new enough information that we should re-open the (twice closed) issue? Thanks!

@marcoscaceres marcoscaceres self-assigned this Aug 9, 2017
marcoscaceres added a commit that referenced this issue Aug 9, 2017
* closes #34
* closes #30
* closes #27
* closes #32
* closes #26
marcoscaceres added a commit that referenced this issue Aug 9, 2017
* closes #34
* closes #30
* closes #27
* closes #32
* closes #26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants