text:
Wikivoyage:Previous collaborations/2006

This page lists previous collaborations for 2006.

26 December 2006 - 1 January 2007

 * Baton Rouge

Why
Needs the following:

 * Understand section.
 * Get around section
 * Sights
 * "Do" activities
 * Research phone numbers and addresses for listings.
 * Overall the article needs more information and improve what information we do have. -- (WT-en) Sapphire 13:36, 15 November 2006 (EST)

Results
5 edits by 1 author, Outline to Outline

19 December 2006 - 25 December 2006

 * Hoi An

Why
Candidate for DotM February 2007 but needs a little work to fit as DoTM. (WT-en) Jc8136 10:13, 10 August 2006 (EDT)

Result
11 edits by 2 authors, Guide to Guide

12 December 2006 - 18 December 2006

 * Cuba.

Why
The main article has some good info in it but could be expanded, and most of the subarticles need serious help or even to be created in the first place. More info for U.S. travelers would be good too, such as how to handle your finances being that you can't use credit cards or atm's. Maybe even a separate article US travelers in Cuba detailing everything from arriving in Cancun and buying a ticket to Havana to avoiding places like Guantanamo and if in trouble, how long to hold out before breaking down and contacting the U.S. interests office, etc. I think there's a ton of possibilities for Cuba and all its subarticles. Trinidad, Santiago, all of these have little to no info.
 * http://www.seat61.com/Cuba.htm is a good website that could provide info for getting around by train.
 * the main Cuba map could be updated with a few more popular destinations like Trinidad and Baracoa, and maybe even show the train line? (WT-en) Cacahuate 04:13, 7 November 2006 (EST)

Result
38 edits by 4 authors, Usable to Usable

5 December 2006 - 11 December 2006

 * Krakow.

Why
Good amount of information in the article. Could do with a bit of MoS editing, more pics, map. Big problems with districts though - 16 are listed on main page, but most dont warrant articles and need to be integrated together into a smaller number of good quality district articles. In my opinion not too far off being a very good guide article, maybe even a star if all above issues are addressed. (WT-en) Tsandell 07:11, 19 June 2006 (EDT)

Result
8 edits by 7 authors, Guide to Guide.

14 November 2006 - 4 December 2006

 * Rio de Janeiro

Why
Good base that needs a bit of formatting and rewriting. A map would be really good. (WT-en) Jan 10:55, 27 July 2006 (EDT)

Result
15 edits by 10 authors, Usable to Usable.

07 November 2006 - 13 November 2006

 * London.

Why
Needs MoSing. -- (WT-en) Andrew Haggard (Sapphire) 15:08, 3 July 2006 (EDT)

Result
7 edits by 5 authors, Usable to Usable.

31 October 2006 - 06 November 2006

 * Delhi.

Why
We're long overdue to have an Indian city as a DotM, and this one isn't too far from being ready. MoS work and grammar/spelling checks are needed throughout. Many attractions need hours/fees/contact info, etc. And as usual, it needs a map. -- (WT-en) Bill-on-the-Hill 14:22, 18 June 2006 (EDT)

Result
35 edits by 11 authors, Usable to Usable.

24 October 2006 - 30 October 2006

 * Los Angeles.

Why
There's actually some pretty good info in the districts, but the main page is a mess, with great big slabs of emptiness. (WT-en) Jpatokal 20:38, 16 June 2006 (EDT)

Result
almost 100 edits by 9 users usable to usable

17 October 2006 - 23 October 2006

 * Newcastle (New South Wales).

Why
A few more sleep listings and conformity to MoS.

Result
2 edits by 2 user guide to guide

10 October 2006 - 16 October 2006

 * Brisbane.

Why
Information for listing is needed and conformity to MoS. - (WT-en) Andrew Haggard (Sapphire) 01:56, 14 June 2006 (EDT)
 * Can somebody do a map while we're at it? Some good editing on this one could promote it to DOTM-worthy very quickly, if a map can be added. -- (WT-en) Bill-on-the-Hill 21:26, 14 September 2006 (EDT)

Result
13 edits by 3 users Usable to usable

03 October 2006 - 09 October 2006

 * Pittsburgh.

Why
The article needs to conform to MoS. District articles need templates, conform to MoS, and listings for sections. - (WT-en) Andrew Haggard (Sapphire) 22:41, 12 June 2006 (EDT)

Result
10 edits by 6 users usable-usable

26 September 2006 - 02 October 2006

 * Frankfurt.

Why
Needs to conform to manual of style. - (WT-en) Andrew Haggard (Sapphire) 18:00, 11 June 2006 (EDT)

Result
2 edits by 2 users guide - guide

19 September 2006 - 25 September 2006

 * Philadelphia

Why
Very basic MoS editing, maps, and photos are the only things that seperate this article from becoming a "star." Also, help researching phone numbers and email addresses for listings would be helpful. - (WT-en) Andrew Haggard (Sapphire) 22:50, 12 June 2006 (EDT)

Result
6 edits by 4 users guide to guide

12 September 2006 - 18 September 2006

 * Kruger National Park

Why
Nominated for DotM Feb 07, but needs a bit of MoSing, info put in appropriate places. -- (WT-en) Tim 06:59, 15 August 2006 (EDT)
 * Information also needs to be transferred into the many camp articles.

Result
3 edits by 2 users guide to guide

5 September 2006 - 11 September 2006

 * Moscow

Why
A city this important, and fascinating, should have a far better article. Needs to be broken into districts, which then should be populated; lots of expansion in "See" and "Do" is possible; "Stay safe" and "Cope" sections need addition/completion; and a good map would be useful. The current article is barely Usable; we can do better. -- (WT-en) Bill-on-the-Hill 16:39, 11 June 2006 (EDT)
 * See my comments on Moscow's talk page. I think I left some useful info there, but I'm too lazy to confirm this.  -- (WT-en) Andrew Haggard (Sapphire)

Result
32 edits by 12 users usable - usable

29 August 2006 - 4 September 2006

 * Macau

Why
Needs formatting, a bit more information and especially some restructuring. (WT-en) Jan 03:30, 06 June 2006 (EDT)

Result
65 edits by 6 users usable to usable

22 August 2006 - 28 August 2006

 * Bermuda

Why
Needs more content in Do/Buy/Eat/Drink/sleep. Was nominated a while ago by anonymous person but interesting destination. (WT-en) Jan 04:19, 12 July 2006 (EDT)
 * Could also do with a few pictures. -- (WT-en) Tim 16:39, 12 August 2006 (EDT)
 * Seems to need underlying organization of towns/parishes with detail in them. (WT-en) OldPine 23:01, 24 August 2006 (EDT)

Result
27 edits by 3 users usable - usable

15 August 2006 - 21 August 2006

 * Everest.

Why
It'd be nice to establish the idea of doing Regions, like this one, as viable CotW candidates. This one needs photos (shouldn't be hard to find) and maps, as well as contact info for many of the things mentioned. "Respect" could use some elaboration. -- (WT-en) Bill-on-the-Hill 11:22, 4 June 2006 (EDT) - just a note to add to above comments - there are currently no phone lines in the Everest region, so there are no contact numbers/info.
 * I agree with the comments regarding contact info. There are no phone numbers or mailing addresses in the Everest region. Furthermore, I'm not sure what kind of elaboration is required for 'respect'. If Bill can leave me message on my discussion page to explain, I could probably add the info immediately. However, I do agree that the quality of the article would be greatly enhanced with the addition of photographs and maps - though don't know if that requirement alone would qualify it as 'collaboration of the week' canditate. (WT-en) WindHorse 20 June 06

Result
14 edits by 5 users usable-usable region

8 August 2006 - 14 August 2006

 * Warsaw

Why
A lot of great information, some listings need to be MoS'd. Move information into respective districts. See Talk:Warsaw on an easy way to help with this. - (WT-en) Andrew Haggard (Sapphire) 19:06, 30 May 2006 (EDT)

Result
106 edits by 6 users unrated to guide

1 August 2006 - 7 August 2006

 * Odense

Why
Usable guide for Danish city, birthplace of Hans Christian Anderson. Odense is also the site of Wikisym 2006, the ACM's annual wiki conference, from 21-23 Aug. A guide or star article would definitely be useful for Wiki people at that conference. Some work needed: expanded Understand section, reformat the listings in See, more hotels in Sleep and better listings, more restaurants in Eat and better listings, some day trips in Get out. --(WT-en) Evan 14:33, 9 July 2006 (EDT)

Result
11 edits by 4 users Usable - Usable

25 July 2006 - 31 July 2006

 * Cambridge (Massachusetts)

Why
Cambridge is the site of the upcoming Wikimania 2006 Wiki conference. The Cambridge article is uneven and needs a good combing through. A guide or star article would help highlight Wikivoyage for Wikimania participants. Five points of improvement: a few paragraphs of overview and history in Understand; edit down the public transportation section of Get Around; long-form attraction listings for Harvard and MIT; a map (!); Expand Sleep listings. --(WT-en) Evan 14:47, 9 July 2006 (EDT)

Result
22 edits by 6 users Usable - Usable

18 July 2006 - 24 July 2006

 * Berlin

Why
New district structure shuffled the content and more pictures would be good. Improved a lot and star status isn't to far. (WT-en) Jan 13:41, 16 May 2006 (EDT)

Result
13 by 6 users Guide - Guide

11 July 2006 - 17 July 2006

 * Calcutta

Why
Has a lot of information, but is in desperate need of reformatting. (WT-en) WindHorse 23 April 06

Result
8 edits by 3 users Usable to Usable

4 July 2006 - 10 July 2006

 * Washington, D.C.

Why
Conform all listings to MoS, shouldn't be a problem. Also, images of the Mall, WWII memorial, Vietnam memorial, Capitol, Smithsonian buildings or exhibitions are needed.

Result
25 edits by eight authors, Unrated - Guide

27 June 2006 - 3 July 2006

 * Budapest and it's Districts.

Why
In Project:Destination of the Month candidates it was pointed out that it needed to be put more in line with the Manual of Style. I've done what I can, but others may see more to do. Needs more telephone numbers. A map would be nice too. -- (WT-en) DanielC 14:03, 7 April 2006 (EDT)

Result
6 edits by one author, An additional 10 edits were made by two authors to district pages.

20 June 2006 - 26 June 2006

 * Dili

Why
lots of good info, but need formatting, removal of first person, some pictures to liven things up, shuffling some info into East Timor. (WT-en) Jpatokal 03:28, 21 March 2006 (EST)

Result
4 edits by 3 authors, Outline to Outline.

13 Jun 2006 - 19 Jun 2006

 * Route 66.

