- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Jun 2018 13:05:34 +0000
- To: public-sdwig@w3.org
I haven't given it much thoughts, but I wonder if we could follow a sort of data pipeline to categorize technologies, completed with a couple of other sections, as was done in the media roadmap (capture, process, distribute, playback). This could help break group 1 a bit. For instance, reusing the subcategories names that you have in the proposed structure, we could have: - capture spatial/sensor data - "to get a device's location" - relevant parts of SensorThingsAPI - APIs based on the Generic Sensor API - relevant WoT work - represent spatial data - "to represent spatial data: vocabularies / encodings" - "moving features XML and CSV" - WoT Thing Description - "to represent geometry" - "to reference a location" - "to geotag video" - publish spatial data on the Web - "general guidelines" (without SSN related specs) - "to describe a spatial dataset" - "to present a view" (MapML, WMS, WMTS, XYZ) - "to provide access" - "to query using spatial operators" - transform spatial data (before / after publication) - Partitioning data for the web proposed by Michael - WPS - sensor data: - "general guidelines" (only SSN related specs) - "to represent: vocabularies / encodings" - "to work with" - relevant WoT work - temporal data: - "to represent: vocabularies / encodings" - stats: - statsBP - data cube, SDMX, DDI, SKOS, etc/. - existing classifications? (activities, products, etc.) -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/sdw/issues/1030#issuecomment-393874309 using your GitHub account
Received on Friday, 1 June 2018 13:05:37 UTC