PROPOSAL: Include an extensibility section in the browser API spec with an ISSUE marker indicating WIP.

[adrianhopebailie]

Background:

• The Payments and Credentials Community Groups are interested in JSON-LD as an extensibility mechanism for the payments API.
• Because we do not have consensus within the WPWG to mandate any particular extensibility mechanism, the proposal is to support the JSON-LD approach in a companion spec that is decoupled from the payments APi specification. This will allow the editors to develop it and gain community support more easily.

The proposal, therefore is to include a link to that companion spec and call for community feedback via an issue marker.

Thus, the proposal is to include this text in the specification (assuming a companion spec exists):

The JSON-LD Payment Extension specification (linked to the document) explains how to extend the parameters used with this API using JSON-LD.

And this issue marker text:

The Working Group seeks feedback from the community on that specification and how well it furthers interoperability needs in the payments ecosystem. To provide feedback, see the status section above (linked to status section of spec)

[ianbjacobs]

@adrianhopebailie ,

I am not sure if you were intending to include the two bullets after the NOTE in the spec. It was not not my intent that those bullets be included (just to be clear).

Ian

[adrianhopebailie]

@ianbjacobs most of the proposals have had some explanatory text to provide background for those that haven't followed the whole conversation. Do you think that needs to be explicitly marked as "background" info?

[adrianhopebailie]

RESOLVED in the 11 February call.

It was noted that there may be updates required to WebIDL to support some complex extensibility requirments. (The paymentRequest proposal does define a new term "JSON OBJECT" since WebIDL doesn't have the concept yet).

Some wording of the proposal was amended on the call.

RESOLUTION:

Include this text in the specification (assuming a companion spec exists):

Another specification (linked to the document) explains how to extend the parameters used with this API using JSON-LD.

And this issue marker text:

The Working Group seeks feedback from the community on that specification and how well it furthers interoperability needs in the payments ecosystem. To provide feedback, see the status section above (linked to status section of spec)

[msporny]

RESOLUTION (re: extensibility): Include this text in the specification ...

This Web Payments WG resolution regarding extensibility and JSON-LD has now been implemented here:

WICG/historical-web-payments-browser-api@6c16447

and here:

WICG/historical-web-payments-browser-api@1228d3f

You can see the live version here:

Web Payments Browser API (low-level):
http://wicg.github.io/web-payments-browser-api/#extensibility

and here:

Web Payments Checkout API (high-level):
http://wicg.github.io/web-payments-browser-api/checkout-api.html#extensibility