Re: Geohash for events

Hi Kingsley,

I really like the fact that there are both timeline and map view for the 
data. But, how much it would take for giving both views in one window?

We have an application where we want to allow classics scholars to 
browse artifacts by both time line and geo-line at the same time. Any 
suggestions, guys?

Jun

Kingsley Idehen wrote:
>
> Bernard Vatant wrote:
>>
>> Hi masa
>>> Hi Bernard,
>>>
>>> Added support for event page uri:
>>> http://www.kanzaki.com/ns/geo/u07t4qf8j:2008-09-28_2008-10-03;INRIA_IST_2008?uri=http://www.inria.fr/actualites/colloques/2008/ist08/ 
>>>
>>>   
>> Really cool. The URI format looks perfect to me now and exactly what 
>> I imagined you would do :-) .
>>> The uri part cannot be combined 'hash:datetime;name' part, because
>>> such uri itself adds another hierarchy to the original uri (i.e. / in
>>> event page uri). Hence it should be provided as query string.
>>>
>>> I wonder this looks too complicated for practical use ?
>>>   
>> It is, if users have to concatenate the URI themselves by going to 
>> geohash, searching the place, copying the geohash id in the service 
>> namespace, add the time interval in conformant date format, add the 
>> event URI. Speak about "user experience" ... for geeks like you and 
>> me, but "ordinary" people will never do it that way.
>>
>> But it you (or someone else) provide a smart bookmarklet (Faviki has 
>> given me a lot of ideas for that matter) to use in your browser from 
>> the page of the event 
>> (http://www.inria.fr/actualites/colloques/2008/ist08/), where the 
>> user can call geohash via a geocoder, enter the dates using a 
>> calendar applet, and grab the name from the page title ... et voilà ...
>> The service would return a page as yours, with the RDF description 
>> and a permanent URI. And maybe call "au passage" the geonames service 
>> to add the neighbouring geonames features, yahoo or google to add 
>> sponsored links, whatever ...
>>
>> This would be *practical* ... You could even "au passage" dump the 
>> created event in a backend data store, etc.
>>
>> Say what?
>
> URI are to be felt, experienced, rather than seen. Yes, the 
> extensions, plugins, plain old anchor text, and the like are the way 
> to go, the Geohase URI scheme are currently implemented is really cool!
>
> I've just opened an example URI in a Browser Session 
> <http://demo.openlinksw.com/rdfbrowser/?uri=http%3A%2F%2Fwww.kanzaki.com%2Fns%2Fgeo%2Fu07t4qf8j%3A2008-09-28_2008-10-03%3BINRIA_IST_2008%3Furi%3Dhttp%3A%2F%2Fwww.inria.fr%2Factualites%2Fcolloques%2F2008%2Fist08%2F>:-) 
> Note, that the Map and TimeLine control provide appropriate views.
>
>
> Kingsley
>>> 2008/6/9, Bernard Vatant <bernard.vatant@mondeca.com>:
>>>  
>>>> One thing I was wondering was how to encapsulate the URI of the event
>>>> itself, something like (completely incorrect syntax, but you get 
>>>> the idea
>>>> again)
>>>>     
>>>
>>> cheers,
>>>
>>>   
>>
>
>