Why
Very close to a "star itinerary" already, but needs some good maps. A few more good photos wouldn't hurt. Many descendant pages need filling out. A little work could make this one the first "itinerary" to be a DotM. -- (WT-en) Bill-on-the-Hill 11:29, 5 May 2006 (EDT)
 * (And anyone who's seen the movie Cars will appreciate the timeliness of this Collaboration.) - (WT-en) Todd VerBeek 16:27, 12 June 2006 (EDT)

Some information about the distances covered each day would be very useful.

Result
19 edits by 3 authors, Unrated to Guide

6 Jun 2006 - 12 Jun 2006

 * Cologne

Why
needs more content, maybe a different structure and individual pieces of information needs to be clarified. Some MoS work is needed, and would anybody like to attempt a map? -- (WT-en) Bill-on-the-Hill 19:42, 27 May 2006 (EDT)

Result
56 edits by 3 authors, Usable to Guide

30 May 2006 - 5 Jun 2006

 * Uganda.

Why
Needs to be split up into into destination pages, entries formatted properly, could use some pictures too. (WT-en) Jpatokal 11:38, 3 April 2006 (EDT)

Result
17 edits by 4 authors, Usable to Usable

23 May 2006 - 29 May 2006

 * Cuzco

Why
Cuzco is an exciting place that could easily become DotM and is from a region that has had few highlighted articles. There is already a lot of info in it but it needs serious editing to comply with the Manual of Style: listings are missing addresses and contact info, there are things placed in the wrong sections and there are some 1st person pronouns. It would benefit from a decent history section, needs a good map and maybe one or two pictures taken from less than 1 mile afar. (WT-en) Ricardo (Rmx) 19:07, 26 April 2006 (EDT)

Result
21 edits by 2 authors, Usable to Usable

16 May 2006 - 22 May 2006

 * Manila.

Why
Needs more images (Shared has a decent selection), See/Buy listings need to be MoS'ed, districts needed to be at least made ready ("Manila/Makati" instead of just red link to "Makati"), Get around should be sectioned, Get out has to be whipped into shape. (WT-en) Jpatokal 05:05, 14 April 2006 (EDT)

Result
9 edits by 6 authors, Usable to Usable

Why

 * Beijing An amazing place, needs more info though, One of the most important cities in the world, more info needed about 2008 Olympics, Needs a map, all of that info won't be helpful if all the streets are in Chinese and the info doesn't say what area of the city it is in (no landmarks to guide your way), No info about renting a car, Not enough pictures, Possibly needs subway map (I could help, I have a Chinese road atlas (of course there would be copyright violations) --(WT-en) Worldtraveller 15:56, 21 March 2006 (EST)
 * Subway map can be found here, it's free (CC license). And I've uploaded many subway and railway pictures there, all in Category:Rail transport in Beijing. (WT-en) Yao Ziyuan 22:57, 11 May 2006 (EDT)

Result
16 edits by 9 authors, Usable to Usable

2 May 2006 - 8 May 2006
Pattaya

Why

 * This article is HUGE and needs to be broken down! There is so much information that the article is no longer useful. (WT-en) Sapphire 03:02, 27 April 2006 (EDT)

This is way to big and needs a a sample itinerary. 70.127.34.98 12:24, 1 May 2006 (EDT)

Result
19 edits by 3 authors, Guide to Guide

24 April 2006 - 1 May 2006
Guangzhou

Why

 * The city is a major point of entry to China, so a good article would be very useful to travelers heading into that country. At the moment, all sections are a little thin, except possibly 'see' and 'understand.'(WT-en) WindHorse 9 March 06

Result
24 edits by 6 authors, Outline to Usable

17 April 2006 - 23 April 2006
Munich

Why

 * A few good maps for the various districts
 * Spelling and grammar
 * The following districts need more information and need to be formatted correctly.
 * Munich/OEZ
 * Munich/Haidhausen
 * Munich/Thalkirchen
 * Munich/Neuhausen-Nymphenburg - Needs more information for "Do," "See."

Hofbaeuhaus, Olympic Park, Residenz palace, Frauenkirche, Hirschgarten, Viktualienmarkt,Englischer Garten, Oktoberfest, Christkindlmarkt (Christmas markets on Marienplatz), the Glockenspiel, National theather, Deutsches Museum, Loewenbraeu (brewery), Augustiner brewery (This would be cool, because despite Hofbraeu being the known beer Augustiner is the prefered beer of the locals), Schloss Nymphenburg gardens.
 * Expand all "Sleep sections"
 * Expand "Eat," "Do," "Buy" sections.
 * Photos of these attractions and events are needed or would at the very least be appreciated:

The article is currently rated as a "guide." This article needs a lot of work before June, July, and August to allow travellers the opportunity to plan for Oktoberfest. I've been trying to do as much as possible, but I'm usually distracted by Rail travel in North America, Rail travel in Europe, or Wikipedia:Wikipedia:Requested images and I tend to forget about this article. Please help. Thanks (WT-en) Sapphire 07:20, 2 April 2006 (EDT)

Result
21 edits by 8 authors, Guide to Guide; additionally, 27 edits to descendant articles

10 Apr 2006 - 16 Apr 2006
Jerusalem

Why
Listings need to be MoSed, districting is haphazard, overall a bit of a mess. (WT-en) Jpatokal 07:52, 8 March 2006 (EST)

Result
18 edits by 6 authors, Outline to Usable;

3 Apr 2006 - 9 Apr 2006
Skye

Why

 * More photos (it's an incredibly gorgeous place that can stand a zillion images)
 * A good map or two
 * Copyediting, particularly for spelling, some of which is non-obvious
 * Details on "Sleep" listings
 * Articles on regions and minor towns referenced
 * "Get out", e.g. minor isles such as Eigg
 * Expanded "Do" information.
 * The current "stub" rating is obsolete; it's more "Usable" but still needs work. -- (WT-en) Bill-on-the-Hill 23:40, 28 February 2006 (EST)

Result
27 edits by 4 authors, Usable to Usable; additionally, 27 edits to descendant articles

27 Mar 2006 - 2 Apr 2006
Sendai

Why
(WT-en) WindHorse 15 Feb 06
 * needs: more sleep listings,
 * map,
 * images
 * general editing.

Result
42 edits by 5 authors, Usable to Guide

20 Mar 2006 - 26 Mar 2006
Dubai

Why
-Simply requires more information.

 * As discussed on Talk:Dubai, the Japanese version has a lot more info and there's even a handy Babelfished version listing lots of flophouses. (WT-en) Jpatokal 03:19, 7 March 2006 (EST)

Result
37 edits by 5 authors, Usable to Usable

13 Mar 2006 - 19 Mar 2006

 * Bangalore -

Why

 * needs: general editing,
 * restaurant list pulling into shape,
 * a map,
 * possibly splitting up into districts (at least the districts of Bangalore Urban should be listed),
 * researching which of the 'Get out' listings should be placed under Bangalore Rural.
 * (WT-en) WindHorse 15 Feb 06

Result
67 edits by 9 authors, Usable to Usable

6 Mar 2006 - 12 Mar 2006

 * Toronto

Why
This would be a good one for early summer feature if brought into shape. -- (WT-en) Tom Holland (xltel) 10:15, 16 Feb 2006 (EST)
 * Needs a lot more sleep,
 * Photos,
 * Some work on MoS,
 * A map,
 * The districts need attention as well.

 * We're going there tomorrow -- we'll take some photos! --(WT-en) Evan 20:33, 5 March 2006 (EST)

 * I can work on a map. Are you looking for metro-region or downtown?. Maybe both? - (WT-en) bulliver 17:22, 11 March 2006 (EST)
 * Downtown map done, working on Annex - (WT-en) bulliver 15:44, 12 March 2006 (EST)
 * ...and done. - (WT-en) bulliver 18:54, 12 March 2006 (EST)

Result
45 edits by 7 authors, Usable to Usable

27 Feb 2006 - 5 Mar 2006

 * Umm al Quwain

Why

 * Arabic script
 * Pictures
 * Addresses for everything
 * Format according to MoS
 * Places to eat, drink or sleep.

(WT-en) Jpatokal 03:51, 16 Feb 2006 (EST)

Result
19 edits by 6 authors, Outline to Outline.

20 Feb 2006 - 26 Feb 2006

 * Chennai

Why

 * Weeding of long listings lists
 * Format of listings (Sleep, Eat, Do, See, etc)
 * Copyediting (caps, spelling, language issues)
 * Additional descriptive content
 * At least one good photo.

Result
106 edits by 14 authors, Usable to Guide.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Wikivoyage:Previous collaborations/2006


text:
Wikivoyage:Previous collaborations/2007

This page lists previous collaborations for 2007.

26 December - 1 January

 * Suzhou
 * One of China's top tourist destinations.
 * We have plenty of text but it could be better organised.
 * Much missing, phone numbers for hotels, etc.
 * Needs MoS work and some de-touting. (WT-en) Pashley 10:07, 17 December 2007 (EST)

19 December - 25 December
129.177.169.78 12:50, 4 December 2007 (EST)
 * Bergen. The article has a lot of information, and is on its way to become a star. It represents an area (Northern Europe) of which only one destination has been the destination of the month (Helsinki, back in 2005). Bergen is regarded as "the gateway to the fjords", and thus very important for most tourists visiting Norway. It is also the south terminus for Hurtigruten, a popular voyage following the Norwegian coastline. Furthermore, Bergen is the center of music in Norway, the home or residence of artists and composers like Sondre Lerche, Röyksopp, Magnet, Kurt Nilsen, Datarock, Ralph Myerz & The Jack Herren Band, Kings of Convenience, Edvard Grieg and Harald Sæverud. A Spanish translation is in progress. There is a list of things to do on the article discussion page. To sum up, the article needs:
 * A map (the city is well covered on Open Street Map, so those with the necessary technical knowledge should be able to help out without knowing the city)
 * A thorough spell check and language cleanup (native English speakers, help out!)
 * More listings under most sections (check out the discussion page for ideas - much information can be found through Google)
 * A bit reorganizing
 * More/different pictures (there is a lot to be found on Flickr)

12 December - 18 December

 * Salem (Oregon)
 * Needs listings to be mos'd... currently looks like a phone book. Some pictures would be nice too – (WT-en) cacahuate  talk 22:14, 30 October 2007 (EDT)

5 December - 11 December
-- (WT-en) Tim (writeme!) 06:17, 8 August 2007 (EDT)
 * Delhi - a lot of info and a lot of good photos, and... a map! I'd love to see this as a DotM sometime soon
 * Needs a bit of an MoS tidy up
 * Having said that about the map, we need to put the main attractions etc on it now
 * Could do with putting the see/buy/eat into listings to get them uniform.

27 November - 4 December
-- (WT-en) Tim (writeme!) 09:13, 18 August 2007 (EDT)
 * Asmara - a lot of information on a relatively obscure destination.
 * Needs some photos.
 * Need to go through and convert (where appropriate) large blocks of text to listings.
 * Needs contact details for hotels/restaurants/sights
 * Needs a bit of MoS work
 * Needs actual local destinations in the get out rather than just advice and information

20 November - 26 November

 * Salzburg (city) -- -- (WT-en) Tim (writeme!) 14:54, 1 July 2007 (EDT)
 * One of 8 host cities for Euro 2008 in June/July 2008 - need to get into tip top shape by then.
 * Need to convert to listings to sort out MoS issues
 * Needs more detail in get in and get around.
 * Listings need contact details (phone numbers, addresses, websites)
 * Sleep listings need more info, in some cases there is none.
 * Get out doesn't link to Wikivoyage guides... :S
 * More photos and a map required.

31 October - 6 November
(WT-en) Cupcakecommander 04:28, 11 June 2007 (EDT)
 * Lankaran city - a great deal of information, nice history section, and a expansive transportation section but:
 * The page need. s a MoS clean up.
 * Hiking and more national park information need to be included from the surrounding area e.g. Isti Su, Hirkan National Park, etc
 * The get out section should have more ideas for possible options post-Lankaran (e.g. going to Iran, enjoying the hot springs in the south, sanatoriums, etc.)
 * The page would benefit from the expansion, revision, and creation of foreign language pages
 * More information on Lankaran and Talish culture should be included
 * Needs more photos
 * Lots of links but no good information
 * Fill out the Talish area in Azerbaijan!
 * Proof the new Japanese page

1 edit by 1 author Usable to Usable

24 October - 30 October 2007

 * Freetown - one of our more indepth articles in Western Africa and a good future Off the Beaten Path candidate
 * Needs a bit of MoS tweaking
 * Contact details required for hotels/eateries in Sleep/Do
 * Needs a few pictures of the sights and maybe a picture of the city itself.
 * Needs a bit of work on the wording
 * Needs some get out destinations

10 edits by 1 author, Usable to Usable

16 October - 23 October 2007

 * Dublin - Lots of info, potentially a star if we can sort the following out.
 * Needs more photos and a map. +
 * Get around needs breaking up into modes of transport +
 * See/do need contact details, more info, MoS +
 * Drink/Eat needs MoS +
 * Sleep needs MoS, contact details in some cases and more description +
 * Get out could do with being a bit more MoS

14 edits by 5 authors, Guide to Guide

9 October - 15 October 2007
13 edits by 2 authors (not counting edits to district articles), Usable to Usable
 * Manchester
 * Manchester - the districts have been recently redone, and need trimming and weeding
 * District articles need converting to listings
 * Find photos for each of the districts
 * Fix links on Manchester so that they point to the correct new district guide (See Talk:Manchester to see which old districts are covered in which new district.

01 October- 7 October

 * Hong Kong

Why
Used to be gorgeous, but is now nearly unreadable thanks to obsessive Wikipedian spoo, and districting is in tatters. (WT-en) Jpatokal 12:02, 5 June 2007 (EDT)

Result
3 edits by 2 authors, Guide to Guide

1 September - 7 September

 * Saint Petersburg (Russia) - huge tourist destination and the largest city in northeastern Europe by far, which is way too light on information, but easy to research --(WT-en) Peterfitzgerald Talk 23:14, 4 June 2007 (EDT)
 * Lots of MoS clean up
 * Lots of famous and less famous sights missing
 * Copy-edit as much of its content was written by non-native speakers
 * Do section is empty, but easy to research—the city has a world-class performing arts scene
 * As a city of 5 million, it might be a good idea to come up with a way to split the city into districts
 * Eat section needs a lot of work—there is a lot of good eating in this city
 * Understand section is very underdeveloped
 * It may be hard to acquire source material compatible with the copyleft, but a city map would be great; a hermitage map would be a big plus as well. If anyone could find suitable source material, I would be glad to do the map myself
 * Here is the official web city guide, with lots of info to mine

25 August - 31 August

 * Reno - lots of good info here but needs some cleanup and expanding --(WT-en) NJR_ZA 16:02, 4 June 2007 (EDT)
 * Needs a map
 * Should be upgraded to big city template. Work, Contact and Cope sections will be really useful.
 * General MoS clean up
 * HTML markup used should be removed
 * Information under Reno belongs in Reno
 * Calendar of events and festivals should be checked to ensure that all events listed under Reno is included there
 * Information under Reno needs contact details
 * Reno section is very small for a city of this size

0 edits by 0 authors, Usable to Usable.

18 August - 24 August

 * Alexandria - needs to be brought in line with our manual of style – (WT-en) cacahuate  talk 03:28, 23 May 2007 (EDT)

31 edits by 11 authors, Usable to Usable.

11 August - 17 August

 * Vienna -- -- (WT-en) Tim (writeme!) 14:54, 1 July 2007 (EDT)
 * One of 8 host cities for Euro 2008 in June/July 2008 - need to get into tip top shape by then.
 * I've mooted the possibility of breaking this up into districts here, and that's going to take a lot of ground work so a CotW would help with the copying and pasting into any district articles.
 * The whole thing could do with being converted to listings.
 * Contact details are needed for a lot of attractions.
 * Some of the information on listings might need to be trimmed, there could be too much description on some. Conversely, some do listings need more info.
 * Could do with info for the Contact and Cope sections.
 * Vienna Metro map is in French, needs to be converted to English.
 * A map would be great, and maybe a few more photos?

38 edits by 4 authors, Guide to Usable. (Note:Original guide rating was debatable)

4 August - 10 August 2007

 * Sheki rayonu and city

Why
- lots of info but:
 * The page needs a MoS clean up.
 * More hiking and historical sites need to be included from the surrounding area e.g. Marxal, Orta Zayzit, the Labyrinth etc.
 * The get out section should have more ideas for possible options post-Sheki
 * The page would benefit from the expansion, revision, and creation of the Japanese, and German pages.
 * The transportation guide needs to have updated prices
 * All of the marshrut routes are not listed
 * Needs more photos
 * Lots of links with no information -- (WT-en) Cupcakecommander 01:42, 10 May 2007 (EDT)
 * Combine with the Sheki page or expand the Kish page

Result
24 edits by 7 authors, Usable to Usable.

8 July - 3 August 2007

 * Puerto Vallarta

Why

 * needs a little work to conform to the Manual of style
 * Research phone #'s, websites, etc for a lot of the listings
 * organize or rewrite "Understand" section into a more digestible amount of info
 * reduce the bloated Stay safe section - doesn't need to be so sub-divided
 * "See" section is blank - surely there are some attractions to see here? – (WT-en) cacahuate  talk 13:38, 18 May 2007 (EDT)

Result
4 edits by 2 authors, Usable to Usable.

18 July - 24 July 2007

 * Geneva

Why
(WT-en) Tim (writeme!) 14:54, 1 July 2007 (EDT)
 * One of 8 host cities for Euro 2008 in June/July 2008 - need to get into tip top shape by then.
 * Need to convert to listings, which will fix the MoS problems on the guide.
 * There are 5 destinations in get out with no info about them. Need a sentence or two to explain why they would make good days out or places to move on to.
 * There are only two photos on the page, and the main one is pretty grainy... We need to get more and find a suitable replacement for the main one that is of higher quality.
 * There are a couple of listings without contact details/addresses, which need to be found and put into the guide.
 * A map would be useful.

Result
16 edits by 3 authors, Guide to Guide

11 July - 17 July 2007

 * Marrakech

Why
good but:
 * many sections need rewriting for more fluid prose.
 * some info needs to be moved into the main Morocco article
 * more photos would be nice - shouldn't be hard to find some that show the main square and the souqs – (WT-en) cacahuate  talk 03:06, 7 May 2007 (EDT)
 * contact details needed for some of the listings in see. -- (WT-en) Tim (writeme!) 05:51, 8 July 2007 (EDT)

Result
17 edits by 3 authors, outline to usable.

4 July - 10 July 2007

 * UNESCO World Heritage List - lots of red links - we should link to the nearest place where possible and be a bit more consistent on how we link. -- (WT-en) DanielC 16:52, 18 April 2007 (EDT)

 * In other words, determine for each listing if it qualifies for its own article as per Project:What is an article, and if not, then list it as Name of attraction in Name of nearest city – (WT-en) cacahuate  talk 03:30, 21 May 2007 (EDT)

Results
51 edits by 8 users (plus an unknown number on guides for UNESCO World Heritage sites.

26 June - 2 July 2007

 * Cincinnati

Why
Currently a star nomination, in case anyone other than Gorilla Jones hasn't noticed. I'd like to fix things that I'm missing, including:
 * Reformatting the hours to conform with MoS.
 * Checking grammar and making the guide a little more enjoyable to read
 * Pointing out any other issues on Project:Star nominations -- (WT-en) Sapphire • (Talk) • 21:22, 22 June 2007 (EDT)

Results
103 edits by 7 users, Guide to Guide

12 June - 25 June 2007

 * Seattle

Why
good article with lots of info, but could use some tlc:
 * Districts need to be further hashed out - is this the best way to divide them? If the map is a good base to go on, then make the list and the district articles match it exactly.
 * MoS / template the listings, and then move to appropriate district articles.
 * Write brief overviews of what's to be found in the city for the sleep, eat and drink sections once listings are moved.
 * Needs a street map.
 * MoS / template the listings in the district articles – (WT-en) cacahuate  talk 02:18, 2 April 2007 (EDT)

Result
15 edits by 10 authors, Guide to Guide

4 June 2007 - 10 June 2007

 * San Diego

Why
An extremely popular tourist destination, but the article is lacking a lot. Five things I suggest:
 * Grammar and Manual of Style cleanup,
 * See listings should really be expanded,
 * District articles need a lot of work,
 * Eat/Sleep sections could use a lot of work,
 * More descriptions of vital things, like more on how to Get Around. There is also nothing in the Cope section. (WT-en) PerryPlanet 22:18, 13 February 2007 (EST)

Results
6 edits by 5 authors, Usable to Usable

28 May 2007 - 3 June 2007

 * Baku

Why
-- Would be the first place in the Caucasus to be a CotW -- (WT-en) Cupcakecommander 06:20, 6 February 2007 (EST)
 * Eat/drink/buy sections need more work.
 * The page needs a MoS clean up.
 * A great deal of the attractions are missing.
 * A new city map (like the ones in fountain square).
 * The page would benefit from the expansion and creation of the Japanese, English, and German pages.
 * Transportation guide
 * Needs more photos

Results
49 edits by 4 editors Usable to Guide

21 May 2007 - 27 May 2007

 * Austin

Why
Eat/drink/sleep sections need MoS, contact details... Needs more photos/map -- (WT-en) Tim 13:36, 28 January 2007 (EST)

Results
27 edits by 5 authors, Usable to Usable

14 May 2007 - 20 May 2007

 * Hyderabad

Why
Needs MoS, contact details, remove some photos (?), sort out huge list in "do" to become useful information rather than just a list... -- (WT-en) Tim 13:36, 28 January 2007 (EST)

 * Research info for listings that are now just a list of names
 * Get it into shape so (WT-en) Ravikiran has something to use when he gets to town! – (WT-en) cacahuate  talk 02:38, 7 May 2007 (EDT)

Result
131 edits by 6 authors, Usable to Usable

7 May - 13 May 2007

 * Prague

Why
Has a lot of information and there's a lot of scope for doing small easy edits. Article needs MoSing. Also needs splitting into districts. A lot of listings have no information or contact details. Could do with a few more photos/map. -- (WT-en) Tim 13:36, 28 January 2007 (EST)

Result
8 edits by 5 authors, Usable to Usable

26 April - 2 May 2007

 * Mauritius

Why

 * Lots of good info, needs to be moved into regions and cities. General MoSing (WT-en) Maj 22:16, 21 December 2006 (EST)
 * The ja: page for Mauritius (a former DOTM) has lots of nice pictures that could also be integrated. (WT-en) Jpatokal 22:43, 21 December 2006 (EST)

Result
26 edits by 9 authors, Outline to Outline

18 April - 25 April 2007
Puerto Rico and regions/cities.

Why
Wikivoyagers will be spending part of the time here for the Wikivoyage Collaboration Confabulation. -- (WT-en) Sapphire 03:11, 10 April 2007 (EDT)

Result
17 edits by 7 authors, Usable to Usable

10 April - 16 April 2007

 * Beaches in Goa and Goa

Why
needs to be re-organized along geographical lines. --(WT-en) Evan 07:38, 15 December 2006 (EST)

Results
Goa: 6 edits by 4 authors, Outline to Outline.

Beaches in Goa: 0 edits by 0 authors, Outline to "Merge into Goa" suggestion.

2 April - 9 April 2007
Paris/4th arrondissement

Why
This article was declared a star before the current star nomination process was implemented, and when our standards for a star article were more relaxed... it's needs several things to get it up to par, including the following:
 * Get In is simply a list of subway stations
 * Get Around is sparse
 * Listings need to be templatized (drink and sleep sections are only ones left to do)
 * The last two sleep listings have no prices mentioned
 * The eat/drink sections need opening hours and meal prices, and all listings should have descriptions
 * The closest Metro station should be mentioned for every listing, in a city like Paris you can never be more than 400m away from a station.
 * Punctuation is a bit lousy at places.
 * Buy - should be expanded and descriptions, hours, etc for all listings
 * The "Do" section needs informative descriptions for the things listed

Let's get this article in shape so that we can renominate it for Star status, it's not that far off! – (WT-en) cacahuate  talk 00:13, 31 March 2007 (EDT)

Result
3 edits by 1 author, Guide to Guide

26 March - 1 April 2007

 * Munnar

Why
Another page with lots of info that's way off of our MoS. --(WT-en) Evan 09:45, 5 December 2006 (EST)

Results
6 edits by 2 authors, Outline to Outline

18 March - 24 March 2007

 * Cambridge (England)

Why
Content is very good and there's a lot of it. Needs a lot of MoS work though. Potential star/DotM. -- (WT-en) Tim 07:31, 26 November 2006 (EST)

Result
10 edits by 4 authors, Guide to Guide

8 March - 14 March 2007

 * Fort Lauderdale

Why
Needs some content and MoSing. Needs photos and maps. Food/Hotels/nightlife needs to be broken down with more detail. Maybe combine with Miami for South Florida? (WT-en) GatorFTL 5:51, 22 November 2006
 * Sleep section needs to be organized into budget/mid-range/splurge... looks like the yellow pages at the moment.
 * All listings could be templatized
 * A lot of the attractions and listings in eat and drink need more contact info, descriptions
 * Do we need such a huge list of radio stations?
 * Eat listings should be organized by budget/mid-range/splurge rather than by area (WT-en) - Cacahuate 13:38, 18 February 2007 (EST)

Result
18 edits by 6 authors, Usable to Usable

26 February 2007 - 4 March 2007

 * Birmingham (England)

Why
Good content. Needs MoS work, more get out. Potential DotM/star contentwise. -- (WT-en) Tim 07:28, 26 November 2006 (EST)

Result
5 edits by 4 authors, Guide to Guide

19 February 2007 - 25 February 2007

 * Maui

Why
Needs all the listings shifted to correct city pages. (WT-en) Maj 17:21, 11 December 2006 (EST)

Result
2 edits by 1 author, Usable to Usable

12 February 2007 - 18 February 2007

 * Valencia (city)

Why
In reasonable shape in most regards, but needs MoS work, entries for "Buy," and many more "Sleep" options. As with most articles, maps and illustrations (which shouldn't be too hard to find) are also needed. The goal is to get this into DotM shape in time for the 2007 America's Cup. -- (WT-en) Bill-on-the-Hill 21:11, 22 November 2006 (EST)

Result
31 edits by 4 authors, Outline to Usable

2 February 2007 - 11 February 2007

 * Caracas

Why
Needs content and MoS editting, especially more hotels and nightlife 84.178.179.131 03:23, 14 November 2006 (EST)
 * Contact details are needed for hotels, restuarants and bars. Addresses/locations are needed for most of the attractions. Contact and cope needs filling. -- (WT-en) Tim 13:13, 28 January 2007 (EST)

Result
12 edits by 4 authors, Outline to Usable

26 January 2007 - 1 February 2007

 * Bangor (Wales)

Why
Listings need MoSing, few more pictures, some sections need rewriting. Plus, I don't think we've had any Welsh CotWs so far... (WT-en) Tim 19:03, 25 October 2006 (EDT)

Result
28 edits by 5 authors, Usable to Usable

19 January 2007 - 25 January 2007

 * Rome

Why
A lot of content, needs to be broken into districts. Someone who knows the town might need to oversee and organise this. (WT-en) Tim 08:31, 25 October 2006 (EDT)
 * Various listings need to be MoS'd. Certain listings need addresses/phone numbers/websites. Drink section needs list of good bars/pubs/clubs. Needs more pictures and a map. Eat section needs a description of "In Rome you can ask for" - what are you asking for?!! Needs more shop/market listings in Buy. See/Do needs sorting out and contact details. -- (WT-en) Tim 11:33, 17 January 2007 (EST)
 * Seems to have been broken into a number of districts, perhaps even too many? Can any of these be combined into groups that make sense to the traveler, or is each actually worthy of it's own article?
 * Listings could be templatized to better conform to the Manual of style.
 * A district map (if not a full city map!) would be useful in understanding how the city is broken down. (WT-en) Cacahuate 02:22, 19 January 2007 (EST)

Result
10 edits by 3 authors, Usable to Usable

2 very minor edits to 1 of the district articles by 1 author.

12 January 2007 - 18 January 2007

 * Madrid

Why
Alot of content, but needs MoS editting, more contact details. I find it surprising that a city of Madrid's size doesn't have a better article. (WT-en) Tim 23:19, 17 August 2006 (EDT)

Result
9 edits by 3 authors, Usable to Usable

2 January 2007 - 11 January 2007

 * Pune

Why
Lots of info, but in desperate need of reorganizing and editing. (WT-en) WindHorse 06:57, 4 December 2006 (EST) Support for CoW. The info is excellent, and the article is v. informative. With a little editing, this can easily become a star. Besides, Pune is a great city, with a laid-back yet vibrant atmosphere. The ideal place to relax after touring the big metros. History, atmosphere, art, culture, it's all there. Virtual Pune and Pune Diary are both good sources of info. Pune City is the official website. (WT-en) Upamanyuwikivoyage 09:17, 11 December 2006 (EST)
 * The Do section can be edited. Not enough info.
 * The Get Around section needs more info on Hiring cars, motorbikes and cycles.
 * In desperate need of good pics. Map also req.
 * Cope sec required
 * Listings req tel nos, price, opening hours etc.

Results
14 edits by 5 authors, Star nomination to Guide

title: Wikivoyage:Previous collaborations/2007


text:
Wikivoyage:Previous collaborations/2008

This page lists previous collaborations for 2008.

December 2008

 * Gold Coast Needs:
 * More images
 * A map
 * More listing(s)
 * Complete listings
 * Much more in the do

Keep smiling, (WT-en) edmontonenthusiast [ee] .T.A.L.K. 13:09, 17 November 2008 (EST).

(WT-en) Sertmann 09:03, 5 September 2008 (EDT)(WT-en) Sertmann
 * Azores Has an amazing wealth of really interesting information, but it's one big mess, and an interesting European destination for a change (see above) :-)
 * Needs grammar & spelling overhaul, and be whipped into standard MoS
 * Lacks Eat & Sleep entries
 * Lacks Pictures
 * Needs a map
 * Needs Climate info

 * Santiago de Chile - (WT-en) Tarr3n 08:40, 5 September 2008 (EDT)
 * Some pictures would be nice, or even a map?
 * Some of the ditricts are a bit sparse, those that do have info could do with a bit of MOS work.
 * No Get Out section. This is the capital so you would expect many travellers to spend a few days here and move on, perhaps for that great climbing that gets a brief mention?
 * Contact - are there any internet cafes?
 * Cope - embassies/consulates? Laundry?
 * There's a decent amount to See, but not an awful lot to Do.

November 2008

 * Tripoli (WT-en) Tarr3n 09:00, 5 September 2008 (EDT)
 * Some good stuff in this article - I want to go there just on the basis of the description of the airport!
 * Eat, Drink and Sleep could all do with a lot more info. Drink in particular - fair enough alcohol is forbidden, but what about tea shops or coffee bars?
 * Buy - There are no big brand shops present in Triopli just yet - brilliant! Tell me more about what is there. I want to go before Zara, H&M and Tesco take over.
 * Contact and Cope are blank at the moment.
 * There must be more to See and Do. What about those multiple sites of archaeological significance mentioned in Understand?
 * Some more pictures? A map?

(WT-en) Hypatia 23:52, 4 October 2007 (EDT)
 * Ko Lanta. Reasonably good, popular northern summer destination in Thailand:
 * Needs a MoS clean up.
 * Needs the addition of cheaper, backpacker budget accommodation, almost everything there is mid range or luxury.
 * Needs better coverage of Lanta Old Town
 * Needs better coverage non-diving activities; there are, I believe, snorkeling tours and kayaking and so on being left out, plus elephant rides
 * Could use a map showing the various beaches at least on the western side where the resorts are.

 * Buffalo National River
 * Under Get in, change the map from an external link into an embedded image.
 * Expand the Eat and Drink sections.

October 2008

 * Antarctica —

Why
it's odd to nominate a continent, but this collection of articles really doesn't need that much to go from usable --> guide (and thus becoming both our first guide-level region & continent!) It would also be a really fun destination to collaborate on, I think. --(WT-en) Peter Talk 15:27, 12 August 2008 (EDT)
 * Remove unnecessary sections
 * Research (research is mostly what's needed)
 * More information about "get around," i.e., what sorts of transportation are feasible, how much it costs to get equipment, and what sort of level of physical fitness one needs
 * More information re: specialty tours throughout the continent
 * Penguin photos (preferably ones where researchers have mischievously dressed them up with top hats, scarves, & Santa beards) (I'm not joking)
 * Need to create a basic South Shetland Islands page
 * Come up with basic descriptions for non-article subregions (like Victoria Land, etc.)

Result
20 edits by 10 users

 * São Paulo

Why
lots of information, listings (WT-en) Tim (writeme!) 12:16, 12 August 2007 (EDT)
 * Some bits of info are in the wrong place
 * Districts need rethinking and then listings need to be placed in them
 * Needs a map and some photos

Result
30 edits by 8 users

 * Zaqatala city - located in the Sheki region of Azerbaijan, with friendly, open, and liberal people:

Why

 * The page need's a MoS clean up
 * The get out section should have more ideas for possible options for trips after Zaqatala
 * The page would benefit from the creation of foreign language pages
 * There is hiking in Zaqatala, but nothing writen about it
 * Fill out the Sheki area in Azerbaijan! (WT-en) Cupcakecommander 02:42, 21 May 2008 (EDT)

Result
2 edits by 1 user

September 2008

 * Little Rock (North America)

Why

 * Needs maps and pictures. —The preceding comment was added by (WT-en) 70.232.65.60 (talk • contribs)

Result
9 edits by 7 users

 * Beijing (Asia)

Why

 * it's the Olympic City come August 8th. Wikivoyage's page should be up-to-date and helpful!
 * There's a lot of recent public transportation infrastructure that's been added and should be explained.
 * The Beijing 2008 Olympic page sucks and needs reworking.
 * MoS clean-up.
 * Restaurants should be ordered in a more meaningful way.
 * List of things to Do seems very small for a city with >15m residents.
 * Get Out list should be longer to suggest daytrips away from the city.
 * If the sights could be grouped by location that might help planning visits. --(WT-en) Julian Suddaby 06:11, 11 July 2008 (EDT)

Result
18 edits by 10 users

 * Calabar (Africa)

Why

 * Needs a serious dose of the MoS – (WT-en) cacahuate  talk 23:35, 19 November 2007 (EST)

Result
9 edits by 5 users

6 August - 13 August

 * Edmonton
 * A ton of great information that's strong in ways a lot of articles are weak (especially a terrific range of restaurants), but the sections aren't MoS and it's a bit disorganized. Listings are almost all incomplete. Could be a strong guide with some help. (WT-en) Gorilla Jones 20:05, 25 June 2007 (EDT)

26 June - 2 July

 * Kathmandu
 * A major stop for travelers in South Asia. Currently, the article has lots of info, even a map, but needs some effort to tighten and pull it into shape. (WT-en) WindHorse 23:39, 25 June 2007 (EDT)

7 May - 25 June

 * Harbin

Why

 * A good article that has been nominated for Destination of the month. To meet the criteria it needs a general work over. (WT-en) WindHorse 12:15, 14 June 2007 (EDT)

Results
4 edits by 3 authors, Guide to Guide

30 April - 6 May

 * Khachmaz

Why

 * A great deal of information, nice history section, and a expansive transportation section but:
 * The page need. s a MoS clean up.
 * The get out section should have more ideas for possible options post-Khachmaz(e.g. going to Russia, exploring Guba, sanatoriums in Nabron, etc.)
 * The page would benefit from the creation of foreign language pages
 * More information on Lesgi culture should be included
 * Needs more photos
 * Fill out the Northeast area in Azerbaijan!

Results
2 edits by 2 users, Usable to Usable

23 April - 29 April

 * Boston

Why

 * Major tourist destination in the USA (18 million in 2007 according to this article)
 * Only one photograph of the city, and no street map
 * District pages are very uneven; some are pretty decent, while others are just stubs
 * Many entries in See, Do, Buy, and Eat sections that should be moved to their respective district pages
 * Includes attractions in the neighboring town of Cambridge; these all need to be moved to the Cambridge page
 * Get in and Get around sections need cleanup: the information there is good, but needs to be condensed, as these sections are too wordy right now
 * No mention of discount programs available to tourists like the Go Boston Card and the Boston CityPass
 * May want to add a Respect section, e.g. mocking the Boston accent is not a good idea, nor is referring to Boston as a racist city based on events from 30 years ago – (WT-en) Jimby 23:39, 27 March 2008 (EDT)

Results
6 edits by 4 users, Guide to Guide

16 April - 22 April

 * Berne -- -- (WT-en) Tim (writeme!) 14:54, 1 July 2007 (EDT)

Why

 * One of 8 host cities for Euro 2008 in June/July 2008 - need to get into tip top shape by then.
 * Convert to listings, to get a uniform style.
 * Need addresses, phone numbers and websites (if poss) for drink section.
 * Need more sleep listings
 * Need some info in cope and contact
 * Put details of destinations in get out and rough travel times to them.
 * Find some more photos

Results
62 edits by 3 users, Usable to Usable

9 April - 15 April

 * Basel -- -- (WT-en) Tim (writeme!) 14:54, 1 July 2007 (EDT)

Why

 * One of 8 host cities for Euro 2008 in June/July 2008 - need to get into tip top shape by then.
 * Convert to listings, in order to get the guide to fit the MoS.
 * Stay safe section could do with main points being boldened.
 * A map would be really useful.

Results
Basel 0 edits by 0 users, Guide to Guide

2 April - 8 April

 * Innsbruck -- -- (WT-en) Tim (writeme!) 14:54, 1 July 2007 (EDT)

Why

 * One of 8 host cities for Euro 2008 in June/July 2008 - need to get into tip top shape by then.
 * Get in and get around could do with more info.
 * Need some listings in the eat and drink, and more in the sleep (currently there is one campsite.)
 * There seems to be more info in de:Innsbruck - it might be the same, but if not we can add it to the english guide.
 * Convert to listings, which will fix MoS problems.
 * Put more info in get out
 * A map would be great, as would a few more descriptive photos of the city.
 * Basic information about the town would be useful for those of us who like to know a tiny bit about the town before we visit it, i.e. what's so special about Innsbruck in the first place? The fact that it's the fifth largest city in Austria doesn't make me want to visit!

Results
3 edits by 2 users, Guide to Outline to Outline

19 March - 01 April

 * Euro 2008

Why

 * The high-level travel topic for Euro 2008 could use help too. It's currently written from a Swiss point of view and needs Austrian info to provide balance, mainly in the following sections: Get in, Get around, Buy, Do, Stay safe, Get out.
 * (WT-en) WTDuck2 16:22, 21 January 2008 (EST)
 * Two and a half months to go, about time we get this one in order --(WT-en) Nick 04:51, 11 March 2008 (EDT)

Results
7 edits by 4 users, No status to No status

12 March - 18 March

 * Disneyland Paris
 * This article is currently usable. I think with the addition of maps and pictures it could be pushed up to guide or star.
 * Make it flow with the layout of the Disneyland and Walt Disney World articles.
 * We need a picture of the Walt Disney Studio Park.
 * Three maps: the entire Disneyland Paris Resort, Disneyland Park, and Walt Disney Studios.
 * Make the See and Do lists more diverse, and emphasize that there are two parks.
 * Most importantly, make it a guide article, if not star.

Results
12 edits by 3 users, Usable to Usable

5 March - 11 March

 * Walt Disney World

Why

 * This article is currently usable. I think with the addition of maps and pictures it could be pushed up to guide or star.
 * Four maps, one for each of the theme parks.
 * A map of the Orlando area showing the location of WDW.
 * A map of the entire WDW resort.
 * Pictures of the theme parks.
 * Under "About The Park": The "Magic Kingdom" subsection has two sub-subsections ("Wheelchairs and strollers" and "Restrooms") that don't tie in right. They should be moved to more appropriate subsections.
 * Most importantly, push it up at least to guide, if not star.

Results
33 edits by 7 users, Usable to Usable

20 February - 4 March

 * Disneyland

Why

 * This article is currently usable. I think with the addition of maps and pictures it could be pushed up to guide or star.
 * We need four maps: One of the entire resort, one of Disneyland, one of California Adventure, and one of Downtown Disney.
 * Also, at least three pictures. My picks: Sleeping Beauty's Castle and the Main Street train station in Disneyland, the California Screamin' roller coaster and the Golden Gate Bridge in California Adventure, and the monorail.
 * Under "Sleep": change the map from an external link to an embedded image.
 * Most importantly, upgrade it to guide, if not star.

Results
21 edits by 11 authors, Usable to Usable

6 February - 12 February

 * Zurich -- -- (WT-en) Tim (writeme!) 14:54, 1 July 2007 (EDT)

Why

 * One of 8 host cities for Euro 2008 in June/July 2008 - need to get into tip top shape by then.
 * More info needed in Get in/by car & by bus.
 * Get around needs splitting into more subsections, ie by bus, by tram etc rather than just by public transport.
 * The whole guide needs converting to listings
 * The see, do, eat and drink sections need phone numbers, addresses, websites
 * Need more photos and a map.

Results
10 edits by 6 author, Usable to Usable

title: Wikivoyage:Previous collaborations/2008


text:
Wikivoyage:Privacy policy

de:Wikivoyage:Datenschutz fr:Wikivoyage:Politique de confidentialité it:Wikivoyage:Informazioni sulla privacy nl:Wikivoyage:Privacybeleid ru:Wikivoyage:Политика конфиденциальности sv:Wikivoyage:Personuppgifter

title: Wikivoyage:Privacy policy


text:
Wikivoyage:Photographs of identifiable people

In general, Wikivoyage's image policy discourages people in photos. Please resist the temptation to pose your travel companion in front of every landmark in every photo. The Wikicommons policy on photographs of identifiable people also applies. Identifiable people carry personality rights quite apart from the image's copyright.


text:
Wikivoyage:Community portal

The community portal is a central place for working together on Wikivoyage. Are you new to the project? Welcome! Wikivoyage is the free worldwide travel guide that you can edit. Start contributing right now – we need your knowledge, your experience, your talent, and your attention. If you want to get more involved in the project, start out by reading through the links on this page, including our goals and the Manual of style. If you still have questions, just ask! We're hanging out in the pub. Virtual drinks on the house!

Communications
 * Requests for comment
 * This page is for requests of additional feedback on ongoing discussions on policies, article content or other matters.

 * Travellers' pub
 * The place to ask questions when you're confused, lost, afraid, tired, annoyed, thoughtful, or helpful.

 * Roadmap
 * Future short-term and long-term plans for Wikivoyage.

 * Multilingual discussion
 * The Lounge on Meta where matters are discussed with users of other language versions of Wikivoyage. Communication takes place in English.

 * Celebrate a contribution
 * This is the place where you can share news of your completed piece of work — and invite the community to celebrate your milestone in contributing to Wikivoyage.

 * Social media
 * Share articles on Facebook and Twitter.

 * IRC channel
 * #wikivoyage Wikivoyage IRC channel.

 * International mailing-list
 * wikivoyage-l (this month).

 * Phabricator
 * Phabricator: Wikivoyage bug reports and feature requests.

Community
 * Featured collaboration
 * (No active project at the moment.)

 * Destination of the month candidates
 * On this page we determine which articles are featured on the main page as "destination of the month". There is a separate category for less visited destinations and for travel topics.

 * Discover
 * Strange but true trivia about destinations around the world. You can add or edit fun facts to this list that will appear on the main page in the near future.

 * Expeditions
 * Expeditions (or WikiProjects) help Wikivoyagers collaborate and organize around certain subjects, be they based on shared interests, geography, or shared skills.

 * Nominations
 * Script nominations
 * Star nominations
 * User rights nominations
 * User ban nominations
 * Vandalism in progress

Policies and guidelines
 * The traveller comes first
 * The core underlying principle of Wikivoyage is that it is written for the benefit of travellers. The question "what is best for the traveller" should always guide decision making.

 * Goals and non-goals
 * Our goal is to create a free, complete, up-to-date and reliable world-wide travel guide. This policy page gives you important information on what we are, and what we are not.

 * Consensus
 * In Wikivoyage, almost all decisions are made by achieving consensus rather than voting — so state your arguments and build consensus for debatable matters.

 * Plunge forward
 * Don't worry about being perfect or making mistakes. If something needs to be done, do it. Jump in and make useful edits to articles.

 * Manual of style
 * Our Manual of style is a collection of rules of thumb and guidelines for giving Wikivoyage articles a consistent look and feel.

All policies and guidelines...

Help and tutorials
 * Quick contribution guide
 * This guide provides suggestions for making your first contribution to this wiki. In general it is best to start out by contributing a listing for your favorite attraction, restaurant, or bar rather than trying to create a new article or make formatting changes to an existing article.

 * Tips for new contributors
 * This page gives a set of tips and tricks that might help you get up to speed working on Wikivoyage articles and participating in the Wikivoyage community.

 * Arrivals lounge
 * Here is where new contributors can post questions to be answered by experienced contributors.

 * How to draw static maps and dynamic maps
 * In this age of satellites and GPS, you no longer need to be a professional cartographer to draw an accurate map. The static map tutorial gives instructions for creating standard Wikivoyage maps using Inkscape, while dynamic maps are generated from (lat, long) co-ordinates on OpenStreetMap base maps. Complete amateurs have created some of our best maps following this guide.

 * How to re-use Wikivoyage guides
 * Wikivoyage articles and images are available under a copyleft license. This means you can redistribute and modify them in any medium, as long as you follow a few simple rules. This page gives an overview on how to re-use Wikivoyage content by third parties.

All help pages...

Content organization
 * Requested articles
 * A list of articles that do not yet exist on Wikivoyage. Are you familiar with one of the topics listed? Plunge forward and share your knowledge!

 * Improvements
 * Articles needing style fixes
 * Articles needing translation
 * Merge articles
 * Move listings to cities
 * Move listings to districts
 * Pages without custom banner images

 * Syntax
 * Broken redirects
 * Double redirects
 * Orphaned pages
 * Pages with broken file links
 * Uncategorized pages

 * Deletion issues
 * Articles for deletion, Candidates for speedy deletion
 * Copyright violations

All articles needing attention...

title: Wikivoyage:Community portal


text: Wikivoyage:Protected page

title: Wikivoyage:Protected page


text:
Wikivoyage:Protected page policy

 * Click here for a list of currently protected pages

The revolutionary nature of Wiki is the ability for any reader of any article to edit that page right now. Wiki is the enabling technology that is making Wikivoyage into a really great travel guide. Wikivoyagers know that we need to keep Wikivoyage open and available to make it succeed. We depend on the distributed effort of the millions of people on the Internet to get high-quality, up-to-date and reliable articles. Whenever possible, we prefer to counteract abusive actions by some users with the ability of other users to edit a page. However, in some circumstances, it may be necessary to protect a page on Wikivoyage.

When a page is fully protected, it can be edited only by administrators. This is an extreme measure and shouldn't be applied lightly.

When a page is semi-protected, it can be edited by autoconfirmed users, but not anonymous users or logged-in users who registered their account less than 4 days ago.

Reasons to protect a page
Administrators may protect a page whenever they feel that this step is warranted. They are expected to use their judgement, and to err on the side of openness.

Example reasons why a page should be permanently fully protected are:

 * The text of the page must remain verbatim on the site. An example is the Full text of the Attribution-ShareAlike 3.0 license, which is a legal document not open to interpretation by Wikivoyagers.
 * A policy page has legal ramifications for the Wikivoyage project. Some policy is important to the continued existence of the project and the livelihoods of Wikivoyagers. If these pages are repeatedly compromised, they should be protected.
 * Non-human spambots occasionally hammer away creating pages that are not and can never be valid Wikivoyage articles (eg. Talk:Bangalore/; note the slash at the end). Such pages can be permanently protected from creation.

Reasons for temporary full protection include:
 * An out-of-control edit war is underway. If two or more Wikivoyagers are involved in an extended edit war over a page and are unable or unwilling to discuss the issue on the appropriate talk page, an administrator can use the page protection feature to declare a cooling-off period on the article until contributors are willing to talk out their differences. Administrators should not protect a page if they are personally involved in the edit war; they should ask another administrator to do it instead.  It's preferred that the participants be cautioned before such a step is taken, rather than simply pre-emptively protecting the page; actual protection of the page should really be a last resort.
 * A page is subject to repeated vandalism. This is a special case of the edit war; if a user is repeatedly and systematically vandalising a page, it should be protected until the user gets their head straight, or they wander away, or they get blocked or banned.
 * A page causes a security risk for Wikivoyage. Hopefully the MediaWiki software is robust enough to deal with simple security attacks through the Wiki interface, but if in some case it's not, administrators should take the step of protecting the page.

Process for protecting a page
Before or immediately after protecting a page, the administrator should note the protection on the accompanying talk page, and add a link on the protected pages page, with a justification for why the page was protected. Other Wikivoyagers can and should comment on the protect action there, but it's not the place for discussing the particulars of an edit war.

If the protect action isn't in the above list of reasons, it should be strongly defended and the reason should be added to the above list.

A page should be unprotected as soon as it's feasible. When a page is unprotected, a note to that effect should be put on the protected pages page.

title: Wikivoyage:Protected page policy


text:
Wikivoyage:Protected pages

 * See also: Special:Protectedpages and Protected page policy

A list of protected pages on Wikivoyage can be found on Special:ProtectedPages.

A fully protected page can be edited only by administrators. Semi-protected pages can be edited by any autoconfirmed user, but not anonymous or newly registered users. Template editor protected pages lie in between the two and can only be edited by template editors and sysops.

title: Wikivoyage:Protected pages


text:
Wikivoyage:Pseudo-phoneticization guide

This guide provides suggestions for making pseudo-phonetic pronunciation cues for Wikivoyage phrasebooks. The goal is to make somewhat phonetic suggestions that could be read aloud according to English spelling rules to make the correct sounds.

This guide is intended for editors who are writing articles. You can find a simplified guide for readers at Pronunciation guide.

Basic rules
The basic rules for pronunciation cues are as follows:

 * Build up the cues from the pronunciation alphabet below.
 * Separate words in the cue by spaces.
 * English "I love you" → igh luhv yoo
 * Separate syllables in a word by hyphens.
 * English "over" → oh-vuhr
 * Use ALL CAPS to show syllables that are emphasized.
 * English "emphasize" → EHM-fuh-sighz
 * Leave off terminal periods ("."), but leave in terminal question marks ("?") or exclamation marks ("!").
 * English "It's OK." → ihtz oh-KAY
 * English "What's your name?" → WUHTZ yoor NAYM?
 * English "Help!" → HEHLP!
 * Avoid the temptation to use English words in their entirety. Mixing words and phonetics makes it hard for a reader to tell how to pronounce phoneticizations that look like English words.
 * Spanish "hay" → igh, not eye
 * French "six" → seess, not cease

Pronunciation alphabet
The following alphabet shows how we like to represent sounds in Wikivoyage phrasebooks. Try to find the sound you're trying to approximate in the definitions, and then use the representation given. These are rough approximations; fine points of pronunciation can be glossed over, unless there's a risk of being misunderstood.

If there's a sound in the language you're trying to provide pronunciation cues for that isn't represented, add a representation here.

 * a : like 'a' in English "hat"
 * ah : like 'a' in English "father"
 * aw : like 'aw' in (British) English "dawn"
 * ay : like 'ay' in English "hay"
 * b : like 'b' in English "bird"
 * ch : like 'ch' in English "chin"
 * ck : like 'ck' in English "kick" (end of syllable only)
 * d : like 'd' in English "dog"
 * dh : like 'th' in English "those"
 * ee : like 'ee' in English "knee"
 * eh : like 'e' in English "bed"
 * eu : like 'eu' in Dutch "keuken" and French "heureux"
 * f : like 'f' in English "fun"
 * g : like 'g' in English "go"
 * gh : a voiced version of 'ch' in Scottish "loch"
 * h : like 'h' in English "hand"
 * ih : like 'i' in English "pin", "hit"
 * igh : like 'i' in English "time"
 * j : like 'j' in English "jump", like "dg" in English "edge"
 * k : like 'k' in English "kiss" (beginning of syllable only)
 * kh : like 'ch' in Scottish "loch"
 * ks : like 'x' in English "extra"
 * l : like 'l' in English "love"
 * ll : like 'll' in English "mill" (end of syllable only)
 * ly: like 'lli' in "million"
 * m : like 'm' in English "me"
 * n : like 'n' in English "nose"
 * ng : like 'ng' in English "sing"
 * ny : like 'ni' in English "onion"
 * o : like 'o' in (British) English "lot"
 * oh : like 'o' in English "hope"
 * oe : like ö in German "Königsberg," a bit like i in sir
 * oo : like 'oo' in English "moon"
 * ow : like 'ow' in English "cow"
 * oy : like 'oy' in English "boy"
 * p : like 'p' in English "push"
 * r : like 'r' in English "row"
 * rh : like 'r' in French "français"
 * rr : like 'rr' in Spanish "perro"
 * s : like 's' in English "sun" (beginning of syllable only)
 * sh : like 'sh' in English "shed", "mush"
 * ss : like 'ss' in English "hiss" (end of syllable only)
 * t : like 't' in English "top"
 * th : like 'th' in English "thin"
 * u : like 'u' in English "push"
 * uh : like 'u' in English "bud", 'a' in English "comma" (schwa)
 * uu : like 'u' in Dutch "nu", like 'ut' in French "salut"
 * uy : like 'ui' in Dutch "huis", like 'œ' in French "œil"
 * v : like 'v' in English "vase"
 * w : like 'w' in English "win"
 * y : like 'y' in English "yes"
 * z : like 's' in English "has", 'z' in English "zero"
 * zh : like 's' in English "treasure"

title: Wikivoyage:Pseudo-phoneticization guide


text: Wikivoyage:Quick big city article template


text:
Wikivoyage:Quick contribution guide

You can make a valuable contribution to Wikivoyage in just five minutes. However, before you start, be aware that the Wikivoyage copyleft allows your contributions to be used elsewhere, edited by others, and even copied or sold as long as you are given proper attribution. Please contribute!

Plunge forward

 * 1) What to add.  Choose any attraction, park, view, bar, pub or restaurant that you are enthusiastic about and would like to share information about.  It should be somewhere you know and have visited, but it doesn't matter if you have been there while travelling, or if it is in your local area.  You don't have to be an expert.  Your experience and perspective is valuable to others like you.
 * 2) How to describe it.  Decide what type of person would like to visit, and what are the features that would make them want to visit.   Everybody has different interests, from birdwatching to adventure sports, from quiet country pub to the latest urban beats.  Help travellers find what they like.  If you like it, what are your interests that make you like it?  If you know the best way to get there, or the best time to experience it, add that too.  Don't use I, me, us, or we in the description.  Don't hesitate to use you, though, when addressing the reader.
 * 3) Find the right article.  Wikivoyage articles are named after the geographical location.  Select the best article based on where the attraction is.  If it is outside of a town, you might have to place it where travellers would normally stay when visiting it.
 * 4) Find the right section.  See for sights.  Do for activities.  Drink for nightlife, pubs and bars, Eat for restaurants, cafes, and fast food. Learn more in Where you can stick it and standard article sections guide.
 * 5) Add your entry.  If you aren't familiar with editing a wiki, you can just click "add listing" next to the appropriate section heading to add a new entry, or "edit" next to an existing listing to edit that entry.  You will then see a dialog box with fields like "name", "address" and "content" for your new entry.  Just fill out the name, hours, description, etc and then click "Submit" to save your changes.
 * 6) All done.  That's it for now.  Your information is now in the guide for all to see, in less than five minutes.

Avoid
If you only have five minutes try to avoid:
 * Changing section headings – even if you don't like them. Wikivoyage uses a standard template for each article.  You are welcome to suggest changes, but count on spending more than five minutes  convincing us to change them.
 * Creating a new article. If you only have five minutes, use it wisely by adding content and not creating new articles – it's because our regional structure can take a little more than five minutes to come to terms with. So just find the closest or best fit, and add your content there.
 * Writing about culture. Wikivoyage articles often have Respect or Understand sections, which attract extensive contributions on culture. However, your five minutes is best spent adding practical advice and suggestions, and letting the traveller discover the culture for themselves when they get there.
 * Writing about things you don't like. Don't waste your five minutes on Wikivoyage telling travellers about places they don't want to go; sharing your insight into somewhere travellers would want to go is infinitely more valuable!
 * Encyclopedic or promotional language. Writing that something is fantastic or the best can be meaningless to a reader who may have different interests to you. Remember to think of why you like something and write it in the normal words you would use. Don't adopt the tone of a tourism board, or a neutral point of view just because you are writing in a guide. Your natural conversational tone and your genuine interest in what you are describing is what we are hoping to capture!

Moving forward
If you want to get more involved, or learn more about Wikivoyage you could start by reading the manual of style, and the help files which will give you an in-depth description, or by looking at some of our star articles.

title: Wikivoyage:Quick contribution guide


text: Wikivoyage:Quick country article template


text: Wikivoyage:Quick district article template


text: Wikivoyage:Quick huge city article template


text: Wikivoyage:Quick itinerary article template


text: Wikivoyage:Quick park article template

title: Wikivoyage:Quick park article template


text: Wikivoyage:Quick phrasebook article template


text: Wikivoyage:Quick region article template


text: Wikivoyage:Quick small city article template


text:
Wikivoyage:RDF

Wikivoyage's guides and other articles have great user-contributed text and pictures meant for human beings to read and understand. Our wiki technique lets us describe people, places, languages, attractions, and thousands of other kinds of things with free prose and pictures. But there are also descriptions and relationships between things in Wikivoyage that can be standardized so that computers can process them as well. For example we can define whether an article is about a country or a city. If it is a city, we can define what country it is in. To make these standardized machine-readable descriptions, we use a tool called the Resource Description Framework or RDF.

So what is RDF?
RDF is a way of recording standarised machine readable information and relationships directly in an article text. There is no need for any form of external database. To make the system more human friendly, the RDF statements are usually contained within templates which are then incorporated into Wikivoyage articles.

So, RDF is a framework for making statements about resources. In Wikivoyage a resource can in theory be anything: a destination, an attraction, a picture, an article, anything that can have a name.

Statements are in the form:

resource predicate object

A predicate is the name of a property of a resource, like its size, location, history, licence restrictions, or a relationship to other "resources". The object is the value.

So "car color red" would be a statement about a car; "Sydney isPartOf New_South_Wales" would be a statement about Sydney and its relationship with New South Wales.

Resources and properties must be uniquely identified. Humans may be able to guess that we are referring to Sydney, Australia, but computers aren't so clever. In the Web world, each "resource" must be identified with a URI (usually an URL). So, we would identify Sydney as "http://en.wikipedia.org/wiki/Sydney". For more abstract resources this can be tricker, but usually it is just a matter of assigning them a unique identifier within the wikivoyage namespace. For example, to identify User:(WT-en) Evan, you could use the URI for his Wikivoyage user page, "http://en.wikivoyage.org/wiki/User:Evan".

Schemas
People who need to agree on statements often create 'vocabularies' or 'schemas'. By agreeing on a schema, we can all agree about what a particular predicate means. Without an agreed schema, people may invent different predicates to mean the same thing, and it all becomes terribly confusing. Think of the schema as being a glossary or dictionary for the predicates that we use.

For example, the Dublin Core Metadata Initiative (DCMI) has a schema for very simple information, such as you'd find on a library card. Because we already know that we need a unique name for all of our resources and predicates, all predicates defined by the DCMI, are prefixed with "dcterms:".

The DCMI defines an isPartOf predicate - the idea of something being part of something else.

So, returning to our above example, we now have the RDF relationship

http://en.wikivoyage.org/wiki/Sydney dcterms:isPartOf http://en.wikivoyage.org/wiki/New_South_Wales

IsPartOf is only one of the many predicates available in the DCMI. Others that Wikivoyage uses include, contributor, and date.

The DCMI isn't the only schema useful for Wikivoyage. Schemas like the Creative Commons schema may also be useful for specifying licensing information.

We also have our own schema, which contains predicates for specifying information particular to wikivoyage, like the predicate wts:hasDocent is a predicate for the fact that some articles have docents.

RDF statements can be encoded in a number of different ways but on Wikivoyage we use a format called "Turtle RDF", which is just a simple way of writing RDF relationships in a human readable way.

What isn't RDF
RDF isn't a programming language. It isn't a way to make things happen, or to implement programming logic. It isn't something that requires experience in programming to understand. The more information we encode in RDF the more automatic processing can be done with Wikivoyage information. RDF is ideally used to make information that is already standardised easily accessible to allow novel and interesting uses of our information by applications and software developers. However, overuse of RDF could make Wikivoyage too much like a database rather than travel guide in free prose.

Getting RDF from Wikivoyage
Retrieving RDF statements about resources from Wikivoyage articles is simple. The Special:Rdf lets you choose which article you're interested in, and what kinds of data to retrieve. Many interesting bits of information about pages -- history, contributors, licenses, links -- can be read in RDF-encoded format.

The RDF for a page is also linked (invisibly) from each page, in a tag in the headers for the page. Although this is invisible to human readers, some browser tools and Web spiders can read and understand the encoded RDF information.

Adding RDF to Wikivoyage pages
It is possible to add RDF statements to Wikivoyage pages through the regular editing process. RDF statements -- or groups of statements -- can just be written between ... tags in the source of the page. RDF statements in these blocks should be encoded in Turtle RDF format -- an easy-to-use format that mirrors English syntax.

RDF that's stored in the page can be retrieved using the "in-page" model on the Special:Rdf page.

RDF and templates
It is better to put all RDF within Mediawiki templates, as this keeps the pages clearer, and makes fixing errors easier.

The syntax for Turtle RDF might also be daunting for people who just want to tag an article with a little information, so putting the RDF within templates helps keep it simple for these people too.

 * Template:isPartOf contains RDF that says the destination described in the current guide isPartOf another place. For example,, added to the Venice page, says that Venice isPartOf the Veneto region of Italy. This data is also used for breadcrumb navigation links.
 * Template:Geo contains RDF to say that the destination described by the current guide has given lat/long coordinates. This is used for geocoding.

See also: Project:RDF templates

Possible uses for RDF on Wikivoyage
Wikivoyage's use of RDF for in-page data is in its infancy, and the take up has been slow. There is a lot of room for experimentation. Some possible internal uses:

 * License info. Adding multi-licensing information using "cc:licence".
 * Noting that a Wikivoyage article is derived from another article on the Web (like the CIA Factbook, say) and information about who wrote it.
 * Listing related articles; articles about similar places, linking destinations with the phrasebook for the language spoken there, linking itineraries to a destination guide
 * Describing places (cities, countries, regions) and their geographical relationships to each other (nearby cities, bordering countries, ...)
 * Article status
 * Geo-spatial lat/long information, including GPS data (See Project:Geocoding)
 * Building "Bread-crumb" navigation, like "North America > Canada > Quebec > Montreal" (See Project:Breadcrumb navigation).
 * Special presentation for certain kinds of articles (travel topics, itineraries, destination guides) and destinations (cities, countries, regions)
 * Organizing "clusters" of articles automatically (say, if you wanted to download Italy and all cities and regions in that country)
 * Automatic interface with mapping sites like Google Maps or Yahoo Maps.

There is an RDF Expedition about the uses for RDF on Wikivoyage. Join the expedition if you are interested in more details.

title: Wikivoyage:RDF


text:
Wikivoyage:RDF Expedition

The RDF Expedition is an expedition to develop new ways to use RDF in Wikivoyage.

Rationale
We have an extension on Wikivoyage that lets users put RDF information into each article, using Turtle syntax. This is very powerful; any user can make important statements about a place, a person, a thing, an article with Turtle. We can also create Mediawiki templates with parameters so that users don't even have to know Turtle to make statements.

RDF is very expressive, but it depends on people making similar statements in the same way. Especially if computer software, like the Wikivoyage user interface, is supposed to do something based on knowledge about a place or page, the statements have to be consistent.

This Expedition can help us organize our ideas about expressing knowledge in RDF and using that knowledge for the Wikivoyage Web site.

Goals

 * 1) To define a process for describing problems that can be addressed with RDF, defining RDF models, writing MediaWiki templates to express them, and (possibly) using them in Wikivoyage code.
 * 2) To incubate new projects until they're ready for everyone to use.
 * 3) To find common expressions particular to Wikivoyage and bring them together into one user-edited RDF schema.

