Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / w3c/payment-method-id issues and pull requests
#74 - Is this being used?
Issue -
State: closed - Opened by decentralgabe 10 months ago
- 2 comments
#72 - Env smple
Issue -
State: closed - Opened by Mherjee18 over 1 year ago
#71 - Explorer | Solana
Issue -
State: closed - Opened by Mherjee18 over 1 year ago
#70 - Google Pay
Issue -
State: closed - Opened by Mherjee18 over 1 year ago
#69 - chore(tidy): tidy up document
Pull Request -
State: closed - Opened by github-actions[bot] about 3 years ago
#68 - Enable addition of new features
Pull Request -
State: closed - Opened by ianbjacobs about 3 years ago
#67 - Remove "standardized payment method identifiers"
Pull Request -
State: closed - Opened by marcoscaceres about 3 years ago
- 4 comments
#66 - Deprecate basic card
Pull Request -
State: closed - Opened by ianbjacobs about 3 years ago
#65 - Clarify security check for URL-based payment method identifier
Issue -
State: open - Opened by fred-wang over 3 years ago
- 2 comments
#64 - editorial: add conformance section
Pull Request -
State: closed - Opened by marcoscaceres about 5 years ago
#63 - editorial: fix xrefs
Pull Request -
State: closed - Opened by marcoscaceres about 5 years ago
#62 - Editorial: use new ReSpec stuff
Pull Request -
State: closed - Opened by marcoscaceres over 5 years ago
#61 - chore(ECHIDNA): use & instead of ;
Pull Request -
State: closed - Opened by marcoscaceres over 5 years ago
- 2 comments
#60 - Cr echidna
Pull Request -
State: closed - Opened by ianbjacobs over 5 years ago
#59 - chore(w3c): small update to w3c json
Pull Request -
State: closed - Opened by ianbjacobs over 5 years ago
#58 - Fix link to implementation report
Pull Request -
State: closed - Opened by ianbjacobs over 5 years ago
#57 - Editorial: Fixed duplication of url and spec name to sync with linked doc
Pull Request -
State: closed - Opened by wonsuk73 about 6 years ago
- 2 comments
#56 - Prepare for Proposed Recommendation
Issue -
State: closed - Opened by marcoscaceres about 6 years ago
- 2 comments
Labels: Process aid
#55 - Updated the link to the test-suit
Pull Request -
State: closed - Opened by yatri1609 about 6 years ago
- 8 comments
#54 - Generate an implementation report
Issue -
State: closed - Opened by marcoscaceres about 6 years ago
- 20 comments
#53 - Editorial: describe relationship to pay manifest
Pull Request -
State: closed - Opened by marcoscaceres about 6 years ago
- 1 comment
#52 - What can I do with a URL-based payment method identifier?
Issue -
State: closed - Opened by rsolomakhin about 6 years ago
- 7 comments
#51 - Auto publication no longer needed
Pull Request -
State: closed - Opened by deniak about 7 years ago
- 3 comments
#50 - Clarify CR exit requirements
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
#49 - Define syntax of standard PMI (closes #48)
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
- 1 comment
#48 - Better defined validity of standardized PMIs?
Issue -
State: closed - Opened by marcoscaceres about 7 years ago
- 2 comments
#47 - Other specs must define validity rules (closes #46)
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
- 1 comment
#46 - w3c.github.io/payment-method-id/ is not in parity with the tests
Issue -
State: closed - Opened by mhahmadi about 7 years ago
- 6 comments
#45 - Editorial: final round of prep for CR (closes #39)
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
- 1 comment
#44 - Define generalized PMI validator
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
#43 - Auto-publishing failing on bad token
Issue -
State: closed - Opened by marcoscaceres about 7 years ago
- 4 comments
#42 - editorial: add CR exit criteria
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
- 3 comments
#42 - editorial: add CR exit criteria
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
- 3 comments
#41 - Clarify validation of standardized PMIs
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
#40 - make fetching URL-PMI optional (closes #33)
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
- 3 comments
#40 - make fetching URL-PMI optional (closes #33)
Pull Request -
State: closed - Opened by marcoscaceres about 7 years ago
- 3 comments
#39 - CR checklist
Issue -
State: closed - Opened by marcoscaceres about 7 years ago
- 6 comments
Labels: Process aid
#38 - Rename repo payment-method-id
Issue -
State: closed - Opened by marcoscaceres about 7 years ago
- 6 comments
#37 - Add ignore example
Issue -
State: closed - Opened by marcoscaceres over 7 years ago
Labels: Editorial
#36 - editorial: rm 'Conditional Matching Beyond Payment Methods' section
Pull Request -
State: closed - Opened by marcoscaceres over 7 years ago
- 1 comment
#36 - editorial: rm 'Conditional Matching Beyond Payment Methods' section
Pull Request -
State: closed - Opened by marcoscaceres over 7 years ago
- 1 comment
#35 - feat: rewrite all the things
Pull Request -
State: closed - Opened by marcoscaceres over 7 years ago
- 3 comments
#34 - Remove "Conditional Matching Beyond Payment Method Identifier Matching"
Issue -
State: closed - Opened by marcoscaceres over 7 years ago
- 2 comments
#34 - Remove "Conditional Matching Beyond Payment Method Identifier Matching"
Issue -
State: closed - Opened by marcoscaceres over 7 years ago
- 2 comments
#33 - Reference manifest spec
Issue -
State: closed - Opened by marcoscaceres over 7 years ago
- 12 comments
Labels: Editorial
#33 - Reference manifest spec
Issue -
State: closed - Opened by marcoscaceres over 7 years ago
- 12 comments
Labels: Editorial
#32 - "W3C String" is overly generic
Issue -
State: closed - Opened by marcoscaceres over 7 years ago
#32 - "W3C String" is overly generic
Issue -
State: closed - Opened by marcoscaceres over 7 years ago
#31 - If URL parsing fails then always fail to match URLs.
Pull Request -
State: closed - Opened by adrianba over 7 years ago
- 3 comments
#31 - If URL parsing fails then always fail to match URLs.
Pull Request -
State: closed - Opened by adrianba over 7 years ago
- 3 comments
#30 - citation to dated version of since-abandoned url spec fork is unusual
Issue -
State: closed - Opened by dbaron over 7 years ago
- 3 comments
Labels: Editorial
#30 - citation to dated version of since-abandoned url spec fork is unusual
Issue -
State: closed - Opened by dbaron over 7 years ago
- 3 comments
Labels: Editorial
#29 - [SECURE-CONTEXTS] should be a normative rather than informative reference
Issue -
State: closed - Opened by dbaron over 7 years ago
- 7 comments
Labels: bug, question
#28 - use of 'must' in section on Syntax of URLs as Payment Method Identifiers is suspicious
Issue -
State: closed - Opened by dbaron over 7 years ago
- 1 comment
Labels: Editorial
#27 - Check what happens if URL parsing throws....
Issue -
State: closed - Opened by marcos-travel over 7 years ago
- 2 comments
#27 - Check what happens if URL parsing throws....
Issue -
State: closed - Opened by marcos-travel over 7 years ago
- 2 comments
#26 - Link to registry of W3C-published short strings
Issue -
State: closed - Opened by ianbjacobs over 7 years ago
- 18 comments
#25 - chore: tidy
Pull Request -
State: closed - Opened by marcoscaceres over 7 years ago
#24 - Add marcoscaceres as collaborator
Issue -
State: closed - Opened by marcoscaceres over 7 years ago
- 1 comment
#23 - Payment Method Identifier needs dfn
Issue -
State: closed - Opened by marcoscaceres over 7 years ago
- 1 comment
Labels: Editorial
#22 - Circular dependency between PMI and PR specs
Issue -
State: closed - Opened by adrianhopebailie over 7 years ago
- 2 comments
Labels: Editorial
#22 - Circular dependency between PMI and PR specs
Issue -
State: closed - Opened by adrianhopebailie over 7 years ago
- 2 comments
Labels: Editorial
#21 - Changes to address Action #40
Pull Request -
State: closed - Opened by adrianhopebailie over 7 years ago
- 5 comments
#20 - Why are payment ids restricted to [a-z0-9]?
Issue -
State: closed - Opened by stevenatkin over 7 years ago
- 2 comments
#19 - How should we address payment method manifest files?
Issue -
State: closed - Opened by ianbjacobs almost 8 years ago
- 11 comments
#19 - How should we address payment method manifest files?
Issue -
State: closed - Opened by ianbjacobs almost 8 years ago
- 11 comments
#18 - SRI on manifest
Issue -
State: closed - Opened by adrianhopebailie almost 8 years ago
- 4 comments
#18 - SRI on manifest
Issue -
State: closed - Opened by adrianhopebailie almost 8 years ago
- 4 comments
#17 - Support for PMI's with schemes other than https?
Issue -
State: closed - Opened by adrianhopebailie almost 8 years ago
- 4 comments
#17 - Support for PMI's with schemes other than https?
Issue -
State: closed - Opened by adrianhopebailie almost 8 years ago
- 4 comments
#16 - Update of PMI spec
Pull Request -
State: closed - Opened by ianbjacobs almost 8 years ago
- 1 comment
#15 - Update editor list
Pull Request -
State: closed - Opened by rvm4 about 8 years ago
#14 - Add github links
Pull Request -
State: closed - Opened by halindrome about 8 years ago
#14 - Add github links
Pull Request -
State: closed - Opened by halindrome about 8 years ago
#13 - Schema.org PaymentMethod as namespace for short strings
Issue -
State: closed - Opened by adrianhopebailie about 8 years ago
- 5 comments
#13 - Schema.org PaymentMethod as namespace for short strings
Issue -
State: closed - Opened by adrianhopebailie about 8 years ago
- 5 comments
#12 - Should a payment method identifier that is a URL bind that payment method to a single payment app or origin?
Issue -
State: closed - Opened by adrianhopebailie about 8 years ago
- 6 comments
#12 - Should a payment method identifier that is a URL bind that payment method to a single payment app or origin?
Issue -
State: closed - Opened by adrianhopebailie about 8 years ago
- 6 comments
#11 - Resolve whether browsers need to police payment app claims of supported methods
Issue -
State: closed - Opened by adamroach about 8 years ago
- 15 comments
#10 - update pmi spec with apen and proprietary payment method identifiers
Pull Request -
State: closed - Opened by rvm4 about 8 years ago
- 1 comment
#10 - update pmi spec with apen and proprietary payment method identifiers
Pull Request -
State: closed - Opened by rvm4 about 8 years ago
- 1 comment
#9 - Why URLs?
Issue -
State: closed - Opened by annevk about 8 years ago
- 47 comments
#8 - Identifier equivalence does not handle failure
Issue -
State: closed - Opened by annevk about 8 years ago
- 8 comments
#8 - Identifier equivalence does not handle failure
Issue -
State: closed - Opened by annevk about 8 years ago
- 8 comments
#7 - Add Security Considerations and Privacy Considerations sections
Issue -
State: closed - Opened by adamroach about 8 years ago
- 5 comments
Labels: Editorial
#7 - Add Security Considerations and Privacy Considerations sections
Issue -
State: closed - Opened by adamroach about 8 years ago
- 5 comments
Labels: Editorial
#6 - slight rewording
Pull Request -
State: closed - Opened by dret about 8 years ago
- 1 comment
#6 - slight rewording
Pull Request -
State: closed - Opened by dret about 8 years ago
- 1 comment
#5 - PROPOSAL: PMI identifies payment method specification, use meta-data for additional granularity
Issue -
State: closed - Opened by adrianhopebailie over 8 years ago
- 26 comments
Labels: Priority: High, proposal
#5 - PROPOSAL: PMI identifies payment method specification, use meta-data for additional granularity
Issue -
State: closed - Opened by adrianhopebailie over 8 years ago
- 26 comments
Labels: Priority: High, proposal
#4 - Update references and issue markers
Pull Request -
State: closed - Opened by adrianhopebailie over 8 years ago
#3 - Should a payment method identifier (URL) resolve to a machine readable resource that describes it?
Issue -
State: closed - Opened by adrianhopebailie over 8 years ago
- 2 comments
Labels: Priority: Medium, proposal
#3 - Should a payment method identifier (URL) resolve to a machine readable resource that describes it?
Issue -
State: closed - Opened by adrianhopebailie over 8 years ago
- 2 comments
Labels: Priority: Medium, proposal
#2 - PROPOSAL: Use query string parameters for PMI matching
Issue -
State: closed - Opened by adrianhopebailie over 8 years ago
- 1 comment
Labels: Priority: High, proposal
#2 - PROPOSAL: Use query string parameters for PMI matching
Issue -
State: closed - Opened by adrianhopebailie over 8 years ago
- 1 comment
Labels: Priority: High, proposal
#1 - Should we define nesting/grouping semantics for payment method identifier matching?
Issue -
State: closed - Opened by adrianhopebailie over 8 years ago
- 5 comments
Labels: help wanted, question, Priority: High