Updates related to ACTION-218

I've added 2 sections with the work we did for the Dutch FD, more to come

bp/index.html

@@ -1060,6 +1060,11 @@ <h4 class="subhead">Benefits</h4>
                 done by software agents and other services like <a
                   href="https://www.google.co.uk/landing/now/">Google Now</a> that interpret
                 information.</li>
+              <li>Map your source data of your SDI dynamically to crawlable resources on the web with the [[R2RML]] 
+                standard. With this process you'll generate crawlable data from features in your spatial
+                data at query time. By using the R2RML it is possible to expose more detailed information and
+                references then with standard WFS
+              </li>
             </ul>
             <p class="issue" data-number="181">More discussion is required on how to structure
               meaningful (spatial) queries with search engines (e.g. based on identifier, location,
@@ -1880,6 +1885,9 @@ <h3>Spatial Data Access</h3>
               endpoint e.g. expose the underpinning postGIS database via SPARQL endpoint (using
               something like <a href="http://www.melodiesproject.eu/content/ontop-spatial"
                 >ontop-spatial</a>) and Linked Data API.</p>
+            <p>3. Provide a default link to web friendly data, use 'rdf_seealso' as spatial feature attribute
+              to point to the web friendly representation of the feature accessd through the SDI
+            </p>
             <figure>
               <img src="images/bp28-example.PNG"
                 alt="Example of providing an alternative access path to WFS GML source data" />