I don't know about the Dublin Core issue but my gut feeling with
geo.position and your example would be that of course the bed and
breakfast in Pisa, Italy should have their location as the hotel will
always be in the same place. I think that you've looked at the issue
from the wrong side
Ben,
I think that you've looked at the issue from the wrong side in that
you assume it would only show in regional searches (e.g. an italian
search engine) whereas in actual fact it should show up in a global
search for that region - e.g. if I search for hotels pisa italy I
would expect
://developer.yahoo.com/searchmonkey
http://developer.yahoo.com/yql
Ted
_
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Ben Dodson
Sent: Tuesday, February 24, 2009 12:38 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] meta tag questions
I
Hi Bob,
Bob Schwartz wrote:
2.
geo.position: According to Wikipedia geo.position tags help in
returning regional search requests, or as they put it: "It
understandably makes little sense to look for a baker and find one who
has his shop in a completely different town". If this is the case,
Hi Robert.
Does the geo ontology/schema also represent properties for longitude
and latitude? I wrote a geospacial inferencing engine a while back
for inferring distances between points using the great circle
method. From memory, I think it used the geo schema.
If it is for a web page,
Thanks Bob,
I've dug up some old java code that contained a snippet from the geo
schema I used (in a javadoc comment). Here it is:
/**
...
* pRDF Vocabulary for describing points:
* code
* rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
*
