On 2013-09-17 2:48 AM, Daniel Kinzler wrote:
To avoid future conflicts, we should probably prefix private paths with an underscore as titles cannot start with it (and REST APIs often use it for special resources).
That would be better.
But still, I think this is a bad idea. Essentially, putting Articles at the root of the domain mains hogging the domain as a namespace. Depending on what you want to do with your wiki, this is not a good idea.
For insteancve, wikidata uses the /entity/ path for URIs representing things, while the documents under /wiki/ are descriptions of these things. If page content was located at the root, we'd have nasty namespace pollution.
Basically: page content is only one of the things a wiki may server. "Internal" resources like CSS are another. But there may be much more, like structured data. It's good to use prefixes to keep these apart.
-- daniel
+1
We've got others for content-related things too besides ones for internal resources and structured data.
eg: https://test2.wikipedia.org/s/85
((And I'll try to resist starting a rant about the knockoff "REST" which is a partial premise here))
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]