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

Add a reference to issue #40. #72

Closed
wants to merge 2 commits into from
Closed

Conversation

msporny
Copy link
Member

@msporny msporny commented Mar 16, 2016

Add a reference to issue #40.

If they are extensible, what is the extensibility mechanism?
Is the browser required to understand this extensibility mechanism?
</p>

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this wording is ambiguous and many of these questions are red herrings.

Proposed issue marker text:

<p class="issue" data-number="40" title="How does a website pass additional 
(not payment method specific) data to the payment app?">
It is proposed that a conformance criteria for implementations of this API be 
that any data passed into the request is passed on to the payment app unaltered. 
This would allow extensions of the data schema such as the addition of 
properties that are not documented in this specification or known to implementors 
such as JSON-LD @context or similar to be passed between the website and 
payment app.
</p>

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also note the resolution of the group which included wording for this issue marker:
w3c/webpayments#83

This is not appropriate wording while we have no extensibility guidance document but should be included as soon as we do.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works for me, happy to go w/ the issue text the group agreed to. I trust that the editors will use the issue text you pointed to.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for me. This feels like an important PR for the FPWD.

@adrianba
Copy link
Contributor

Merged as be49a84 with text from @adrianhopebailie.

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

Successfully merging this pull request may close these issues.

None yet

4 participants