Face to Face Meetings/September 2011/Notes

This will be formatted later

Location with href:

<pois>...
<location href="http://example.com/foo.gml" rel="Alternate">
<SimplyPolygon>
</SimplyPolygon>
</location>
....

Location with link: <pois><poi> <link rel="alternate" href="http://...foo.gml"/> <location></location>

Link to POI in HTML 5: <link rel="alternate" href="http://foo.poi" type="application/poi+xml">

The browser could find that POI, and then find links within that to get things like a 3d model

We could also embed the POI directly in html5 via namespaces. Ick.

One could use Javascript to find the link to the POI and transform it into the HTML DOM: <html> ...<script> document.getElementsByName("link") search results for link rel="POI" parse the POI embedd in DOM

ID discussion:

http://smithsonian.com/pois#123

0. GET http://alexshill.com/pois

<pois> <link rel="current" href="http://alexshill.com/pois"> <poi id="123"> <-- is this id the same as the one in the 39/40? <link rel="canonical" href="http://smithsonian.com/pois#123.xml"> ? fragments too? <link rel="current" href="http://alexshill.com/pois#123.xml"> <link rel="latest-version" href="http://alexshill.com/pois#123.xml"> <label>example poi</label> <link rel="author" href=""> <Location>

   serialised content

</Location> </poi> </pois>

1. GET http://alexshill.com/pois

<pois href="http://alexshill.com/pois"> <-- do we want more than one POIs in a doc? if so we need pois element <link rel="current" href="http://alexshill.com/pois"> <poi id="123"> <-- is this id the same as the one in the 39/40? <link rel="canonical" href="http://smithsonian.com/pois#123.xml"> ? fragments too? <link rel="current" href="http://alexshill.com/pois#123.xml"> <link rel="latest-version" href="http://alexshill.com/pois#123.xml"> <label>example poi</label> <link rel="author" href=""> <Location>

   serialised content

</Location> </poi> </pois>

(Note that to make things even more complicated, there is an HTTP header, Link, which is equivalent to having a link inline)

On links and serialization: 1. <Location>

   serialised content

</Location>

1.a <Location href="">

   serialised content

</Location>

2. <Location>

   <link rel="canonical" href="http://example.com/pois/123/location">
   serialised content

</Location>

3. <Location>

   <link rel="canonical" href="http://example.com/pois/123/location">
   <polygon term="parcel">
      <link rel="canonical" href="http://example.com/pois/123/location/parcel">
       serialised content
   </polygon>
   <polygon term="footnote">
      <link rel="canonical" href="http://example.com/pois/123/location/footnote">
       serialised content
   </polygon>

</Location>

4. <Location>

   <link rel="alternate" href="http://example.com/pois/123/location/full">  <-- points to example 3.
   <link rel="canonical" href="http://example.com/pois/123/location">
   <polygon term="parcel">
      <link rel="canonical" href="http://example.com/pois/123/location/parcel">
       serialised content
   </polygon>

</Location>

   <polygon href="..." rel="canonical">
    <pos>3 4 5 1</pos>   
   </polygon>
   <address href="..." rel="canonical">
   1234 Mockingbird Lane
   </address>

</location>

   <polygon >
   <link href="..." rel="canonical"/>
    <pos>3 4 5 1</pos>   
   </polygon>
   <address>
       <link href="..." rel="canonical"/>
   1234 Mockingbird Lane
   </address>

</location>