https://bugzilla.wikimedia.org/show_bug.cgi?id=43342

       Web browser: ---
            Bug ID: 43342
           Summary: Register wiki:// URI schema
           Product: MediaWiki
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: Unprioritized
         Component: General/Unknown
          Assignee: [email protected]
          Reporter: [email protected]
    Classification: Unclassified
   Mobile Platform: ---

The gradual transition from http:// links to https:// links is a reminder that
Wikipedia and its sister projects will (we hope) live longer than the current
set of protocols we use to access it.

Currently, all article URLs couple a reference with some implementation
details, leaving no single implementation-independent way of addressing
articles. You have, as I noted, http:// and https://, /w/index.php?title=X and
/wiki/X, and ways of retrieving articles via the API.

RFC 4395, "Guidelines and Registration Procedures for New URI Schemes",
explains the criteria for URI schemes and the process for registering a new one
(http://tools.ietf.org/html/rfc4395).

You can see the current set of registered schemes here:
http://en.wikipedia.org/wiki/URI_scheme

I propose we adopt interwiki links
(http://en.wikipedia.org/wiki/Wikipedia:InterWikimedia_links) as a basis for a
hierarchical identifier scheme. In other words, the current short names used
for interwiki links would form the basis of an initial directory of canonical
wiki names, to be used for a wiki:// URI scheme. URIs belonging to this scheme
would look like this:

wiki://w/en/529238017

The above URI references revision 529238017, belong to the article "Barack
Obama" on the English Wikipedia.

This URI scheme is agnostic about the means of retrieving the article. Just as
repositories specified using git:// URIs may be retrieved, at the agent's
discretion, via https or SSH, wiki:// URIs could be retrieved using the API, or
by being loaded from a dump, or what have you. The important thing is that the
reference is stable and permanent and not tied down to the state of networking
technology, circa 2012 (as the http:// -> https:// transition ably
demonstrates).

I don't think this is any crazier than a bitcoin:// or a secondlife:// URI
scheme, both of which officially exist and are recognized by the IETF.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to