Requirements from UC-50

Dear Frans, Ed,

for the last usecase "50 Incorporating geospatial data (e.g. 
geo-referenced geometry) into interactive 3D graphics on the web (Best 
Practice)" at 
https://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Incorporating_geospatial_data_.28e.g._geo-referenced_geometry.29_into_interactive_3D_graphics_on_the_web_.28Best_Practice.29
I identified the following already gathered requirements:
  * URIs
  * RESTful API (not necessarily using JSON)
  * Data should be streamable (a consumer should be able to do something 
meaningful before the end of the data message is received)
  * All best practices should be applicable to 3D data. - obvious 
requirement for this usecase
  * Best practices should support tiling (for raster and vector data, 
for two or three dimenions) - in conjunction with streaming
  * spatial data on the web should be compressable (for optimization of 
data transfer)

Moreover, I suggest the following additional requirements to be 
considered for best practices:
  * Spatial data with a visual representation should be offered in 
delivery formats and encodings that are (preferably natively) supported 
by web browsers
  * Efficient content delivery (bandwidth-wise is already covered by 
requirement "spatial data on the web should be compressable"), but it 
does not cover the processing overhead for the visualization on the 
consuming client-side application that should be almost none or negligible
  * Consuming spatial data should seamlessly work with widely used and 
established libraries of web developers, such as jQuery

Please feel free to incorporate this into the spreadsheet as I was not 
able to do so.
Comments are appreciated as usual.

Unfortunately, I will not be able to join today's call.
Thus, I'll follow the discussion offline in the minutes.

Best regards,
Stefan

Received on Wednesday, 15 April 2015 19:30:57 UTC