PR API Status Update for 24 January 2019

Status: These are Notes for Ian Jacobs to give a status update at the WPWG's 24 Jan 2019 teleconference.

Status of Call for Consensus to remote regionCode

Anticipate decision to approve the proposal. Email confirmation to follow the teleconference.

What is the timeline for browsers to converge in implementation on the agreed to semantics for canMakePayment?
What is the timeline (not for v1 of PR API, but in parallel) of support for specification and implementation of hasEnrolledInstrument?

Per W3C Process, we must return to Candidate Recommendation due to substantive changes.
In the request to return to CR, must include evidence of wide review from relevant parties; in this case Ian plans to request review on the changes from the Privacy Interest Group and the Security Interest Group.
The Director approves publication as a revised CR.
At that point we turn attention to implementation; see the implementation report and tests with fewer than 2 implementations. We will work with implementers during that time to bring implementations up to speed with the specification. We will also spend time doing manual testing (as some tests are not automated or automatable).
Once we have a suitable implementation report, we will request to advance to Proposed Recommendation (minimum 4-week review by the Advisory Committee).