Andrew,
I like your idea about the XML file, it is definitely how it will have
to go, the idea is at the heart of the "Semantic Web" which is slowly
evolving.
Of course it shouldn't be just for accommodation, in fact virtually
every object that we tag currently should be pulling it's metadata from
the "Operator".
However, we are quite a way off that I feel, so in the mean time we do
need to, at the very least, structure our tags correctly and decide on
the broad brush strokes for describing various objects. The granularity
of the data is down to each individual mapper.
Jonathan
http://bigfatfrog67.me
On 18/10/2013 11:35, Andrew Errington wrote:
On Fri, 18 Oct 2013 01:47:51 Dudley Ibbett wrote:
From a tourists perspective it is quite important to know whether it is
self catering accommodation or not. It is also important to know whether
it is a single building unit (i.e. house,cottage,chalet) as opposed to a
number of units in a building (i.e. apartments). I would be inclined to
use tourism=apartments for the latter. Types of tourist accommodation do
seem to be quite country specific. There are very few tourist apartments
in the UK but they are very common in Croatia for example. I would agree
that tourism=chalet would seem to be the most appropriate tag for a gîte.
Surely it's simply a matter of tagging "There is accommodation of some kind
here" and including a URL to the website? There is very little point in
slicing the data so thinly, especially since renderers will paint a little
picture that probably looks identical for any class of tourist accommodation.
With a website URL, the OSM map user can hop over to the hotel's site and read
all about the number of rooms and facilities.
What I really think would be nice is to specify an osm.xml file that a
business can put on its website. Inside OSM we would tag the place with a
URL for that file, and we copy a small set of basic tags taken from that
file, sufficient to render the object. Periodically we can automatically (or
semi-automatically) refresh the tags with the content of the file. (If there
is no file, or no URL we just tag manually as we do now). Then at runtime,
whenever someone seems interested in the place the mapping app uses the URL
to fetch the contents of the XML to display to the user. The advantage of
this is that it distributes the data, and allows the site owner to maintain
the details without filling OSM up with useless cruft. The XML file could
even be dynamic and contain current vacancies, prices, upcoming closures (for
renovation) etc.
Best wishes,
Andrew
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
