<div class="gmail_quote">2009/9/29 Tom Hughes <span dir="ltr"><<a href="mailto:tom@compton.nu">tom@compton.nu</a>><br><br></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Linking the tags to the wiki is going to be a great way of joining the<br>
two things together much more closely. The other thing I'd like to see<br>
is being able to browse sideways from the 'browse' pages, so that it's<br>
possible to navigate from, say, a pub, through to other pubs nearby.<br>
But I guess this requires some more XAPI-like functionality to be added<br>
to the main server?<br>
</blockquote>
<br></div>
The wiki's full of shit though, so do we really want to encourage people to believe all the stuff that is there...<br><div class="im"></div></blockquote><div class="im"><br>Heh, well I guess you could argue that this might help encourage people to make the wiki less "shit".<br>
<br>I also think that when clicking on an "amenity=pub" link, I'd expect to see a list (or, say, a map) of nearby pubs, rather than a description of what a pub is. But having both links, suitably labelled/designed, can't really hurt.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* displaying the address in a more address-like style, perhaps also<br>
marked up with the hCard microformat.<br>
</blockquote>
<br></div>
I'm not at all sure that we should start getting "clever" about how we display specific tags - to my mind we are about the data and we should be tag agnostic and just display the raw data and let the reader draw conclusions from it.<br>
<br>
Doing "clever stuff" with our data is primarily something for other people to do, not for us to do.<br><div class="im"></div></blockquote><div><br>Ha, well there's a contentious statement! If that were the case, then why do we even bother with the Mapnik/Osmarender tiles? Surely they're the ultimate form of doing "clever" stuff with the data.<br>
<br>My personal view is that it's the XML view which is tag-agnostic, and that the map and browse views are where we should be displaying the data in the most useful, usable form possible. I think our browse pages could be as good, if not better, than Google's "place pages" [1].<br>
<br>Whilst I can understand the view that OSM should only be about gathering and maintaining the data, and that we should leave building user-friendly 'services' on top of it to other companies and organisations, I think that we need some form of usable services (like the map, and the browse pages) in order to show off the data and to attract people to the community. To use Wikipedia as an example, they seem to focus equally on providing a well-designed, stable, fast encyclopaedia website as on providing a good editing experience and community (despite the huge financial burden of running all the extra servers).<br>
<br>Guess this is a tricky one to balance though.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* showing the date that the node/way/relation was first created (rather<br>
than just date of the last changeset).<br>
</blockquote>
<br></div>
Certainly possible but I'm not sure how much value it has.<br><div class="im"></div></blockquote><div><br>Mainly I was thinking that it helps to give some idea of how 'stable' the way is (how long it's been around). But I'll agree that it's not the most important value in the world.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* making wikipedia=* and website=* links more prominent, possibly with<br>
icons.<br>
</blockquote>
<br></div>
I think this comes under "clever" rendering again.<br><div class="im"></div></blockquote><div><br>The cleverer the better, in my books... :-) <br><br></div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* adding some stats like "total length" (for open ways) or "area size"<br>
(for closed ways).<br>
</blockquote>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Relatively expensive for us to compute though so we would need to be a bit careful with larger/more complicated objects.<br></blockquote><div><br>Guess we could limit it to ways with less than X number of nodes. Or figure out a neat way of caching it.<br>
<br>Frankie</div></div><br>[1] <a href="http://googleblog.blogspot.com/2009/09/place-pages-for-google-maps-there-are.html">http://googleblog.blogspot.com/2009/09/place-pages-for-google-maps-there-are.html</a><br clear="all">
<br>-- <br>Frankie Roberto<br>Experience Designer, Rattle<br>0114 2706977<br><a href="http://www.rattlecentral.com">http://www.rattlecentral.com</a><br><br>