Closed jkreft-usgs closed 5 years ago
from W3C DXWG : https://www.w3.org/TR/2018/WD-dx-prof-conneg-20181218/#realizations use HTTP OPTIONS and HTTP Link header field. Apparently HTTP OPTIONS was 'discouraged ' based on various tests
The landing page (what the Non Information Resource resolves to) provides a series of links to various representations. The landing page itself it only available in HTML, RDF/XML, RDF/JSON-LD and RDF/TTL. The HTML page is actually built from the RDF.
eg (ttl)
<https://geoconnex.ca/id/swmonitoring/WSC_02OJ007>
rdfs:seeAlso
<https://geoconnex.ca/data/swmonitoring/WML2/real-time/WSC/WSC_02OJ007> ,
<https://geoconnex.ca/data/swmonitoring/WFS3/hydrometric-daily-mean/WSC/WSC_02OJ007> ;
# then information resources have formats
<https://geoconnex.ca/data/swmonitoring/WML2/real-time/WSC/WSC_02OJ007>
rdfs:label "Data in real time"@en , "Données en temps reél"@fr ;
dct:format "text/html" , "text/plain" .
<https://geoconnex.ca/data/swmonitoring/WFS3/hydrometric-daily-mean/WSC/WSC_02OJ007>
rdfs:label "Daily means"@en , "Moyennes quotidiennes"@fr ;
dct:format "text/html" , "application/vnd.geo+json" .
See #11 for list we are planning to include in a context for this section of the info resource.
This is related to #1. Once we choose a word for the different views of a thing, what is the most effective way to tell a client that the different things are available?