Projects

 * Project:RDF Expedition/Tags -- loose categorization of places, articles, and attractions
 * Project:RDF Expedition/Description -- give an abstract or summary of an article
 * Project:RDF Expedition/Multilicensing -- marking up pages and images so that can have more than one license.
 * Project:RDF Expedition/Derived works -- make notes about where images and texts come from, who wrote them, and what the original work's license was
 * Project:RDF Expedition/Article status -- Express Article status in RDF so that software can read it
 * Project:RDF Expedition/Article type -- Define types of articles (destination guides, itineraries, travel topics)
 * Project:RDF Expedition/Image type -- Define types of images (maps, photos, diagrams, others)
 * Project:RDF Expedition/Place type -- Define types of place in the geographical hierarchy
 * Project:RDF Expedition/Geographic relationships -- borders, directions, "nearby" destinations
 * Project:RDF Expedition/RSS -- ways to do community-programmable RSS feeds
 * Project:RDF Expedition/Language -- Define a relationship between a place and the language(s) spoken there

Process
New ideas for working with Wikivoyage RDF should work as follows:

 * For the new idea, start a new sub-page of Project:RDF Expedition, like Project:RDF Expedition/New idea . Use the Project:RDF Expedition/Template as a source for the page.
 * Describe the idea's goals. What kind of knowledge do we need to express? How could that knowledge be used?
 * Look for existing RDF vocabularies (either from other Wikivoyage projects, or elsewhere on the Web) that would support the knowledge. If they don't exist, or if they need to be refined for our needs, consider adding to the Wikivoyage RDF schema (see below).
 * Make some examples of statements. Add them to existing pages, and test that they work with the Special:Rdf tool.
 * Create one or more MediaWiki templates so that making the statements are easier.
 * If the new idea should have some effect on the user interface of the site (add a menu item, automated links, color changes, wording changes) add a feature request to get the effect coded.
 * After the UI is coded, the templates are designed, and everything else is ready for "regular" users to start using the feature, create a help page to explain the feature.

