Re: WPD Namespace (was: Place to put bug genie documentation.)

I thought meta was a parking lot that we weren't going to expose to search,
etc. If that's the case, how will changing the WPD namespace to Meta affect
that experience? Thanks. J


----------------------------
julee@adobe.com
@adobejulee

From:  Scott Rowe <scottrowe@google.com>
Date:  Monday, April 15, 2013 8:16 AM
To:  Doug Schepers <schepers@w3.org>
Cc:  "public-webplatform@w3.org" <public-webplatform@w3.org>
Subject:  Re: WPD Namespace (was: Place to put bug genie documentation.)

+1 
"Meta" is cool with me.
~Scott



On Fri, Apr 12, 2013 at 11:06 PM, Doug Schepers <schepers@w3.org> wrote:
> Hi, folks-
> 
> All this talk about the "WPD:" namespace reminded me that the designation
> itself is a bit strange. I don't remember exactly why we decided to use that
> prefix (it was probably some quirk of mine), but before we go too much
> further... maybe we should change it to something a bit less opaque, so we
> don't have to explain it to people?
> 
> We have the "Meta:" namespace prefix available, and that seems a bit more
> intuitive.
> 
> At the risk of starting a naming debate... what would people think about
> changing "WPD:" pages to "Meta:" (with a redirect)?
> 
> Regards-
> -Doug
> 
> On 4/12/13 1:47 PM, Jonathan Garbee wrote:
>> I was thinking more along the lines of:
>> * WPD:Contributors_Guide
>> ** Editing
>> *** Getting Started
>> ** Project Mangement
>> *** Filing an issue
>> *** Voting on issues
>> *** Editing an issues attributes
>> ** Design
>> 
>> With each lower level in the list simply being a sub-folder ( /
>> separator, we don't really use folders but that is the only thing I can
>> think to call it.) Doing WPD: so much just gets very repetitive very
>> quickly, and wouldn't even work doing WPD:Project_Management/WPD:Projects.
> 
> 
>