54
Copyright © 2015 Open Geospatial Consortium.
The GeoJSON encoding seems a good alternative because we will have a homogeneous encoding where a GeoJSON-context will link to other GeoJSON files that will contain
real simple features. The problem is that JSON doesnt provide native file linking mechanism and GeoJSON-context was forced to propose one based on the transposition
of the Atom link mechanism. The adoption of this or other linking mechanism on the web it not expected soon so it is not expected that this approach is useful in web search
engines.
As we have demonstrated before, JSON-LD provides an alternative way of linking resources on the semantic web. Is it possible that search engines adopt some form of
JSON or JSON-LD in the future? It seems so. In fact, Google is already experimenting with JSON-LD for describing critical reviews of web resources:
https:developers.google.comstructured-datacritic-reviews. JSON-LD could be a promising alternative in the future.
8.2.3 HTML as a natural way for linking. OWS Context encoded in HTML
Everybody knows that HTML was designed with the linking capacity in mind. Both, users reading HTML and automatic crawlers, transverse links all the time. HTML seems
the natural selection for linking JSON on the web. The question is how to complement the linking mechanism with some additional metadata that search engines could use for
indexing. A solution could come from mechanism that web search engines already had agreed to use for better indexing: Microdata.
Microdata is a WHATWG
3
HTML specification that provides both vocabulary and strategies to embed metadata within existing content on web pages. Search engines, web
crawlers, and browsers can extract and process Microdata from a web page and use it to provide a richer browsing experience for users Google, Microsoft and Yahoo rely on
this markup. In particular, provide more relevant results to users. Microdata can also be considered an annotating mechanism in HTML elements with machine-readable tags.
Microdata vocabularies provide the semantics, or meaning of an Item. The aim is to use Microdata to achieve better results in searches and also better presentations in the found
items
Figure 3: A found recipe presentation in Google search results
3
Web Hypertext Application Technology Working Group
Copyright © 2015 Open Geospatial Consortium.
55 A collection of commonly used markup vocabularies are provided by Schema.org
schemas which include: Person, Event, Organization, Product, Review, Review- aggregate, Breadcrumb, Offer, Offer-aggregate. Where possible, authors are encouraged
to re-use existing vocabularies, as this makes content re-use easier. It is also possible to create a custom vocabulary that better fits the purpose.
In this section we are going to explore the current use of common vocabularies to describe geospatial resources. Our purpose is to illustrate how this approach could work
in practice and present the approach as a possible encoding for OWS Context in HTML. This section presents a solution that validates correctly in the Google Structured Data
Testing Tool https:developers.google.comstructured-datatesting-tool. The possibility of defining a new vocabulary for describing geospatial resources can be considered later
by the OWS Context group.
The simple use case that we are going to consider here is a list of resources that could be GeoJSON or TIFF files available on the web. To expose them we are going to create a
web page that is going to link them. The common object in the Microdata vocabulary that better fits with OWS Context is the “Product” vocabulary. It is possible to create a web
page that enumerates a list of products http:schema.orgProduct and for each product it is possible to include one or more offers http:schema.orgOffer. This way we are
going to map the product concept to the resource concept in OWS Context and the offer concept to the offering concept in OWS Context.
One of the simplest examples in the currently approved OWS Context atom encoding is the following:
?xml version=1.0 encoding=UTF-8? ?valbuddy_schematron ..owc.sch?
?xml-model href=..atom.rnc type=applicationrelax-ng- regular-syntax?
feed
link rel=profile href=http:www.opengis.netspecowc-atom1.0reqcore
title=This file is compliant with version 1.0 of OGC Context
idhttp:www.opengis.netowc1.0examplesgeotiffid titleGeoTIFF Exampletitle
subtitle type=html GeoTIFF Example
subtitle author
nameJoan Masóname author
updated2012-11-04T17:26:23Zupdated entry
idftp:ftp.remotesensing.orgpubgeotiffsamplesgdal_egce a.txtid
titleGeoTIFF Exampletitle
