<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2014-03-29 13:41, nounours77 wrote :<br>
</div>
<blockquote
cite="mid:55412B4F-E747-4A32-B628-EC429B75B8D1@gmail.com"
type="cite">
<pre wrap="">Hi everybody,
As discussed in my earlier post, I think voting is important even for specific service tags to make them offical. Therefore, I extend the voting period for the boat_sharing proposal:
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Proposed_features/boat_sharing">https://wiki.openstreetmap.org/wiki/Proposed_features/boat_sharing</a>
The idea is to replicate the same structure for boats as for cars. To indicate where you can pick up a shared boat you reserved. I expect that service providers will mostly deliver this information, but we should agree on the format.
</pre>
</blockquote>
Don't believe those who advocate lack of coordination and chaos,
they might be paid by Google ;-)<br>
Go ahead with your standardizations! Nice to vote.<br>
<br>
But I think that general principles must be respected. A more
structured approach might me more rewarding.<br>
<br>
A map feature must be made of an object having attributes.<br>
An object is the more generally a building=yes or a shack=yes, an
open place or whatever "physical" (meadow, forest, landuse, tower,
...): it is what is represented by the node, way or relation and
that needs to be rendered on the map.<br>
amenity, shop, rental, hairdresser etc... are not objects but the
activity or other attribute taking place at the object.<br>
There can be several attributes (e.g. shop and rental activities)
for the same object, not no two objects for the same map feature.<br>
As discussed before, a building may be both a castle (château) and a
hotel.<br>
I have recommended that the wiki should clearly classify objects and
attributes.<br>
People have advocated that the street number is the object and that
the house (and roof) are the attributes of the number.<br>
This is of course nonsense. The object is what is represented by the
map node, way or relation and that is a house or land ...<br>
One may be interested in building a "view" (in SQL sense) by street
number key, but that does not make a closed way a number.<br>
Or several numbers being represented by the same closed way.<br>
Well known objects have a well known rendering, which solves the
problem of those complaining that amenity=their_invention is not
rendered. building=yes must always be rendered and it may be
rendered differently according to its attributes, e.g. amenity.<br>
<br>
In practice, amenity, for example, is all-right, but it should not
be considered a mistake but rather a requirement to add building or
meadow or landuse, an object to it.<br>
<br>
<a href="http://wiki.openstreetmap.org/wiki/Semicolon">Semi-colon
value separator </a>explains that what;some;taggers;are;doing and
that talking about it here are sins.<br>
I'm nut sure I agree, but it suggests namespaces: a good idea
because it's more general and because it's already used.<br>
So, we can have:<br>
<br>
building=yes<br>
and<br>
shop=goods1;goods2<br>
or<br>
shop:goods1=yes<br>
shop:goods2=yes<br>
<br>
So, for your boat business, we would have things like:<br>
<br>
building=yes | wharf=yes | whatever<br>
rental:kayak=yes<br>
rental:life-jacket=yes<br>
shop:life-jacket=yes (rent or buy)<br>
rental:boat=yes<br>
rental:boat:capacity=10<br>
sharing:boat=yes<br>
sharing:boat:capacity=2<br>
or<br>
sharing:boat:1:capacity=2<br>
sharing:boat:2:capacity=4<br>
shop=yes (used alone for surprise selling)<br>
and, of course, not excluding<br>
sharing:car=yes<br>
and the beat goes on...<br>
rental:opening-hours=*<br>
shop:opening-hours=*<br>
shop:русский:матрёшки=many<br>
<br>
So, regarding your 1-2-3 choice, I think that # 3 is the good
direction.<br>
Please note that, regarding searches, shop, rental, boat, car, ...
are different words.<br>
One may search for "rental" = anything to rent or "car" = any way to
use a car or "car rental" or "car sharing" specifically.<br>
life-jacket, on contrast, is a single word.<br>
<br>
Tags like car_rental, car_pooling, boat_rental etc... are annoying
because they multiply the same kind of wiki pages and propositions.<br>
For example, I need tags to indicate places where subscribed
pedestrians can stop a subscribed car).<br>
Do I really need to create a new "car_riding_on_subscription" page,
nobody would discuss that and I understand,<br>
or would the following two riding:*, very agreeable additions to
that general framework suffice:<br>
<br>
Logically, following that and one's reasoning:<br>
post=yes (or stop-sign=yes, or whatever (to be discussed), that's
the map feature where the service takes place)<br>
get-a-vehicle=yes (if felt needed, generic term for all those
kinds of activities, term off my improvable invention)<br>
riding:car=yes<br>
riding:car:subscription=yes<br>
....<br>
<br>
I would love to see you propose this general framework allowing your
boats as well as my kayaks and car riding.<br>
As well as "Trains and boats and planes to Paris or Rome" with Billy
and Dionne :-)<br>
I think you would be heard.<br>
<br>
Hoping this can help,<br>
<br>
<br>
<br>
<br>
</body>
</html>