19:45:50 RRSAgent has joined #sdw2 19:45:50 logging to http://www.w3.org/2015/03/25-sdw2-irc 19:50:21 phila has joined #sdw2 19:50:49 Zakim has joined #sdw2 19:51:02 Hangout link https://plus.google.com/hangouts/_/event/c4jg7851fkfmo3f9sjm1ck7epe8 19:53:36 phila has changed the topic to: This is the channel for the discussion around Best practices. See the agenda at https://www.w3.org/2015/spatial/wiki/Meetings:Telecon201503025b 19:53:37 phila has changed the topic to: This is the channel for the discussion around Best practices. See the agenda at https://www.w3.org/2015/spatial/wiki/Meetings:Telecon201503025b 19:55:03 meeting: SDW Weekly B - session on Reqs for Best practices 19:55:05 chair: Ed 19:56:16 https://www.w3.org/2015/spatial/wiki/Minutes_from_Best_Practice_deliverable_group#UC-25:_Optimizing_energy_consumption.2C_production.2C_sales_and_purchases_in_Smart_Grids 19:56:49 Linda has joined #sdw2 19:58:05 Hi Linda - Can you get on Hangouts OK ? 19:58:23 MattPerry has joined #sdw2 19:58:49 Ian_Holt has joined #sdw2 19:59:53 Hi Matt & Ian R U OK with hangouts 20:00:14 Link above 20:00:40 Should be 20:01:34 Can I dial into a hangout with a phone? 20:01:37 I'm trying to listen to both conversations - nad it's already impossible 20:01:59 Matt no sorry online only 20:02:20 FransK has joined #sdw2 20:03:27 Ok. That's not going to work for my current location. I'll have to dial into the other group. 20:03:53 present+ Linda, Frans, Ed, Phil, Ian, Matt, Bart 20:04:44 zakim, pick a victim 20:04:44 sorry, BartvanLeeuwen, I don't know what conference this is 20:04:56 Bye. I'm going to jump into the other one. 20:05:03 RRSAgent, make logs public 20:05:25 scribe: Linda 20:05:33 Ed: preliminarieds 20:06:09 two housekeeping items: 20:06:27 1: email conversations should go via the public mailing list 20:06:41 at least cc 20:07:31 http://www.w3.org/2015/11/TPAC/ 20:07:32 2: we are planning the next face to face in Japan, W3C TPAC meeting. 20:07:47 Try to get there 20:08:02 stlemme has joined #sdw2 20:08:03 q+ 20:08:36 ack next 20:08:36 ack me 20:09:14 Bart: when will it be definite that we have the f2f there? Because then I can book my plane ticket as prices are rising. 20:09:15 q+ 20:09:25 ack next 20:09:27 Ed: we'll make the decision in the next week or two. 20:10:10 Phil: It will be either monday/tuesday or thursday/friday 20:10:27 If you go to Sapporo, we'll ask you your preference 20:11:36 https://www.w3.org/2015/spatial/wiki/BP_Requirements 20:11:49 Ed: we'll go quickly through the work we did at the f2f and then go on with the rest of the UC's 20:11:59 thx phil 20:12:04 https://docs.google.com/spreadsheets/d/1PSnpJYQDgsdgZgPJEfUU0EhVfgFFYGc1WL4xUX9Dunk/edit#gid=1542305387 20:13:15 ...created a spreadsheet with requirements. Will go through the list. 20:13:24 Frans are you ok with that approach: 20:13:32 Frans: ok 20:14:19 eparsons: goes through the list 20:15:41 https://www.w3.org/2015/spatial/wiki/BP_Requirements 20:17:12 ... what was the one on validation about? 20:17:33 phila: having difficulty seeing what column we're at. 20:17:56 -> RDF Data Shapes WG https://www.w3.org/2014/data-shapes/wiki/Main_Page 20:18:00 ... we have ways of validating xml, no standard for validating rdf. But the data shapes wg is working on it. 20:18:00 SHACL 20:18:30 q+ 20:18:47 -q 20:19:03 eparsons: we are also talking about whether the geometries are valid 20:19:14 ... so two things: valid data and valid geometries 20:20:00 ... the one about fuzziness is perhaps the most relevant and one we've been struggling about 20:20:02 q+ 20:20:13 ack next 20:21:06 BartvanLeeuwen: re hierarchical relations between locations: there could also be other spatial relations. Is that the same thing or a different topic 20:22:31 ... administrative connections between features. Example: child care place on fire, need to place the kids in another daycare center. 20:22:47 AndreaPerego has joined #sdw2 20:22:58 ... maybe not the one closest by, but one that is close and also from the same organization. 20:23:29 ... I could put another paragraph in my uc to clarify this. 20:23:57 eparson: or add it to the requirements doc that Frans is editing. 20:24:30 ... if you add the clarification, we'll capture it in the doc. It's a good requirement. 20:24:53 Hangout link at the top of the irc 20:25:22 I have made the request to generate http://www.w3.org/2015/03/25-sdw2-minutes.html phila 20:25:35 eparsons: 3D geometry: just x,y,x or more complex than that? 20:25:58 ... moving on to the reqs not specific to spatial data 20:26:09 I have made the request to generate http://www.w3.org/2015/03/25-sdw2-minutes.html phila 20:27:53 eparsons: reqs around performance could be difficult 20:28:09 ... we went through the first 25 or so use cases 20:28:33 +1 20:28:35 +1 20:28:37 ... I suggest we go through the rest of them now. Everybody clear about the process so far? 20:28:43 +1 20:28:51 +1 20:29:43 ... Smart cities 101 use case 20:30:19 ... a lot of information available at the links in the use case. 20:30:44 ... digging through those links seems not helpful now. 20:31:06 BartvanLeeuwen: it links to a 101 different use cases 20:31:20 eparsons: next one. Linked data for tax assessment. 20:31:59 q+ 20:32:03 ... provenance of data from authoritative sources 20:32:06 ack next 20:33:13 AndreaPerego: a similar issue was discussed in barcelona. 20:33:47 ed: yes I think it was discussed and I think we need to add it. 20:33:52 See https://www.w3.org/2015/spatial/wiki/BP_Requirements#Be_able_to_annotate_data_with_a_specification_of_what_the_information_is_.2F_where_do_you_find_the_geographic_information_for_the_wellknown_reference_like_a_zip_code 20:34:21 frans: provenance seems out of scope 20:34:40 .... because it's not typically spatial 20:34:55 eparsons: yes, I suppose. We can discuss that one. 20:35:41 ... next one: Images, e.g. a Time series of a water course 20:35:47 http://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Images.2C_e.g._a_Time_series_of_a_Water_Course_.28Best_Practice.2C_Time.2C_SSN.2C_Coverage.29 20:36:11 ... the idea of being able to capture time series of imagery. 20:36:18 ... I think we did capture that 20:36:49 ... next: droughts in geological complex environments. 20:36:52 http://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Droughts_in_geological_complex_environments_where_groundwater_is_important_.28Best_Practice.2C_Time.2C_SSN.2C_Coverage.29 20:37:50 ... isn't this modeled environment instead of real world? 20:38:06 q+ 20:38:16 ack next 20:38:36 AndreaPerego: not clear if this is about spatial data on the web 20:38:44 eparsons: no, it's not clear. 20:39:19 frans: there was a similar thing in the time group 20:39:27 eparsons: we'll move on 20:39:41 ... its not that clear to me, Chris can clarify if needed. 20:39:59 Next UC: http://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Soil_data_applications_.28Best_practice.2C_SSN.2C_Coverage.29 20:40:01 ... next: Soil data. Anything specific here? 20:40:16 ... noone argues, we'll move on 20:40:26 ... next: bushfire response. 20:40:36 http://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Bushfire_response_coordination_centre_.28Best_practice.2C_SSN.29 20:41:05 URI issue mentioned here. 20:41:08 ... reads the list of interrelated use cases. 20:41:33 ... not sure if there's anything new. Have we covered synonyms? 20:41:49 Linda: I don't think so. 20:41:59 eparsons: Frans? can you remember? 20:42:10 q+ 20:42:13 frans: no, I can't think of one 20:42:23 eparsons: so we'll need to add it. 20:43:28 AndreaPerego: a related req is place names can change and people use unofficial names. 20:43:54 ... not sure if we can merge these all together. Maybe should be separate, but are related. 20:44:15 See: https://www.w3.org/2015/spatial/wiki/BP_Requirements#Named_places_can_overlap_and_change_over_time 20:44:39 eparsons: definitely a key requirement 20:44:54 frans: all data on the web can change 20:45:35 eparsons: true, but there are issues that are more complex. Like colloquial geography. 20:46:28 Linda: important for cultural heritage use cases 20:47:00 frans: i remember Chaals made a point of scoping the requirements because we should be careful not to have too much work. 20:47:08 +1 20:47:13 ... and this is not typically spatial, so out of scope. 20:47:22 Not sure... 20:47:46 +1 Andrea 20:48:06 eparsons: maybe discuss this offline / via email. Maybe not typically spatial but there is a spatial element to the problem. Not convinced we can drop this. Discuss via email. 20:48:16 More discussion needed indeed. 20:48:24 ... will try to come up with a convincing example. 20:48:41 ... next: observation of geological samples 20:49:08 ... nothing use here except things for the other group 20:49:24 BartvanLeeuwen: my comment was about the previous question. 20:49:37 eparsons: next: spatial sampling, Covered by the other group. 20:50:09 ... next: Select hierarchical geographical regions. Again the hierarchy req we were discussing. 20:50:40 http://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Select_hierarchical_geographical_regions_for_use_in_data_analysis_or_visualisation_.28Best_practices.2C_Time.2C_Coverage.29 20:50:52 ... the changing over time thing comes up in this uc. 20:51:37 ... next one :satellite data processing. More for the other group. 20:51:40 http://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Satellite_data_processing_.28Best_practice.2C_SSN.2C_Coverage.29 20:51:45 ... the ones on marine observations as well. 20:52:25 ... next: BIM. anything new here Linda? 20:52:38 Linda: no, everything covered 20:52:47 eparsons: next: landsat data services 20:53:22 http://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Metadata_and_Search_Granularity_.28Best_Practice.2C_Time.29 20:53:23 q+ 20:53:39 ... related to level of granularity and URIs. Nothing new, anyone? ? 20:54:25 AndreaPerego: how to make available spatial data that may be not easily consumable by web applications. 20:54:52 ... depending on granularity you can have huge files. 20:55:24 ... a req could be to describe the data in the metadata 20:55:49 ... the use case should be described more clearly 20:56:26 eparsons: are you talking about something in the middle between metadata and very finegrained data. 20:56:37 AndreaPerego: yes, exactly. 20:56:46 eparsons: is this a new requirement? 20:56:56 ... lets put this on the email 20:57:12 +1 20:57:55 ... not going to rush through the rest of the uc's. Next week: start with Crowd sourced earthquake observation information, nr 42. 20:57:58 http://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Crowd_sourced_earthquake_observation_information_.28Best_Practice.2CSSN.29 20:58:14 ... and will have at least a couple of email discussions. 20:58:16 zakim, list participants 20:58:16 sorry, phila, I don't know what conference this is 20:58:32 ... everybody ok with the process? 20:58:32 present+ AndreaPerego 20:58:36 Linda: this is fine 20:58:37 +1 20:58:39 present+ Linda, Ed, Andrea, Ian, stlemme, Bart 20:59:02 I have made the request to generate http://www.w3.org/2015/03/25-sdw2-minutes.html phila 20:59:03 eparsons: anything else ?thanks everyone for calling. 20:59:10 we'll use Hangout again 20:59:14 bye! 20:59:22 I have made the request to generate http://www.w3.org/2015/03/25-sdw2-minutes.html phila 20:59:37 thanks phil ! 21:03:25 thx ed bye 21:05:39 I have made the request to generate http://www.w3.org/2015/03/25-sdw2-minutes.html phila