The new Yahoo Maps API described with RDF Forms;

<rf:Indexable xmlns:rf="http://www.markbaker.ca/2003/rdfforms/"
              xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
              rdf:about="http://api.local.yahoo.com/MapsService/V1/geocode">
  <rf:indexedBy>
    <rf:IndexParam rf:shortName="appid">
      <rdf:predicate rdf:resource="http://developer.yahoo.net/faq/index.html#appid"/>
    </rf:IndexParam>
  </rf:indexedBy>
  <rf:indexedBy>
    <rf:IndexParam rf:shortName="street">
      <rdf:predicate rdf:resource="http://en.wikipedia.org/wiki/Street"/>
    </rf:IndexParam>
  </rf:indexedBy>
  <rf:indexedBy>
    <rf:IndexParam rf:shortName="city">
      <rdf:predicate rdf:resource="http://en.wikipedia.org/wiki/City"/>
    </rf:IndexParam>
  </rf:indexedBy>
  <rf:indexedBy>
    <rf:IndexParam rf:shortName="state">
      <rdf:predicate rdf:resource="http://en.wikipedia.org/wiki/State_codes"/>
    </rf:IndexParam>
  </rf:indexedBy>
  <rf:indexedBy>
    <rf:IndexParam rf:shortName="zip">
      <rdf:predicate rdf:resource="http://en.wikipedia.org/wiki/ZIP_Code"/>
    </rf:IndexParam>
  </rf:indexedBy>
  <rf:indexedBy>
    <rf:IndexParam rf:shortName="location">
      <rdf:predicate rdf:resource="http://en.wikipedia.org/wiki/Location_%28geography%29"/>
    </rf:IndexParam>
  </rf:indexedBy>
</rf:Indexable>

Ideally, such a form would be returned on a GET to http://api.local.yahoo.com/MapsService/V1/geocoding when application/rdf+xml is declared in the Accept header as the preferred representation format.

I grounded most of the parameters in Wikipedia URI space, but Yahoo might want to be more precise and define their own terms where Wikipedia isn’t suitable. Also, Wikipedia doesn’t yet do RDF, so you can’t get any of the (eventual) goodness that comes from WebClosure. Of course, the form is useful without that.

Trackback

no comment until now

Add your comment now