- From: Ian Jacobs <ij@w3.org>
- Date: Tue, 19 Apr 2016 12:05:43 -0500
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: public-payments-wg@w3.org
- Message-Id: <A3E1C34F-1010-486A-81A7-D895C5938F7D@w3.org>
> On Apr 19, 2016, at 12:02 PM, Manu Sporny <msporny@digitalbazaar.com> wrote: > > On 04/18/2016 09:12 AM, Ian Jacobs wrote: >>> What is the process for selecting the short names for these specs? >> >> They were proposed in the draft documents. > > I didn't think I was agreeing to that shortname and thought better ones > would be selected before publication, for example: > > payment-browser-api > payment-methods > payment-method-card > > and then: > > payment-apps > payment-mediator > payment-http-api > payment-core-messages > payment-method-sepa > payment-method-bitcoin > >> * I expect there will be new shortnames coming if we reorganize the >> documents. * If we decide to change the shortname as a result in a >> future publication, the Webmaster will redirect the previous URIs to >> the new ones. >> >> Therefore, we can evolve our shortname choices as we make progress on >> the spec organization. > > This is sloppy. Short names hang out in TR space forever. Let's pick > better ones if we don't like the current ones. We can and should revisit this as the set of our specifications evolves. Ian -- Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs Tel: +1 718 260 9447
Received on Tuesday, 19 April 2016 17:05:46 UTC