No one person has to do all these steps. As with anything on Wikivoyage, it's best to Project:Plunge forward and get something started. It's OK to just start with an idea, and let other people more interested in knowledge representation and coding work on the rest.

Wikivoyage schema
Some data representations are going to be particular to Wikivoyage. For example, our article status designations aren't used by other organizations.

One nice thing about Turtle RDF is that we can create new RDF schemas in it. So we can use the same wiki technique to develop our schemas.

We can create a schema on the shared Wikivoyage site, which would be available at Shared:Wikivoyage:Schema. Elements from the schema would be accessible with the namespace "wvs:" (Wikivoyage schema) in Turtle.

RDF limitations
A couple of things worth noting here:

 * We currently don't have a way to identify attractions within a destination. You need URIs to identify things in RDF world. Places are defined by the URL of their destination page, but attractions aren't directly addressable.
 * The RDF extension currently reads RDF for one page at a time. So uses like "find all pages that have property X" aren't (currently) very practical.

Both of these should be fixed in the near(-ish) future.

Existing implementations
These are some problem domains that have existing implementations on Wikivoyage; they may be a good model for future problems.

 * Project:Breadcrumb navigation
 * Project:Geocoding

RDF vocabularies
These are some good vocabularies, many of which apply to our problem domain.

 * Dublin Core -- the "granddaddy" of semantic data.
 * Creative Commons -- some refinements on the Dublin Core metadata specifically for Web documents and licensing.
 * Friend-of-a-Friend (FOAF) -- A project for describing people and their relationships to projects, ideas, places, and other people

