Wikivoyage:RDF Expedition Collection of wanted features

This is step 1 of the RDF Expedition.

Here go brain-storming like collections of all features that would be nice to have and maybe could be provided by RDF meta data. You should not too much concern about how to build them, just enlist what you ever have dreamed about. Try to describe your wishes as exact as possible. Everybody is welcome to contribute here.

If you already have some ideas about how to represent the information, note that on the step 2 page.

License info

(sweapt in from Project:RDF)

Adding multi-licensing information using "cc:licence".

Notes about derivated Work

(swept in from Project:RDF)

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

(sweapt in from Project:RDF)

Articles about similar places, linking destinations with the phrasebook for the language spoken there, linking itineraries to a destination guide==

Describing places

(swept in from Project:RDF)

Are they cities, countries, regions or whatever?

Geographical relationships

(swept in from Project:RDF)

Describing geographical relationships of some place to each other (nearby cities, bordering countries, ...)

bordering countries

Countries that have a political border. OK.

bordering regions

If some regions realy border to each other, OK.

partly overlapping regions

Regions of a country may overlap. Should this be treated as bordering or separately?

nearby cities of same importance

Are San Francisco and Los Angeles nearby cities by this meaning?

geographicaly nearby cities

Then Long Island and NYC are nearby cities.

natural park

Is a natural park nearby to the region(s) it is in?

Article status

(sweapt in from Project:RDF)

Quality: maybe: alpha, beta, stub, (ok), good, excellent, outstanding.

Completeness: maybe a level per section: poor ... (ok) ... rich.

Precision of geographical coordinates: maybe: radius = kilometers (the point is surely within this radius)

Quality rating: maybe: rating = percent (just xx % of the articles are of better quality)

Geo-spatial lat/long information

(swept in from Project:RDF)

• including GPS data
• lat/long information for a point, like a attraction.
• Several latitude/longitude points connected to a area, like a region or country. Might be useful for automatic Interface with mapping sites like Google Maps or Yahoo Maps.
• Several lat/long points connected to a line. Itineraries like hiking trails maybe need an option to download these points to a GPS device.

"Bread-crumb" navigation

(swept in from Project:RDF)

Building "Bread-crumb" navigation, like "North America > Canada > Quebec > Montreal" .

Should this apply to the geographical hierarchy only, or even for for other travel topics or meta-articles? -- (WT-en) Hansm

Presentation for certain kinds of articles

(swept in from Project:RDF)

Special presentation for certain kinds of articles (travel topics, itineraries, destination guides) and destinations (cities, countries, regions)

Presentation for certain groups of readers

Special presentation for certain groups of readers addressed by that article (fishing, backpackers, buisiness travelers, ...).

"Clusters" of articles

(swept in from Project:RDF)

Organizing "clusters" of articles automatically (say, if you wanted to download Italy and all cities and regions in that country). Every point in the geagraphical hierarchie tree should be able to be choosen as the top of a custom guide (say, a Toscana guide).

Maybe some kind of grain or level is possible. If I only traverse some region by bus, I'm not interested in all details of that region, but only in perhaps basic information of larger cities and the region article itself.

Should also work for itinaries as top of the hierarchical tree.

There might be some general travel topics that should be included into a custom guide, like Tips for travel in developing countries into a Peru guide. Maybe only special sections of it? And, of course, the phrasebook in a certain language (say, French) is an other general article that could be part of many different guides.

Interface with mapping sites

(swept in from Project:RDF)

Automatic interface with mapping sites like Google Maps or Yahoo Maps.

Index lists for print versions

This should include alternative spellings or names, famous sights not treated in an own article and usual nouns in names (mountain -> Monte ...).

(WT-en) Unger has manualy made an index list for places in Egypt on de:. A partly translated version is here. For several reasons, this might be used as a reference for this feature:

1. Names had to be romanized, thus several usual spellings are possible.
2. We use diacritics on de:, so we have to care about an alphabetical order. Unger has maped all characters with diacritics onto their non-diacritic version. This would be one way, the other one would be to keep diacritics, but define an alphabet that includes diacritical characters.
3. The Arabic article al is part of many names, but should be ommited for the index list.
4. The Arabic word Om or Umm, respectively, seems to be part of many names. Instead of giving two different spellings for each place which starts with Om, a general redirection "Om ... -> Umm ..." is given in the index.
5. Some names are ambiguous and need to be resolved.
6. Monasteries start with the word Deir in their name. This might be important since somebody might search for Monastery of Abu Mina, what is perhaps the name he knows, but doesn't know the Arabic name Deir Abu Mina.
7. Many sights are better known than the city they belong to, thus even some sights with no own article should be indexed.

Additional remark on (3): One should be able to mark name components, which should not considered for alphabetic sorting. This concerns mostly articles (en: the; de: der, die, das, ar: el-). For instance, _The_ Tower Bridge should be written as "The Tower Bridge" and sorted as "Tower Bridge". (WT-en) Unger 04:36, 22 Nov 2005 (EST)

Searchable keywords

It should be possible to limit a search to titles and keywords. Keywords can be marked words of the article plus just metainfo, marked as keyword.

Sequence of Articles for print versions

In Order to print a real travel guide, we need to provide some information about the sequence of articles. We have to linearize a net.

Customized index lists on the fly

For example, I send a search queue for all scientific museums in northern Italy and want to get a list of them imediately.

Climatical searching criteria

What would be the places in Europe warmer than 10°C average in january? - Which of them is the closest on to me?

Finding nearby places that hold certain criteria

Where is the next golf park?

Navigation

At the top of an article (not at the bottom like with categories in Wikipedia) there should be links (one or more) to the "parent" articles. Or, maybe to the "main" article of the parent category of the current article.

This is the same as #"Bread-crumb" navigation. Or do you see differences? ((WT-en) Hansm)

It's an example of how to use this hierarchical structure. I'd suggest to have a link on each article page which has a fixed position in the page's layout and points to a "parent" article or several parent articles. --(WT-en) Roland2 15:06, 22 Nov 2005 (EST)

Queries

Examples:

• What Austrian stubs have been created since my last login?

Opening hours

What museum has opened now? Where can I have a meal in Paris on Friday at 2 o'clock in the morning?

Wanted information

So I've just arrived in the center of London: What information about the center of london is missing in wikivoyage? What missing information has been requested by other readers of wikivoyage?

Categories

Attributes which could be represented by categories:

"thermal spring", "coal mine", "Celtic place of warship", "carnival procession", "national park", "elephant riding", "church", "airport", "suited for children", "suited for disabled people", ...

What is the goal you want to explain here? -- (WT-en) Hansm

These are examples to discuss if a certain type of category will/should be supported or not:

1. The example "elephant riding" could raise the question if there should be categories "elephant riding", "horse riding", "camel riding" or if there should be hierarchical categories like "riding > elephant", "riding > horse" and so on. If there are no category pages, I think it will not be easy to build a hierarchical structure of attributes (formerly "categories").
2. The example "suited for children" raises the question if "suited for children" were a useful attribute or whether the attribute "suited for children" should be expressed by a combination of specific attributes like "diaper changing table available", "childcare", "playground" etc.

--(WT-en) Roland2 15:26, 22 Nov 2005 (EST)