- From: L. David Baron <notifications@github.com>
- Date: Tue, 11 Apr 2017 01:06:04 -0700
- To: w3ctag/spec-reviews <spec-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 11 April 2017 08:06:36 UTC
So I've been bad about getting to this review in a timely manner. However, I did take a look at the Basic Card Payment spec today, and have a few initial comments that aren't concrete enough to turn into github issues (in addition to the two filed above): I think the idea of [linking to](https://w3c.github.io/webpayments-methods-card/#dfn-supportednetworks) and maintaining a [separate registry](https://www.w3.org/Payments/card-network-ids) of approved card network identifiers that's separate from the specification seems like a good thing. I'm not sure that the W3C has a lot of experience doing this sort of list/registry, though. I wonder if they should be a little more centralized within W3C so that W3C itself can keep track of them better if, e.g., the working group in question goes out of existence. Regarding billingAddress -- I'm curious if there's good practice on whether optional fields in dictionaries should, by convention, be nullable. I don't actually know. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/spec-reviews/issues/152#issuecomment-293182737
Received on Tuesday, 11 April 2017 08:06:36 UTC