title: Wikivoyage:RDF Expedition


text:
Wikivoyage:RDF Expedition/Airport codes

For many destinations, it's useful to note one or more nearby airports for getting into or out of the destination. If we use some structured data through RDF, we can possibly, in the future, have enhanced search for destination based on nearby airports, or vice versa.

Representation
There's a contactNearestAirport property in FOAF, but it doesn't have quite the same semantics as we're looking for. Probably the best thing is to say, "This page is about a place, and that place is near an airport with this IATA code: FOO." Using the DAML airport ontology, this might be expressed as follows:

<> dc:spatial place:Denver. place:Denver wts:hasNearbyAirport .   "DEN".

With the proper prefixes, this boils down to:

@prefix airport: . @prefix air: . <> dc:spatial place:Denver. place:Denver wts:hasNearbyAirport airport:DEN. airport:DEN air:iataCode "DEN".

Templates
Template:IATA does formatted output of the IATA code, and also has some structured RDF included. Template:ICAO does the same thing for ICAO codes.

title: Wikivoyage:RDF Expedition/Airport codes


text:
Wikivoyage:RDF Expedition/Article status

We have a nice 1-5 measurement of article status on Wikivoyage, which we use for evaluating the maturity of an article. If we represented this status in RDF, we could query article status, if we could query.

