W3C home > Mailing lists > Public > uri@w3.org > January 2016

RE: URI Registration - limited release / commercial application

From: Peter Johnson <Peter.Johnson@incontextsolutions.com>
Date: Mon, 11 Jan 2016 22:50:45 +0000
To: Graham Klyne <gk@ninebynine.org>, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, "uri@w3.org" <uri@w3.org>
Message-ID: <SN1PR05MB1872886CE22513CC422B93F18EC90@SN1PR05MB1872.namprd05.prod.outlook.com>
Thank you both.  We will be going ahead with a domain-name-constructed scheme as per 3.8.


Peter Johnson
Senior Software Engineer 
m: 414.975.3008
e: Peter.Johnson@incontextsolutions.com | www.incontextsolutions.com
Connect with InContext Solutions:
Chicago | New York | Minneapolis | London

-----Original Message-----
From: Graham Klyne [mailto:gk@ninebynine.org] 
Sent: Monday, January 11, 2016 12:09 AM
To: "Martin J. Dürst"; Peter Johnson; uri@w3.org
Subject: Re: URI Registration - limited release / commercial application

On 11/01/2016 01:52, Martin J. Dürst wrote:
> On 2016/01/08 22:30, Peter Johnson wrote:
>> I found this email address while researching URI Scheme registration.  
>> If this is not the correct list, please direct me elsewhere.
> This is a good place to ask such questions.
>> I'm creating a URI scheme that is intended to be used only by users 
>> of our commercial software.  The scheme name will be the same as one 
>> of our software products. For very limited-use schemes, is it 
>> necessary to submit a provisional registration as per https://tools.ietf.org/html/bcp35#section-7 ?
> See https://tools.ietf.org/html/bcp35#section-6:

>     As such, a unique namespace MUST be used and 'provisional'
>     registration is strongly encouraged (unless the scheme name is
>     constructed from a domain name), as discussed in Section 3.8.
> "very limited use" isn't guaranteed to stay that way.


It's also worth noting that provisional registration is very lightweight.  It doesn't guarantee any kind of lock on the scheme name, but it does serve to alert other developers to what you are doing.

Received on Monday, 11 January 2016 23:21:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 11 January 2016 23:21:52 UTC