Re: Use of URNs for PMIs

On 8/9/16 13:33, Ian Jacobs wrote:
>> On Aug 8, 2016, at 5:30 PM, Adam Roach <abr@mozilla.com> wrote:
>>
>> On 8/8/16 17:26, Ian Jacobs wrote:
>>>   1. It must be possible for the Working Group to mint a payment method identifier for any payment method.
>>>      1a) The Working Group uses URNs with a root namespace registered with the IETF.
>>>      1b) W3C is the only entity that can allocate names within that namespace.
>>>      1c) Names are allocated by Working Group decision. We don’t expect to allocate many names.
>>>      1d) We can come up with a variety of ways to publish those names
>>>
>> I think that works.
>>
>>>   2. It must be possible for the anyone to mint a payment method identifier for a payment method under their control.
>>>      2a) Those parties can use whatever mechanism they want, other than URNs within the W3C namespace.
>>>
>> I would personally be happier if we limited it to (a) URLs under the control of the entity minting the payment method,
> I don’t know how we enforce that.

The same way we do everything else: we state it in a spec, and people 
follow it or they don't.

>   And I’m not sure of the need to restrict it thusly.

So you'd be okay with Paypal deciding to assign a PMI of 
"https://www.w3c.org/payment-type/paypal" to a "Paypal" payment type?

The overall point here is that by nominally restricting URL PMIs to be 
under the control of the issuing entity, that entity can ensure 
uniqueness. If people start grabbing URLs from domains other than their 
own, you're going to end up with collisions.

>> and (b) URNs conforming to RFC 3406 (leaving it open for other entities to register new URN namespaces for this purpose if they so desire). I'm not comfortable with an "any string you want" approach.
> I think we agree that PMIs should be URNs or URLs. We have a few options, including:
>
>   * Update the PMI spec to say URLs or URNs. (Today it says URLs)
>   * Update the PMI spec to say URIs (which includes both)

What I propose above is the second thing.


-- 
Adam Roach
Principal Platform Engineer
Office of the CTO