Representation
There's not a clear vocabulary for representing document's development stage, so we'll probably have to make up our own in the Wikivoyage schema. Something like wts:stage, with either literals ("stub") or resources (wts:Stub) as the range.

We will use the following representations

Stub
<> wts:stage wts:Stub.

Outline
<> wts:stage wts:Outline.

Usable
<> wts:stage wts:Usable.

Guide
<> wts:stage wts:GuideStage.

Star
<> wts:stage wts:Star.

Though we use different templates to indicate the article status for different types of articles (city, country, travel topics, etc.) we will not do the same in our RDF representation, as we don't wish to repeat what Project:RDF Expedition/Article type will be doing.

Examples
For Lausanne,

<> wts:stage wts:Star.

Templates
It should be easy and expedient to add this code to the existing article status templates.


text:
Wikivoyage:RDF Expedition/Derived works

When we import images or text from other sites, it's a good idea to note where it came from, what its copyright status is, and who made it. In some cases, this is required by the license for the work.

It would be good to express this information so that it can be read by both humans and machines. In particular, it would be great to add source and authorship information into the credit blocks at the bottom of each page.

Representation
The Dublin Core and Creative Commons schemas are fine-tuned to represent authorship, licenses and sources.

In particular, we can use the dc:creator and dc:contributor elements for authors; we can use dc:source for the original URLs, and we can use cc:license to describe the works' licenses.

