Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1)

@rsolomakhin wrote:
> I hope to leave the subclassing semantics to the payment method specifications.

I agree for some part of the semantics (at least). The question I have is: are there any bits you need in the mediator to enable that? For instance, do we need "substring matching" so that different payment method specs can specify subclasses in some capacity?

In your proposal you use "/" for subclass matching and that syntax would enable anyone using that payment method spec to know that. But it would not enable the mediator to do anything with that syntax unless the mediator somehow specially implemented that payment method spec. If other payment method specs wanted to use other syntax, the mediator would have to know about that other syntax too. I believe your point is that "the mediator doesn't have to know about it." That's fine, but then my question is: what software component makes use of that information? Your answer might be: "The payment app". What algorithm does the payment app use to determine which URLs to provide to the mediator for matching?

Thanks for working on this. I am very happy to have a simple solution if it meets our needs!

Ian


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments-method-identifiers/issues/1#issuecomment-227751583