In summary, the Architecture of the World Wide Web, Volume 1 states these principles:
URI assignment authorities and the Web servers deployed for them may benefit from an orderly mapping from resource metadata into URIs.
Decoding that:
http://www.example.org/weather/San-Francisco
vs http://www.example.com/node/3452
/data/q/2.5/
and /data/q/2.5/n/2976/
allows ./n/2976/
bad.
social contractof the URI:
http://www.example.org/weather/{location}
HTTP is your friend.
It wants to help you.
Don't abuse your friends.
HTTP metadata:
> GET /data/q/5/n/768/2014-09-11T05:30:00Z HTTP/1.1 > User-Agent: curl/7.37.0 > Host: www.mesonet.info > Accept: */* < HTTP/1.1 200 OK < Content-Length: 129465 < Content-Type: application/xhtml+xml; charset=UTF-8 < Last-Modified: Thu, 11 Sep 2014 05:37:16 GMT < Date: Mon, 15 Sep 2014 18:48:43 GMT < Accept-Ranges: bytes < Server: XProclet Server V1.0.m1 < Access-Control-Allow-Origin: * < Access-Control-Allow-Headers: accept-encoding,cache-control
Use common formats:
Or do it this way: CWOP Weather for the Bay Area
But not this way (1GB binary data):
http://nasanex.s3.amazonaws.com/NEX-DCP30/NEX-quartile/rcp26/mon/atmos/tasmax/r1i1p1/v1.0/CONUS/tasmax_quartile75_amon_rcp26_CONUS_209601-209912.nc