Examples
Our guide to Mexico is based partially on the CIA Factbook. We can note that fact like so (on the Mexico page):

<> dc:source .  cc:license cc:PublicDomain ; dc:creator "Central Intelligence Agency".

Consider Image:Flag of Croatia.png, a flag image derived from the OpenClipArt project. Here's a way to specify its source:

 dc:source .  cc:license cc:PublicDomain.

Consider Image:Suomenlinna.jpg, from the Wikimedia Commons.

 dc:source .  cc:license  ; dc:creator .

Consider pt:Project:Sobre, which was largely translated from Project:About. On the Portuguese page, we could say:

<> dc:source en:Wikivoyage:About.

en:Wikivoyage:About cc:license  ; rdfs:seeAlso en:Wikivoyage:About.

Templates
The most common template would give the source URL, the license, and the creator's name.

Another would give an URL for the creator's ID (for authors who have user pages on other wikis, for example):

One easy template would just fill in the original source URL:

...and the source URL, plus a license, but no author:

For works with lots of authors, we could have a bunch of related templates assembled in a block.

For stuff translated from other language versions of Wikivoyage, we could have a simple translation template.

Other notes

 * For sources where we get a lot of data (Wikimedia Commons, CIA Factbook) we may want to include some namespace prefixes ("CIA:" or "WMCommons:").
 * We don't have an easy way to say, "the image referred to by this image page".
 * We'll need some code to add source information to the credits block.

