Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / w3c/webpayments-http-messages issues and pull requests
#15 - Updated Payment Response JSON schema
Pull Request -
State: open - Opened by wonsuk73 almost 7 years ago
#14 - Add Wonsuk Lee from ETRI as a co-editor of the spec
Pull Request -
State: open - Opened by wonsuk73 almost 7 years ago
#13 - Updated PaymentRequest JSON schema
Pull Request -
State: closed - Opened by wonsuk73 almost 7 years ago
- 1 comment
#12 - Fix link to spec
Pull Request -
State: open - Opened by BigBlueHat about 7 years ago
- 1 comment
#11 - fixing typo
Pull Request -
State: open - Opened by dret about 8 years ago
#10 - What are the security and privacy implications of the Core Messages?
Issue -
State: open - Opened by msporny over 8 years ago
#9 - How is message extensibility achieved?
Issue -
State: open - Opened by msporny over 8 years ago
#8 - What is the value range for 'type' property in PaymentResponse?
Issue -
State: open - Opened by msporny over 8 years ago
#7 - Should Core Messages contain paymentDetails and paymentOptions?
Issue -
State: open - Opened by msporny over 8 years ago
#6 - What is the value range for 'type' property in PaymentRequest?
Issue -
State: open - Opened by msporny over 8 years ago
- 2 comments
#5 - Fix PaymentResponse example wording for paymentTerms
Pull Request -
State: open - Opened by tnguyen14 over 8 years ago
- 1 comment
#4 - Inline JSON Schema / JSON-LD
Issue -
State: open - Opened by msporny over 8 years ago
#3 - Validation of values that may contain more than one item
Issue -
State: open - Opened by msporny over 8 years ago
- 5 comments
#2 - Should concrete expressions be normative?
Issue -
State: open - Opened by msporny over 8 years ago
#1 - How should we test Web Payments messages?
Issue -
State: open - Opened by msporny over 8 years ago
- 1 comment