Closed pietercolpaert closed 5 years ago
This seems like a good use of Hydra. However, I would not add tiles:longitudeTile, tiles:latitudeTile, and tiles:zoomTile to Hydra itself, I would definitely create a separate vocab (+spec?) for this. Hydra could refer to this as a good example though.
What do we mean to indicate by hydra:manages <http://www.wikidata.org/entity/Q34442>
?
What do we mean to indicate by
hydra:manages <http://www.wikidata.org/entity/Q34442>
?
I removed that from my proposal above now. It was a gimmick to say that the types of the things in this collection were of the type Roads. I’m working on a JSON-LD tiling mechanism to describe roads.
Geospatial tiling in e.g., OpenStreetMap works according to a formula. When you open a map, and you want to know which tiles you have to show, you have to use a formula (https://wiki.openstreetmap.org/wiki/Slippy_map_tilenames#ECMAScript_(JavaScript/ActionScript,_etc.)) to calculate which tiles you need, and fill out the description of these tiles in a URI template as follows:
https://c.tile.openstreetmap.org/{z}/{x}/{y}.png
which results in a URL like https://c.tile.openstreetmap.org/15/16722/10964.pngI think this tiling strategy is pretty powerful, and want to be able to express this in my Linked Data documents as a hypermedia form.
My current suggestion to describe this would be as follows:
Currently this introduces 3 new properties: tiles:longitudeTile, tiles:latitudeTile, and tiles:zoomTile. Do you think adding these semantics within the Hydra spec makes sense, or should I add these elsewhere?