title: Wikivoyage:RDF Expedition/Derived works


text:
Wikivoyage:RDF Expedition/Description

It can sometimes help automated processes to have a description of a page. We can show these descriptions in, say, the "description" meta tag for an HTML page, or in other metadata for other media.

Representation
The Dublin Core "description" element clearly fits the bill here.

Examples
For Toronto, we might have:

<> dc:description "A travel guide to Toronto, Canada's largest city, including hotels, restaurants, and neighborhoods." .

Templates
The Template:Description can be used to add a description.

Other notes

 * If no description element is used, a stock description based on the template at MediaWiki:travelguidedescription is used. If the article isn't a travel guide, the first text paragraph from an article is used as the HTML description.

title: Wikivoyage:RDF Expedition/Description


text:
Wikivoyage:RDF Expedition/Docent

Wikivoyagers have knowledge about our destinations that sometimes goes beyond what can be included in a guide. Often, visitors to Wikivoyage have a very specific question that is not answered buy our usual guide format. To connect these folks, it would be great to make an explicit connection between some articles and contributors.

Representation
None of the existing Schemas (FOAF, Dublin Core, etc) quite nail down the feeling of "docent" quite right. We would need to be extended using the Wikivoyage schema to define our specific use. I suggest

wts:hasDocent

Note that we are defining a place as having a docent as opposed to the other way around.

For the user identifier, using User page urls has an advantage over using general/public email addresses.

Examples
For Kathmandu

Templates
Template:hasDocent

Other notes
The duties and policies should be documented at Project:Destination Docents. If an article has no docents (or maybe even if it does?) there should be a link explaining what a docent is and how to become one.

title: Wikivoyage:RDF Expedition/Docent


text:
Wikivoyage:RDF Expedition/Language

The goal here is to define what language or languages are spoken at a destination. The data could be used to add a phrasebook automatically to the "related articles" section of the navigation area.

Relationship
At the RDF level, there doesn't seem to be a standard way to say "this language is spoken at this place." So we'd need to add it to our local schema -- something like wts:languageSpoken. We can use standard RFC 3066 identifiers for languages ("en", "fr", "pt-BR").

That way we could say:

place:Brazil wts:languageSpoken "pt-BR".

place:Switzerland wts:languageSpoken "fr", "de", "it", "rm".

For most countries, this would only need to be defined at the country level. However, for regions that use different languages from the country they're in, we could add a language code at the region level, too.

place:Catalonia wts:languageSpoken "ca", "es".

place:Brittany wts:languageSpoken "br", "fr".

To save ourselves some work, we can assume that the language spoken in a place is either a) the language defined for that place or b) the first language(s) defined up the isIn hierarchy. To avoid having any difficult rules about whether or not the national language is spoken or understood at the region level, we can require that if any languages are defined, they all have to be defined.

Template
Template:Language would be used to say "the place covered in this article uses the associated language." Examples:

title: Wikivoyage:RDF Expedition/Language


text:
Wikivoyage:RDF Expedition/Place type

Wikivoyage destination guides describe different kinds of places on the geographical hierarchy. Adding some machine-readable code to indicate what kind of place a guide describes can let software do different things with different levels of the hierarchy. For example: indicating which articles don't match their template in the MoS, or the Web software could include different controls or links on country pages than on city pages. Scripts could be written just for city articles, just for regions in France, etc.

Representation
The Simile basic location ontology is a good start for Wikivoyage. However, to map closely to Wikivoyage's hierarchy, it may make sense to use classes that strictly match it.

 * wts:Place - any kind of place, superclass for the rest of these classes
 * wts:Continent
 * wts:ContinentalSection
 * wts:Country
 * wts:Region
 * wts:State
 * wts:Province
 * wts:County
 * wts:Department
 * wts:City
 * wts:SmallCity
 * wts:BigCity
 * wts:HugeCity
 * wts:District
 * wts:Park

Examples
We use an URN format to define places.

place:Lausanne a wts:BigCity. place:France a wts:Country. place:Montana a wts:State.

Templates
The following templates will include minimal code to mark a destination guide as describing a particular kind of place. Many of them can and should be included in the more specific Project:article status templates like Template:Usablecity.

 * Template:Continentguide
 * Template:Continentalsectionguide
 * Template:Countryguide
 * Template:Regionguide
 * Template:Cityguide
 * Template:Districtguide
 * Template:Parkguide

title: Wikivoyage:RDF Expedition/Place type


text:
Wikivoyage:RDF Expedition/RSS

RSS is a family of related protocols that lets people subscribe to "channels" or "feeds" of information. It's commonly used on the Web to keep let people organize, in one place, updates to their favorite blogs, wikis, news Web sites, or other regularly-updated information.

We currently have an RSS channel for English-language Wikivoyage based on the regularly-updated content on Wikivoyage (Project:Discover, Travel news, Project:Destination of the month, etc.). The feed depends on a long and fragile script that scrapes these articles directly.

It would be nice to have a way that users could design and organize RSS channels for English Wikivoyage and other Wikivoyage language versions without needing to program page-scrapers. Some possible examples:

 * Casual readers' channel. Something to attract people back to the site on a regular basis, such as the current "travel news and trivia" feed.
 * Community channel. A feed for people more involved in the community. It could include items from Project:Requests for comment, Project:Votes for deletion, Project:User rights nominations, Project:Collaboration of the week, Project:Logbook, etc.

As new features or content for Wikivoyage are developed, we could enhance or replace parts of the RSS feeds without extra programming. A single multipurpose RSS generator script (running nightly, say) could read info for all RSS feeds from pages on Wikivoyage, and output the RSS automatically. It could read a MediaWiki namespace article, like MediaWiki:rsschannels, to get the names of the articles with each feed to create. Then, each channel would have its own page, like Project:Community channel or Project:Readers channel. This would have some baked-in RDF code defining the channel properties, and links to articles that includes RDF code for the RSS items.

Representation
RSS 1.0 is an RDF vocabulary for defining feeds. It's one of the three competing standards for RSS, and probably the least used, but it has the advantage of being implemented on top of RDF. Since most feed readers support all three standards, it should probably be fine to build this feature using RSS 1.0.

RSS 1.0 defines two kinds of things: RSS channels and RSS items. We can include the channel definition on the channel page, then one or more item definitions in each item page.

Examples
The Turtle RDF for an RSS channel would look something like this:

 a rss:Channel; rss:title "Wikivoyage News and Trivia"; rss:link ; rss:description "Travel news, trivia, and featured destinations from Wikivoyage, the free travel guide.". For an RSS item, it would look something like this. Note that the item has to have a unique URI; I'm using a tag URI.

 a rss:item; rss:title "January 2007 Destination of the Month: Taipei"; rss:link ; rss:description "Taipei is the provisional capital of the Republic of China, otherwise known as Taiwan. ...".

Templates
It would make sense to wrap the RDF that defines an item in its own MediaWiki template Template:rssitem; similarly for channels Template:rsschannel. Then, a second layer of templates could use these RSS templates to make a page "RSS enabled". For example, Template:Newsitem could include the to add an RSS item for each news item without any work by the contributor.

title: Wikivoyage:RDF Expedition/RSS


text:
Wikivoyage:RDF Expedition/Template

''This is an article template for new ideas for the Project:RDF Expedition. You can copy this page to a new sub-page of the RDF Expedition, and fill some or all of the sections. Try to erase this italicized stuff, too.''

''Up at the top, add a little description of what kind of knowledge we want to represent. How would a marked-up page be different from other pages? Would there be UI changes, or would the knowledge only be visible to automated systems? This is where you make your "sales pitch" for the idea.''

Representation
''Here, you make references to the RDF schemata (!) and schema elements (like relationships or predicates) that could represent the knowledge. If we need to add new elements to the Wikivoyage schema to make this knowledge representation work, note the changes here.''

Examples
''Here, give some examples of how the knowledge would be represented. If you've put examples on other pages, add links to them here.''

Templates
''Link (like Template:Template name -- don't forget the initial ':' !) to Mediawiki templates that make expressing this knowledge easier. Give examples of how to provide parameters to the template.''

title: Wikivoyage:RDF Expedition/Template