08:09:20 RRSAgent has joined #dwbp 08:09:20 logging to http://www.w3.org/2014/03/31-dwbp-irc 08:09:24 Zakim has joined #dwbp 08:10:15 PhilA has changed the topic to: Agenda https://www.w3.org/2013/dwbp/wiki/London_2014 08:10:21 agenda: https://www.w3.org/2013/dwbp/wiki/London_2014 08:11:10 chair: HadleyBeeman 08:11:35 meeting: DWBP WG F2F meeting, day 1 08:12:30 passcode 3927# is not valid, don't get voice connection 08:12:53 was there also going to be a skype session? 08:13:11 Yes, Makx 08:13:20 Deirdre is working on getting a laptop set up for that 08:13:44 OK hasn't the meeting started yet? 08:13:53 makxdekkers we're getting set up 08:14:16 OK, gives me time to grab a coffee 08:14:20 go for it 08:14:21 :) 08:14:21 ah ok.. it gives me time to do other stuff ;) 08:16:31 Ig_Bittencourt has joined #DWBP 08:17:42 JohnGoodwin has joined #DWBP 08:17:51 CarlosIglesias has joined #dwbp 08:17:51 RickRobinson has joined #DWBP 08:18:43 deirdrelee has joined #dwbp 08:19:03 Vagner_Br has joined #dwbp 08:19:04 markharrison has joined #dwbp 08:19:07 BrianMatthews has joined #DWBP 08:19:34 We're sorting out the A/V and the phone line … bear with us 08:20:00 Okay standing by 08:20:46 zakim, room for 5? 08:20:49 ok, PhilA; conference Team_(dwbp)08:20Z scheduled with code 3927 (DWBP) for 60 minutes until 0920Z; however, please note that capacity is now overbooked 08:20:58 zakim, code? 08:20:58 the conference code is 3927 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), PhilA 08:21:42 Team_(dwbp)08:20Z has now started 08:21:50 +Makx_Dekkers 08:21:55 + +1.509.554.aaaa 08:22:14 zakim +1.509.554.aaaa is ericstephan 08:22:19 + +44.207.202.aabb 08:22:22 Connected voice 08:22:32 zakim, aabb is Steve 08:22:32 +Steve; got it 08:22:33 zakim, +1.509.554.aaaa is ericstephan 08:22:33 +ericstephan; got it 08:23:32 For those wanting to join webcam, we can connect via my skype: deirdrelee 08:23:42 zakim, who is here? 08:23:42 On the phone I see Makx_Dekkers, ericstephan, Steve 08:23:44 On IRC I see BrianMatthews, markharrison, Vagner_Br, deirdrelee, RickRobinson, CarlosIglesias, JohnGoodwin, Ig_Bittencourt, Zakim, RRSAgent, PhilA, ericstephan, gatemezi, 08:23:44 ... MakxDekkers, ivan, trackbot 08:24:45 zakim, Steve has Hadley, Yaso, PhilA, deirdrelee, BrianMatthews, Ig_Bittencourt, Antoine 08:24:45 +Hadley, Yaso, PhilA, deirdrelee, BrianMatthews, Ig_Bittencourt, Antoine; got it 08:24:48 zakim, Makx_Dekkers is me 08:24:48 +MakxDekkers; got it 08:25:40 topic: Welcome 08:25:58 Steve: Welcomes everyone, thanks those who have flown/travelled to be here 08:26:10 I wish I could be there with you all 08:26:25 ... attended conference on 50 years of alleviating proverty, programme begun by LBJ 08:26:28 scribe: PhilA 08:26:30 HadleyBeeman has joined #dwbp 08:27:02 Steve: Percentage of population in poverty reduced, absolute numbers increased 08:27:14 yaso has joined #dwbp 08:28:05 Steve: tells a story about how people know each other, but many people don't work together. Seems a lost opportunity 08:28:18 Caroline_ has joined #DWBP 08:28:44 Steve: Describes outcome of meeting, plan was to put collected papers into a new book 08:29:04 ... problem is that people aren't working together 08:29:43 ... so our job is to provide standards that allow people to work together. That's what we're trying to achieve - better collaboration through open data 08:29:57 ... we have a chance to make a big difference 08:30:01 ... people are looking at us 08:31:04 Topic: The Name Game 08:31:15 rrsagent, make logs public 08:32:41 Guest: Rick Robinson 08:32:52 Rick: Works on smart cities for IBM 08:33:09 JohnGoodwin: Introduces himself 08:33:40 markharrison: Here today to represent GS1 (although works for Cambridge University) 08:33:59 ... mentions LOD project at GS1 08:34:18 Laufer: Intrduces self 08:35:22 deidre my skype name is makxdekkers 08:36:03 I can now see them all.. Thanks Deirdre ;) 08:36:24 yaso has joined #dwbp 08:37:07 Vagner_Br: Introduces himself 08:37:40 bernadette: Introduces herself, from Recife in NE Brazil 08:37:47 Ig_Bittencourt: Introduces self 08:38:43 Newton: Introduces self (from Nic.br) 08:39:14 Flavio: Introduces self from Sao Paolo 08:39:58 Guest: Phil Tetlow 08:40:31 PhilT: Introduces self and recognises follow IBMers 08:41:39 Adriano: Introduces self 08:41:55 ... interested in big data, data mining etc 08:42:28 Antoine: Introduces self from Europeana 08:43:34 CarlosIglesias: Introduces self 08:45:12 ... experience with OD in Spain, working with Web Foundation, CTIC etc. 08:45:21 Guest: Brain Matthews 08:46:15 laufer has joined #DWBP 08:46:26 +laufer 08:47:03 BrianMatthews: Introduces self from STFC (Science and Technology Facilities Council) - astronomy, physics etc. 08:47:34 antoine has joined #dwbp 08:47:56 BrianMatthews: refers to SKOS, see http://www.w3.org/TR/skos-primer/ 08:48:03 raphael has joined #dwbp 08:48:29 deirdrelee: Introduces self 08:49:08 antoine has joined #dwbp 08:49:35 -MakxDekkers 08:49:48 yaso: Introduces self 08:50:33 +MakxDekkers 08:51:55 PhilA: Introduces self 08:52:00 HadleyBeeman: Introduces self 08:52:14 + +33.4.93.00.aacc 08:52:31 zakim, aacc is gatemezi 08:52:32 +gatemezi; got it 08:53:26 gatemezi: Introduces self (from Eurecom) 08:53:30 -MakxDekkers 08:53:39 zakim, who is here? 08:53:39 On the phone I see ericstephan, Steve, gatemezi 08:53:41 Steve has Hadley, Yaso, PhilA, deirdrelee, BrianMatthews, Ig_Bittencourt, Antoine 08:53:41 On IRC I see antoine, raphael, laufer, yaso, Caroline_, HadleyBeeman, BrianMatthews, markharrison, Vagner_Br, deirdrelee, RickRobinson, CarlosIglesias, JohnGoodwin, Ig_Bittencourt, 08:53:41 ... Zakim, RRSAgent, PhilA, ericstephan, gatemezi, MakxDekkers, ivan, trackbot 08:54:16 +MakxDekkers 08:54:28 ericstephan: Introduces self 08:54:49 https://plus.google.com/hangouts/_/7ecpi31t3gsbcrq6onet5o0280 08:54:54 I'll post it on wiki too 08:55:21 I have made the request to generate http://www.w3.org/2014/03/31-dwbp-minutes.html raphael 08:55:23 PhilA: Just to note that ericstephan and BrianMatthews have similar interests here 08:55:24 s/Sao Paolo/NIC.br, Sao Paulo/ 08:55:37 MakxDekkers: Introduces self 08:55:57 MakxDekkers: Consultant in Spain, works with PhilA on an EC project 08:56:07 BrianMatthews Kerstin Kleese Van Dam (my manager) sends her greetings to you. 08:57:19 maybe, I don't hear you guys not so well either 08:58:51 Google Hangout details on wiki: https://www.w3.org/2013/dwbp/wiki/London_2014#Google_Hangout 08:59:50 BernadetteLoscio has joined #dwbp 09:06:14 -MakxDekkers 09:07:11 Disconnected phone line. Hearing you on hangout 09:09:38 @all , I will send regret in 30 minutes for one hour because I have an appointment with my Doctor.. Sorry for that :( 09:09:47 Oh dear — sorry makxdekkers. We'll see if we can fix that 09:09:52 Bye for now, gatemezi! 09:10:10 zakim, who is here? 09:10:10 On the phone I see ericstephan, Steve, gatemezi 09:10:12 Steve has Hadley, Yaso, PhilA, deirdrelee, BrianMatthews, Ig_Bittencourt, Antoine 09:10:12 On IRC I see BernadetteLoscio, antoine, raphael, laufer, Caroline_, HadleyBeeman, BrianMatthews, markharrison, Vagner_Br, deirdrelee, RickRobinson, CarlosIglesias, JohnGoodwin, 09:10:12 ... Ig_Bittencourt, Zakim, RRSAgent, PhilA, ericstephan, gatemezi, MakxDekkers, ivan, trackbot 09:10:26 zakim, steve has me 09:10:26 +HadleyBeeman; got it 09:11:20 ivan has left #dwbp 09:13:24 newton has joined #dwbp 09:13:29 adrianov has joined #dwbp 09:15:18 Topic: Target for meeting 09:15:21 yaso has joined #dwbp 09:15:48 HadleyBeeman: We hope to get to the point by end of tomorrow that we can publish the First Public Working Draft of the Use cases document 09:16:13 ... an issue that has come up a lot, is how we work together. So I want to talk about how we can organise ourselves 09:16:20 ... we need to do things that make sense to us 09:16:26 ... we have to be working in the open 09:16:38 ... everyone can see what we're doing (e-mails are publicly archived) 09:16:42 ... but we can use whatever we like 09:16:47 ... to build the deliverables 09:16:54 fkyanai has joined #dwbp 09:16:59 ... quick reminder of the deliverables 09:17:07 ... minimum things are 3 docs 09:17:22 ... the Best Practices Recommendation (some bullet points) 09:17:35 -> http://www.w3.org/2013/05/odbp-charter charter 09:17:56 HadleyBeeman: We can work through that bullet list. We can drop them, add news ones, they're just a guide 09:18:12 ... in addition, the WG agreed to create UCR 09:18:33 ... we may well decidce that we need to write more, split the BP into multiple documents. We have a lot of leeway 09:18:41 ... but this is what we begin with 09:18:59 ... Vagner was concerned about keeping track of our work on the UCR 09:19:12 ... the wiki makes it easy to make lists, centralise things etc. 09:19:39 -> https://www.w3.org/2013/dwbp/wiki/Use_cases_timetable Use Cases timetable 09:20:00 ... probably want to change the wiki homepage 09:20:31 ... a big part of the chairs' job is to make the wiki useful and useable 09:20:59 laufer: I think the main page can be a little confusing if it has too many items 09:21:15 ... the main things of the groups are there 09:21:55 Topic: The Use Case document 09:22:12 deirdrelee: Following on from what Hadley said... we've been working on the UCR doc 09:22:28 ... aim is that it is a lead into the deliverables (BP, QDV, DUV) 09:22:42 ... goal is FPWD of UCR 09:23:04 rainbow has joined #dwbp 09:23:06 deirdrelee: We suggest that we start from the challenges 09:23:28 ... what were the problems/issues - so this is where we could potentially help 09:23:39 Caroline_ has joined #DWBP 09:23:40 ... yaso made the point about highlighting positive aspects 09:24:33 ... the challenges are in the Google doc https://docs.google.com/spreadsheet/ccc?key=0AhTZf3B9yQ3odGVvU3pBazFsY3pyUVppNDFSZGtyQkE&usp=sharing&richtext=true#gid=2 09:24:40 ... is the challenge relevant? 09:24:56 ... so data on the Web should ... to make it reusable for example 09:25:07 ... data should be in format X to be reusable 09:25:14 ... or should include metadata Y to be reusable 09:25:22 ... and then we need to consider whether it's in scope 09:25:27 ... is it in scope of W3C in general 09:25:52 ... (i.e. about the technical infrastructure of the World Wide Web) 09:26:02 ... and is it within our own expertise 09:26:20 ... if so, then it becomes a requirement for one of the deliverables (potentially more than one) 09:26:57 deirdrelee: refers to 09:27:02 -> http://www.w3.org/TR/csvw-ucr/ CSVW UCR 09:27:25 Steve: I just want to ask about data on the Web, Open data, and data 09:27:37 ... do we mean that these thingsa re the same or that these things are different? 09:27:45 laufer: I think for each of us it's different 09:28:17 laufer: I am one of the people discussing this and the metamodels that we have 09:28:34 ... things like CKAN and Soctrata have their own metamodels 09:28:39 q+ 09:28:51 Steve: So What did you mean when you wrote the charter 09:28:58 scribenick: hadleybeeman 09:29:11 q+ 09:29:37 phila: It began as the "Open Data Best Practices" working group. But discussing it, it became clear that was too narrow. 09:30:08 … for example, one of the papers presented at that workshop were from Fujitsu, who use open data to augment a private system. Healthcare needs. The technology they use is the same, whether open or not. 09:30:20 … So, from a tech point of view, any distinction is irrelevant. 09:30:27 q+ 09:30:35 … A lot of our use cases will be open data, but we must not exclude non-open data. 09:30:48 yaso: I'd like to suggets a radical way through this 09:30:54 scribenick: phila 09:30:57 ... I think today we can talk about data on the Web, not open data 09:31:16 q? 09:31:20 ack yaso 09:31:25 yaso: There's too much focus on open data. We spent too much time talking about publishing and not eneugh about reuse 09:31:57 q+ 09:32:53 steve: w3C does web standards. A city may do a lot of things before publishing data that may be out of scope for the W3C. Does "Data on the Web" show the distinction between what a group does before publication, vs out on the web? 09:33:22 Laufer: When you want to put this data on the Web, you have to make a transformation. This is the issue here. Our recommendation. 09:33:39 Phila: That's not ON the web — that's using the web as a glorified file transfer system 09:33:49 q? 09:34:03 Do we need a "Data on the Web" definition document to bound this? CSV on the Web made something similar to define and bound tabular data http://w3c.github.io/csvw/syntax/ 09:34:06 q+ 09:34:11 q+ 09:34:12 ack rick 09:34:25 RickRobinson: I'll start from the city councils that I work with 09:34:47 ... they have a lot of data that they want to open, but don't have the tech skills to do some of the things we talk about 09:35:06 ... I think it would be helpful to have a common language for tech and non-tech people 09:35:18 PhilA: Nods to 5 stars of LOD 09:35:37 RickRobinson: There's a section in the UCR on the revenue models tha implies that open data is freely available 09:35:41 ... that's contentious 09:35:52 ... is this WG getting into this area? 09:36:00 PhilA: Nods to recent Web payments Wworksho[p 09:36:06 ack ericstephan 09:36:21 ericstephan: Do we need a data on the web definition doc 09:36:38 ... in the CSVW WG we found ourselves in the predicament of defining tabular data - surprisingly 09:36:56 ... in science we're always pushing at the edge of the definition 09:37:09 ... so maybe we need a separate definition doc to define that 09:37:11 ack antoine 09:37:28 antoine: OP/Data I agree that we should try to ignore it for now. Maybe consider it later 09:37:36 q+ 09:37:41 ... and then see what others have done 09:37:56 q+ 09:38:04 ... as for data on the Web... it's up to us to make it better, not say that your council's PDF is bad 09:38:49 antoine: You started with data vs data on the Web - but in our rec we should make sure that some of the work applies earlier in the process 09:39:10 ... if we want them to be implemted properly, X needs to be done before it makes it to the Web 09:39:47 Steve: I think there's way to do this. The charter preserves scope but gives us a limit to where we can go. i.e. not reinventing data dictionaries for mainframes 09:39:57 ... but we can say what we expect to find in data and metadata on the Web 09:40:02 ... we expect lineage, names etc. 09:41:06 PhilA: We can recommend methods for doing that 09:41:09 ack yaso 09:41:16 q- 09:41:31 -gatemezi 09:41:37 yaso: I want to highlight the definition of open data. I don't want to discuss those now 09:41:43 http://opendefinition.org/ 09:41:46 ... it's another reason for me to forget about OD for now 09:42:08 ... we don't want to discuss licences? 09:42:19 Steve: Some of our use cases are open data oriented? 09:42:30 yaso: I want some use cases on closed data 09:42:52 q+ 09:42:56 Steve: You want the WG to cover non-open data? Copyrighted data? 09:43:06 q+ 09:43:14 Agreed Steve to not covering copyrighted or closed data 09:43:15 yaso: There are many licences that offer less than opnness 09:43:20 q+ to ask about the technical differences between open and closed (closed licenced) data 09:43:26 RickRobinson: Is your point that there are issues that are technical? 09:43:26 q+ 09:43:39 +q 09:43:40 q+ 09:43:49 RickRobinson: and these are separate from open data in a legal or financial issues? 09:43:51 yaso: Yes 09:44:13 yaso: I can collect data from my car and put it on the Web, say with a CC licence 09:44:25 ... maybe CC-NC 09:44:31 ack markharrison 09:44:32 ack mark 09:44:58 markharrison: Going back to what Steve was saying, I'm not sure we need to differenitate between open/closed, dumps. 09:45:03 ... what about liability issues? 09:45:32 ... there's new EU food labelling obligations saying that it must be available online and the same as found on the packaging 09:45:50 ... the retailer may want to reuse/reference that data in their own site , and there can be apps that reuse it 09:46:07 ... so we need to think about licences, yes, but also liability, up to date 09:46:11 ack CarlosIglesias 09:46:36 CarlosIglesias: On open/other - I tend to agree that from the tech perspective that's not important 09:46:52 ... we also have the linked/non-LD approaches 09:46:58 ... most of us work with LOD 09:47:08 ... but it's not only about technology 09:47:25 ... most of us are familiar with the underlying principles 09:47:33 MakxDekkers has joined #dwbp 09:47:40 ... we often ttalk about data not following 5 Star paradigm 09:48:11 ->http://5stardata.info/ In case anyone here is unfamiliar with the 5 stars of open data 09:48:30 CarlosIglesias: There are some basic principles that we all agree on? Licences etc? 09:48:54 ... we are already not focusssing on non-tech issues 09:49:55 CarlosIglesias: We are already talking about all these points, open government principles, bring value to open data 09:50:00 q- 09:50:03 q? 09:50:20 q- 09:50:48 http://www.w3.org/TR/gov-data/ 09:50:57 https://public.resource.org/8_principles.html 09:50:58 To me if data is not following 5 star, it is not in scope of this group that means not even meeting the 1 star criteria. How could it be data on the web then? 09:51:47 Steve: Tells story about Long Beach defibrillator. 09:52:04 ... ideas was to publish data on where these things are around the city 09:52:23 ... what happens if the data is wrong because it was used and not put back 09:52:36 ... need to have indemnity 09:52:59 ... we can't stipulate that, but we can't offer advice on legal areas 09:53:14 Steve: So I think we can be aware of these issues 09:53:17 q+ 09:53:39 lost my conection. Now conference bridge does not allow dial-in: this conference is restricted at this time 09:53:47 ack ig 09:54:13 Ig_Bittencourt: I think we should ignore the open/non-open distinction 09:54:24 ... it's not important for us as such 09:54:26 oh dear, makxdekkers. We'll try to sort it in 2 or 3 minutes 09:54:27 ack HadleyBeeman 09:54:27 HadleyBeeman, you wanted to ask about the technical differences between open and closed (closed licenced) data 09:54:42 zakim, code? 09:54:42 the conference code is 3927 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), PhilA 09:54:51 zakim, room for 4? 09:54:52 ok, PhilA; conference Team_(dwbp)09:54Z scheduled with code 3927 (DWBP) for 60 minutes until 1054Z 09:55:20 I am back on hangout with sound 09:55:25 HadleyBeeman: I keep trying to work out what is tech and can be written and what is out of our scope 09:55:56 HadleyBeeman: We can provide the mechanism through which people can describe how accurate/reliable their data is 09:56:02 ... what they say is out of our ken 09:56:05 q? 09:56:07 ack BrianMatthews 09:56:21 BrianMatthews: I also wanted to reiterate that open data might be a red herring 09:56:34 ... from the science perspective, the data might be free but it's not necessarily open 09:56:49 ... sometimes specific people/groups are able to read the data 09:57:04 ... doesn't matter about that here - it's delivered by Web protocols 09:57:29 ... as for whether we should have stars etc. We should look for best practices that help take people forward 09:57:31 +1 BrianMatthews proposal 09:57:37 ack BernadetteLoscio 09:58:09 BernadetteLoscio: I think we're talking about data which can be unstructured, structured. I don't think we're concerned about non-structured data 09:58:49 BernadetteLoscio: Structured data maybe a relational data, Excel etc. Non-structured can be anything such as text 09:58:55 q+ 09:59:29 BernadetteLoscio: When we start to think about this we come back to some of the principles of open data 09:59:39 q+ to talk more about structured vs. unstructured data 10:00:30 +1 to support the idea of having principles 10:00:45 Ig_Bittencourt_ has joined #DWBP 10:00:51 BernadetteLoscio: Maybe we should think about principles for data on the web which may not be the same as principles of open data 10:01:00 q? 10:01:05 scribe: Ig_Bittencourt 10:01:19 q+ 10:01:50 q- 10:02:05 ack phila 10:02:07 ack PhilA 10:02:41 PhilA: Does everybody know what 5 start data are? 10:02:41 -> http://5stardata.info/ 5 star LOD 10:02:49 q+ 10:03:08 ... the difference we might have to change 10:03:21 ... first of all about open and close 10:03:41 ... there is another 5 start which is useful is 10:03:45 Tim Davies 5 stars of data engagement http://www.timdavies.org.uk/2012/01/21/5-stars-of-open-data-engagement/ 10:04:06 ... not just about use the data but feedback 10:04:18 and these are other 5 start that could be useful 10:04:37 q? 10:04:37 Available on coffee mug! :-) http://www.cafepress.com/mf/45953815/five-star-linked-data_mugs?productId=480759174 10:04:38 q? 10:04:53 spot on, ericstephan! 10:05:08 http://www.opendataimpacts.net/engagement/ 10:05:19 ack CarlosIglesias 10:05:19 CarlosIglesias, you wanted to talk more about structured vs. unstructured data 10:05:35 CarlosIglesias: I would like to get back about the format 10:05:47 Antoine: This is the original from TimBL? http://www.w3.org/DesignIssues/LinkedData.html 10:05:57 ... a PDF already could be data on the web 10:06:25 ... PDF structured or non-structure data depends how you publish it 10:06:42 ... it is not about how the data is, but how to use it 10:06:56 -> http://www.w3.org/DesignIssues/LinkedData.html The original LOD definitions from TimBL 10:07:18 ... my point here is not to discuss philosophical points 10:07:36 ... but we need some definition and background definition 10:07:42 ... to build the best practices 10:08:00 q? 10:08:04 PhilT has joined #DWBP 10:08:06 ... every one has a difference understanding about data 10:08:09 ack Vagner_Br 10:08:22 Vagner_Br: I want to go back about deirdrelee presented 10:08:32 ... i would like to understand more about the methodology 10:08:40 ... about challenges 10:08:50 .. when we are talking about challenges 10:09:13 ... we want to reach some certain points 10:09:27 ... i would like to support the idea about define basic principles 10:10:03 ... if we define any challenge without a basic reference or common definitions could be bad 10:10:18 -> https://docs.google.com/spreadsheet/ccc?key=0AhTZf3B9yQ3odGVvU3pBazFsY3pyUVppNDFSZGtyQkE&usp=sharing&richtext=true#gid=2 Challenges 10:10:20 ... for instance, interoperability, data granurality 10:10:32 RRSAgent, draft minutes 10:10:32 I have made the request to generate http://www.w3.org/2014/03/31-dwbp-minutes.html PhilA 10:10:40 ... another example is like privacy 10:10:53 ... what are the basics about privacy 10:11:01 in order to define the challenges 10:11:09 ... even licenses 10:11:26 acl laufer 10:11:27 ack laufer 10:11:36 laufer: i think we have some issues here 10:11:39 q+ to suggest another approach on challenges and/or best practices 10:11:43 ... that are the formats of the data 10:11:49 .. we can have some information on a PDF 10:11:57 ... or in a CSV 10:12:12 ... but we are talking about the conteent and if it is relevant or not 10:12:37 ... it is valuable if the data is not structured 10:12:46 ... but if it is relevant. 10:13:13 ... we can have the CSV 10:13:31 ... if we have a recommendation bout pdf we can achieve 10:13:59 ... so I think that is not related to the format 10:14:17 just a few thoughts...I think we need to discuss data on the web, not data near the web, but when it is on the web, what are the best practices? 10:14:22 ... if a human can extract the information, it does not matther 10:14:29 === 10 Minute Break === 10:14:35 HadleyBeeman: we have 10 minutes stop 10:14:35 RRSAgent, draft minutes 10:14:35 I have made the request to generate http://www.w3.org/2014/03/31-dwbp-minutes.html PhilA 10:32:14 newton has joined #dwbp 10:34:10 newton_ has joined #dwbp 10:34:53 yaso has joined #dwbp 10:35:22 fkyanai has joined #dwbp 10:35:24 HadleyBeeman: welcome back 10:35:27 zakim, who is here? 10:35:27 On the phone I see ericstephan, Steve 10:35:29 Steve has HadleyBeeman 10:35:29 On IRC I see fkyanai, yaso, newton_, Ig_Bittencourt_, MakxDekkers, Caroline_, adrianov, BernadetteLoscio, antoine, raphael, laufer, HadleyBeeman, BrianMatthews, markharrison, 10:35:29 ... Vagner_Br, deirdrelee, CarlosIglesias, JohnGoodwin, Zakim, RRSAgent, PhilA, ericstephan, trackbot 10:35:34 q? 10:35:52 I am drinking espresso 10:35:54 zakim, code? 10:35:55 the conference code is 3927 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), PhilA 10:36:15 2.5 hours sleep and a full day ahead after this :-) 10:36:29 PhilT has joined #DWBP 10:36:38 HadleyBeeman: useful discussion about the scope 10:37:06 ... we could spend next days talking about what is useful 10:37:13 .. about what are the use cases 10:37:36 ... i would like to ask to the editors about the use cases and what is useful. 10:37:58 deirdrelee: points related to the scope 10:38:02 ... but also about the methodology 10:39:43 scribe: PhilA 10:39:47 scribe: yaso 10:40:06 Ber looking in to the use cases, we tried to collect the main problems 10:40:17 Bernadette: looking in to the use cases, we tried to collect the main problems 10:40:24 Ig_Bittencourt has joined #DWBP 10:40:30 scibe: Ig_Bittencourt 10:40:31 q+ 10:40:37 …what we need to have clear: what do we want from the use cases document? 10:40:40 s/Ber/Bernadette: 10:40:41 zakim, open queue 10:40:41 ok, PhilA, the speaker queue is open 10:40:46 q+ 10:40:57 BernadetteLoscio: we have to agree that the goal of the uc doc is about the potential BP 10:41:12 … help to identify potencial best practices? What kind of infomation we can extract from the UC elements? 10:41:13 .. and them we can look and ask if the information we have is enough 10:41:23 … do we need something else? 10:41:37 …I think these are important questions fot us 10:41:59 deirdrelee: what do we want the group to achieve... 10:42:05 ... BP in terms of challenges 10:42:14 ... it would based on different levels 10:42:17 deirdreelee: what do we want the group provide? These challenges are the core, but they can be based on use cases of different levels 10:42:40 …the best practices can be focused on the moturity of the publisher 10:42:40 ... the BP could be about different levels 10:42:42 q+ 10:43:05 q+ 10:43:10 q+ later 10:43:14 q- 10:43:19 q+ 10:43:27 ack PhilA 10:43:32 ack markharrison 10:43:38 scribe: ig_Bittencourt 10:43:48 markharrison: we have to thing not just about people publishing data on the web 10:43:58 ... but also on both sides 10:43:59 ack PhilT 10:44:01 q+ 10:44:03 q+ on data publishing, consuming and the full data cycle of life 10:44:32 PHIL: for me it is more about preserving data on the web 10:44:39 q+ 10:44:47 ... characteristics of the data 10:45:16 ... my suggestion to the group is about information management 10:45:22 ... and information dissemination 10:45:28 ... and how to best take care of the data 10:45:41 +1 PhilA 10:45:45 ... if we look at the practice of generating data 10:45:58 ... it is about the creation and structing of the data 10:46:13 .. how do we make the reference correctly 10:46:15 I was +1 PhilA comment 10:46:17 :-) 10:46:25 .. how do we now when it is not relevant anymore 10:46:53 s/PhilA/PhilT 10:47:01 s/PhilA/PhilT 10:47:28 ... the reason could work on collecting data... 10:47:33 ack antoine 10:47:47 antoine: there is an agenda about life cycle 10:48:04 +1 PhilT 10:48:07 q- 10:48:15 .. we don't actually know about BP or requirements 10:48:31 .. I would hope that this end up in requirements 10:48:31 +1 to antoine around the data lifecyle, which is also a +1 to PhilT 10:48:40 +1 to this 10:48:45 ... i would keed in challenges now. 10:49:00 ack HadleyBeeman 10:49:04 q+ 10:49:09 HadleyBeeman: how much do we do 10:49:22 +1 to antoine 10:49:28 deirdrelee: I think it would be good to keep it open 10:49:29 q+ 10:49:53 ack Vagner_Br 10:50:01 Vagner_Br: I also agree that we need to add more UC 10:50:16 .. if we want to publish BP 10:50:21 ... we need more UC 10:50:28 ... such as from Asia or Africa 10:50:30 good point+ 10:51:39 deirdrelee: we need the foundations of BP 10:52:03 ... perhaps we could start about 5 stars 10:52:05 q+ to suggest a DWBP Primer? 10:52:18 ... the more stars you have the more you have BP 10:52:34 HadleyBeeman: it is about the maturity of the data. 10:53:03 BernadetteLoscio: It also if a beginner wants to publish data on the web 10:53:16 q? 10:53:18 ... he would like to publish data on the web based on the BP 10:53:32 ... so he could be interested on data integration 10:54:04 ... for example, I small stratup publishing data on the web and could not be interested on advanced points. 10:54:26 deirdrelee: meybe the BP could be to try to encourage easy way about data on the web 10:54:32 BernadetteLoscio: It depends on the scenario 10:54:35 q+ 10:54:40 .. if you want to publish a dataset 10:54:42 s/I small/A small 10:54:55 For beginners are there "core" best practices that could be recommended? Interesting Deirdrelee 10:55:05 ... and i think it is more about the problems when you have lot of projects 10:55:13 ... you know how to solve some simple problems 10:55:20 ... and you don't know how to solve big problems. 10:55:22 ack CarlosIglesias 10:55:22 CarlosIglesias, you wanted to comment on data publishing, consuming and the full data cycle of life 10:55:37 CarlosIglesias: I really like the way the discussion is moving 10:55:46 .. from technical issues 10:55:52 .. about the preparation of the data 10:56:04 .. I think that was my ambition about the BP group 10:56:13 ... and it is connected with my initial point 10:56:17 .. about guidance 10:56:23 q? 10:56:53 .. I think it is really important we agree about the scope 10:57:26 ... for example we don't have any uc about people demading data trying to reuse not from data publishing perspecctive 10:57:56 .. it is the first think is about data publishing 10:58:03 I think we should be working on this 10:58:13 .. licensing issues 10:58:27 ... we are technical group 10:58:38 .. and there are other groups that can point about this 10:58:44 laufer: ack laufer 10:58:47 ack laufer 10:59:06 laufer: I think we have to make recommendation about the distribution of data 10:59:18 .. and we have to do recommendation about the way they link data 10:59:44 ... if the tools can make it easy to do 10:59:59 ... so I think we can forbidden about publishing the data 11:00:10 ... and we need to make recommendation about the nature of the data too 11:00:23 ... another one is about the skeleton of the UC 11:00:37 ... we could have a running example 11:00:50 s/structing/structuring/ 11:00:51 ... we have the skeleton and we don't have an example about the UC 11:00:59 ach PhilT 11:01:03 ack PhilT 11:01:15 scribe: yaso 11:01:33 Thanks. 11:01:39 ig_Bittencourt :-) 11:01:49 …Second one is Value 11:02:00 ...You can get value proposition on the use cases 11:02:37 … the 3rd one is: we have to construct credibility to this BP 11:03:10 PhilA: there’s a lot of agreement in the group, this is positive. 11:03:12 ack phila 11:03:12 PhilA, you wanted to suggest a DWBP Primer? 11:03:20 …Bernadette’s lifecicle is really important 11:03:34 …the cicle arount it is really important 11:03:39 +1 DWBP Primer 11:04:00 …we’re trying to get some use cases on the developer’s point of view 11:04:37 This is what PhilA is referring to: http://www.w3.org/TR/mobile-bp/ 11:04:47 PhilA: There’s a section on the Best practices document that says: this is how to get value.. 11:05:03 …I think i’d rather see this in the Best Practices Document 11:05:13 …so that’s kind of a beginner’s guide 11:05:14 q? 11:05:16 +1 about beginners guide 11:05:20 ack mark 11:05:51 q+ to talk about ShEX etc 11:06:16 +1 to Markharrison 11:06:19 ack phil 11:06:19 PhilA, you wanted to talk about ShEX etc 11:06:40 PhilA: we’re not talking about testing 11:07:32 …it’s about the ability to say “for this tool, you must to include the title…” 11:07:35 PhilA: New W3C working group coming on RDF validation. 11:07:51 …this is going to be useful for us 11:08:19 q? 11:09:29 We are looking at this: https://docs.google.com/spreadsheet/ccc?key=0AhTZf3B9yQ3odGVvU3pBazFsY3pyUVppNDFSZGtyQkE&usp=sharing&richtext=true#gid=3 11:10:04 loading very slow :-) 11:10:40 Sorry, ericstephan — we're going to the document linked from the bottom of the Dimensions tab 11:10:50 okay thanks 11:10:52 https://docs.google.com/presentation/d/13gakj4BzYcAMf1NCNIpXXpPwr35qkVwfKgGbsZ-fpHE/edit#slide=id.p 11:11:22 Link to the slides 11:12:38 Bernadette: the description is there. We had a discussion about the mais steps or how can we organize the steps of publishing and using data on the web 11:12:54 …we have 4 steps 11:13:20 …we can have more steps 11:13:26 …if we need it 11:13:51 I would change "Data Usage" to "Data Application and Management" 11:13:54 …we can have best practices for each step 11:14:26 q+ 11:14:27 …these steps are related to the challenges that we identified 11:14:36 q+ to ask about "data usage" as a term 11:14:41 …how we relate the challenges to each one of the steps 11:14:51 q+ 11:15:26 q+ 11:16:41 ack ig 11:16:52 ..we’re talking about this, so if you want to do something about this, use that BP.. Like a framework 11:17:14 Hadley: how the use cases fit your spiral 11:17:19 q? 11:17:36 HadleyBeeman: my question is more about “Data Usage" 11:17:48 q+ 11:17:50 q+ to talk about a similar model he has been applying in OD projects 11:17:54 …is there any difference between data usage and dara reuse? 11:18:31 PhilT: reuse is a pottencial not an action 11:18:41 q+ 11:18:46 …in software engineering the term “use” is a verb 11:18:55 ack me 11:18:55 HadleyBeeman, you wanted to ask about "data usage" as a term 11:19:03 …and the term “Reuse” is a potencial so it’s a property, not a verb 11:19:21 PhilA: my understanding is about the source of the data 11:19:51 q? 11:20:08 ack me 11:21:08 PhilA: how that we know that we included everything? 11:21:23 PhilA: somewhere in this feedback it should say: it 11:22:00 PhilA: having metrics for the value of this 11:22:15 Bernadette: I’m not sure if everything is there 11:22:25 PhilA: how do we know that we’ve got enought? 11:22:33 Bernadette: maybe this is a draft 11:22:51 …maybe we need a methodology for our work 11:23:07 …I’m not sure if this would be a problem 11:23:08 q? 11:23:33 for the recor, philT's 3 points: invariance, value, measurement 11:23:34 PhilT: for me that slide represents a data lifecicle 11:23:47 tks antoine 11:24:05 s/recor/record/ 11:24:44 Yaso: About the data usage problem: we have to worry about the provider of the data and the people using the data. 11:24:52 … They are not necessarily the same people. 11:24:58 Here are some graphics of life cycles... https://www.google.com/search?q=lod2+data+lifecycle&client=opera&hs=S0b&channel=suggest&tbm=isch&tbo=u&source=univ&sa=X&ei=RFA5U_blL8boywOouoHoDg&ved=0CGQQsAQ&biw=1366&bih=577 11:25:07 +1 Yaso 11:25:10 … We have to find a place in this lifecycle to differentiate the two personas. 11:25:31 +1 Yaso 11:25:34 … We have already referenced work in the Linked Data working group about lifecycles of data. Michael Hausenblas did it, if I remember correctly. 11:25:39 q+ 11:25:43 ack yaso 11:25:47 Many times consumers are not considered from the producers perspective. 11:25:48 PhilT: we shoul look http://www.slideshare.net/mediasemanticweb/linked-data-life-cycles 11:25:51 http://www.slideshare.net/mediasemanticweb/linked-data-life-cycles 11:25:58 philT: we need to refrrence other lifdcycle definitions. it s a matrr of reputation for the group 11:26:30 Yaso: The linked data lifecycle isn't the same but there are many intersections for us. 11:26:41 s/lifdcycle/lifecycle 11:26:45 -> GLD Best Practices http://www.w3.org/TR/ld-bp/ 11:26:52 ack brian 11:27:20 losing sound? 11:27:26 CarlosIglesias: I would add more about sources 11:27:35 Just one Open Data lifecycle more http://www.slideshare.net/carlosiglesiasmoro/estrategias-open-government-data (in Spanish, but happy to elaborate on this if needed) 11:27:51 Bernadette: this is about the use cases that we have now 11:28:07 -> http://demo.lod2.eu/lod2demo The LOD2 Data Life Cycle 11:28:19 zakim, who is noisy? 11:28:19 I am sorry, PhilA; I don't have the necessary resources to track talkers right now 11:28:22 Yes thank you 11:28:43 q? 11:28:47 Deirdrellee: maybe it’s just a way of thinking about it 11:29:08 Bernadette: this is just a draft, we have to work on it 11:29:13 ack carlos 11:29:13 CarlosIglesias, you wanted to talk about a similar model he has been applying in OD projects 11:29:30 CarlosIglesias: I really like the model, because we’re building on that is similar 11:29:46 There are a lot of 'data use' use-cases as well as data publication use-cases 11:30:06 …the main differences is that we are working on indicators, an actions depending on the indicators 11:30:14 use-cases can cover multiple stages of the data life-cycle 11:30:30 …also, we are talking about licencing 11:30:56 …what are the current licence issues within data usage 11:31:36 …I miss a lot of things in data reuse, because we have to thin on data engagement on 5 stars 11:31:55 … I really like the IBM ?? 11:32:03 http://www.businessofgovernment.org/report/designing-open-projects-lessons-internet-pioneers 11:32:07 ack vagner 11:32:29 s/??/http://www.businessofgovernment.org/report/designing-open-projects-lessons-internet-pioneers 11:33:11 Vagner_br: I can see that interoperability, I can see in this lifecicle here, we should think about other elements like updating data 11:33:44 Bernadette: this are the main actions, and the lifecicle is based on it. We have 2 things: the elements and the process 11:33:45 Previous reference is on the role of openness and user engagement for the success of the Web and it can be applied also to data reuse 11:34:09 …for example: versioning it’s a process. Interoperability can be a principle 11:34:24 ...Machine-readability it’s a principle 11:34:46 q? 11:34:50 …I think there are different things: aspects, processes and ??? 11:35:10 q+ to suggest it may be possible to write a BP or two as we work on the UCR? 11:35:28 …I call these dimensions. There is the aspects elements 11:35:31 q? 11:36:01 Bernadette: I think we can divide in to principles and processes, 11:36:16 …for example: traceability is a principle 11:36:34 …data versioning… I’m not sure if this is a principle 11:36:50 …we have some aspects, or some elements that we have to look at 11:36:56 q? 11:37:04 …we have problems, for example: heterogenity: it will be ther 11:37:12 s/ther/there 11:37:21 q+ on the complexity of so much levels 11:37:57 vagber_br: my question is about data collecting 11:38:30 …should we now consider some other aspects, like the management aspects of how the data is available before we can collect them? 11:38:44 …consider some ecossystem aspects 11:39:02 …because in this lifecycle we are considering that data is available 11:39:15 …the government shoul consider legal aspects, for example 11:39:30 HadleyBeeman: it’s of the web 11:39:38 s/of/off 11:39:57 q+ 11:40:17 ack deirdre 11:40:24 q+ 11:40:32 PhilA: these are issues that you have to consider, but these are legal aspects and W3C will not deal with it in this WG 11:40:57 q- 11:41:00 deirdrelee: we have to go back to the use cases requirements, based on the life cicle 11:41:28 q- 11:41:35 +1 deirdrelee proposal 11:41:35 …do we need more use cases? Maybe we’re not in position to answer it now, but we can decide if we need more use cases if we look at the challenges 11:41:51 ack yaso 11:42:16 yaso: Principle that fits in best practice for data collection are the problems of performance for REST APIs, for example. 11:43:03 … When we collect data, we have to think about how big this dataset will be. Data for four cars is one thing; data for billions of cars, using REST APIs — how will we do that? And how will it affect the performace of applications using this data? 11:43:06 +1 to Yaso 11:43:24 (and +1 to Deirdre's plan too, hence I took myself off the queue) 11:43:25 +1 to yaso 11:43:28 ack philt 11:44:40 PhilT: using use cases is generally a tool used to set up a scope 11:44:41 +1 to Deirdre's plan and to Phil's plan of taking myself off the q for that 11:44:42 +1 to yaso, 11:45:07 PhilA: we have to look for properties 11:45:17 s/PhilA/PhilT 11:45:46 …best practices should be aplied to all this range 11:46:06 scale versus efficiency 11:46:59 OSI Data management and interchange - http://www.iso.org/iso/home/store/catalogue_tc/catalogue_tc_browse.htm?commid=45342 11:46:59 zakim, close queue 11:46:59 ok, PhilA, the speaker queue is closed 11:48:23 +1 for starting with group discussion on challenges 11:48:40 Organization for the Advancement of Structured Information Standards - https://www.oasis-open.org/ 11:49:01 Topic: Dinner venue 11:49:08 -> https://www.jamieoliver.com/italian/covent-garden Jamie Oliver Italian 11:50:21 Other - perhaps useful URL's - http://www.usgs.gov/datamanagement/index.php 11:51:59 Break for lunch — back for 14:00 BST 11:52:03 === LUNCH === 11:52:14 rrsagent, draft minutes 11:52:14 I have made the request to generate http://www.w3.org/2014/03/31-dwbp-minutes.html PhilA 11:52:32 -ericstephan 11:52:49 -Steve 11:52:50 ok 11:52:50 Team_(dwbp)08:20Z has ended 11:52:50 Attendees were +44.207.202.aabb, ericstephan, Hadley, Yaso, PhilA, deirdrelee, BrianMatthews, Ig_Bittencourt, Antoine, MakxDekkers, +33.4.93.00.aacc, gatemezi, HadleyBeeman 11:53:31 Also perhaps - http://www.dama.org/i4a/pages/index.cfm?pageid=3364 12:14:50 JoaoPauloAlmeida has joined #dwbp 12:25:53 : I am trying to get online on the conference bridge and google hangout but can't 12:26:01 are you in session? 12:28:27 ok, I see you are probably breaking for lunch. Please let me know when the google hangout is back on! 12:29:01 gatemezi has joined #dwbp 12:57:35 newton has joined #dwbp 12:58:05 adrianov has joined #dwbp 12:59:02 fkyanai has joined #dwbp 13:00:28 Ig_Bittencourt has joined #DWBP 13:00:30 == Starting Again== 13:00:42 zakim, who is on IRC? 13:00:42 I don't understand your question, PhilA. 13:00:49 zakim, who is here? 13:00:49 apparently Team_(dwbp)08:20Z has ended, PhilA 13:00:51 On IRC I see Ig_Bittencourt, fkyanai, adrianov, newton, gatemezi, JoaoPauloAlmeida, MakxDekkers, antoine, raphael, laufer, markharrison, JohnGoodwin, Zakim, RRSAgent, PhilA, 13:00:51 ... ericstephan, trackbot 13:01:08 zakim, room for 4? 13:01:09 ok, PhilA; conference Team_(dwbp)13:01Z scheduled with code 3927 (DWBP) for 60 minutes until 1401Z 13:01:20 HadleyBeeman has joined #dwbp 13:02:16 Team_(dwbp)13:01Z has now started 13:02:23 +??P7 13:02:28 Zakim, ??P7 is me 13:02:28 +JoaoPauloAlmeida; got it 13:02:54 Hi, I see you are back from lunch :-) 13:03:50 +gatemezi 13:04:17 zakim, code? 13:04:20 the conference code is 3927 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), PhilA 13:04:26 Caroline_ has joined #dwbp 13:04:31 deirdrelee has joined #dwbp 13:04:43 CarlosIglesias has joined #dwbp 13:04:53 We are alone in the call with JoaoPauloAlmeida ? 13:04:55 +ericstephan 13:05:27 PhilA, are you dialing in so we can hear what's going on in the room? 13:05:48 Vagner_Br has joined #dwbp 13:05:49 PhilA is dialling in 13:05:56 ok thanks 13:06:31 I will have to leave the meeting early to attend a Force 11 Implementation telecon at I believe 4pm London time. 13:06:34 +Steve 13:06:40 HadleyBeeman has joined #dwbp 13:06:44 New google hangout for the afternoon: https://www.w3.org/2013/dwbp/wiki/London_2014#Google_Hangout 13:08:01 Zakim, mute me 13:08:01 JoaoPauloAlmeida should now be muted 13:08:07 BernadetteLoscio has joined #dwbp 13:08:36 scribe: Caroline_ 13:08:51 topic: Challenges 13:09:09 zakim, who is here? 13:09:09 On the phone I see JoaoPauloAlmeida (muted), gatemezi, ericstephan, Steve 13:09:09 -> https://docs.google.com/spreadsheet/ccc?key=0AhTZf3B9yQ3odGVvU3pBazFsY3pyUVppNDFSZGtyQkE&usp=sharing&richtext=true#gid=5 Looking at second sheet on the challenges 13:09:11 On IRC I see BernadetteLoscio, HadleyBeeman, Vagner_Br, CarlosIglesias, deirdrelee, Caroline_, Ig_Bittencourt, fkyanai, adrianov, newton, gatemezi, JoaoPauloAlmeida, MakxDekkers, 13:09:11 ... antoine, raphael, laufer, markharrison, JohnGoodwin, Zakim, RRSAgent, PhilA, ericstephan, trackbot 13:09:37 deirdrelee: we don't have to go into details on how to solve all the problems, it is more about the scope 13:09:57 ... regarding the challenges we can go through one by one 13:09:59 zakim, steve has bernadetteloscio, hadleybeeman, vagner_br, carlosiglesias, deirdrelee, Caroline_, Ig_Bittencourt, fkyanai, adrianov, newton, antoine, laufer, markharrison, JohnGoodwin, PhilA 13:10:20 +bernadetteloscio, hadleybeeman, vagner_br, carlosiglesias, deirdrelee, Caroline_, Ig_Bittencourt, fkyanai, adrianov, newton, antoine, laufer, markharrison, JohnGoodwin, PhilA; got 13:10:22 ... it 13:10:22 ... metadata 13:10:37 .... 1st challenge is on metadata 13:10:48 ... do we need to put more details? 13:10:59 zakim, Steve has Rick, JohnG, Mark Harrison, Laufer, Vagner, Caroline, Ig, Bernadette, Newton, Flavio, PhilT, Adriano, Antoine, Carlos, Deirdre, Yaso, PhilA, Hadley, Jeremy Debattista 13:10:59 laufer was already listed in Steve, PhilA 13:11:00 newton was already listed in Steve, PhilA 13:11:00 antoine was already listed in Steve, PhilA 13:11:00 PhilA was already listed in Steve, PhilA 13:11:00 +Rick, JohnG, Mark, Harrison, Vagner, Caroline, Ig, Bernadette, Flavio, PhilT, Adriano, Carlos, Deirdre, Yaso, Hadley, Jeremy, Debattista; got it 13:11:09 Guest: Jeremy Debattista 13:11:23 q+ 13:11:32 zakim, open queue 13:11:32 ok, HadleyBeeman, the speaker queue is open 13:11:43 q+ johngoodwin 13:11:56 -> https://certificates.theodi.org/ ODI Certificates 13:12:20 Steve: When you publish the data some people are deciding what to publish, but none of these is documented 13:12:31 -> http://www.w3.org/TR/prov-o/ The Provenance Ontology 13:12:35 ... Chicago decided to build its on metadata to describe its data 13:12:44 yaso has joined #dwbp 13:12:47 ... NYC also did it 13:12:47 zakim, open queue 13:12:47 ok, PhilA, the speaker queue is open 13:12:49 ack john 13:12:55 q+ 13:13:01 adler1 has joined #DWBP 13:13:26 q+ to pick up INSPIRE use case 13:14:17 I just asked about the metadata work discussed here could/should, for example, fit in with other initiatives like INSPIRE 13:14:20 Laufer: I think we have 2 issues: metadata is not standarized and if it is machine readable 13:14:30 ... we will decide the format of the metadata? 13:14:36 http://inspire-geoportal.ec.europa.eu/ 13:14:46 Hadley: do we want to take all metadata or some kinds of metadata? 13:14:47 ack laufer 13:14:49 ack me 13:14:49 PhilA, you wanted to pick up INSPIRE use case 13:15:23 PhilA: data shoujld be machine readable and also could be human readable 13:15:26 q+ on metadata to add it should be unambiguous defined 13:15:32 RickRobinson has joined #DWBP 13:16:07 s/shojld/should 13:16:09 +q 13:16:10 ... if we are talking about a data tool to describe data catalogues, this group would decide for dcat 13:16:45 ... best practices includes to describe metadata, it includes data vocab 13:16:58 q? 13:17:16 ack carlos 13:17:17 CarlosIglesias, you wanted to comment on metadata to add it should be unambiguous defined 13:17:21 ... you might have general cases and some others with 8%... etc. How do you handle that 13:17:37 q+ 13:17:37 s/8%/80% 13:17:50 q+ 13:17:53 ack adler 13:17:59 q+ to mention something I though of earlier around BP doc 13:18:01 CarlosIglesias: 1. an agreement on standarized metadata, 2. a good description of metadata, 3. a machnie readable format on metadata 13:18:14 Steve: can we define a metadata vocab that is agnostic? 13:18:24 ... can we provide use cases examples? 13:18:37 ... use cases that could use different tools 13:18:39 ack bern 13:18:58 q+ 13:19:02 BenadetteLoscio: asks CarlosIglesias what is the difference between medatada and vocab 13:19:15 ... for example: if we describe information about hospitals 13:19:27 CarlosIglesias: dcat is vocab about metadata 13:19:39 ... you may have lots of different vocabs 13:19:55 ... there is a specific domain which is metadata, and then you have many other domains 13:20:05 ... geographic domains for example 13:20:13 ... metadata is just a particular use of a given vocab 13:20:32 BernadetteLoscio: metadata can be used to describe a data catalog 13:20:40 PhilT has joined #DWBP 13:20:46 ... if you are going to describe a csv file would you consider that a matadata? 13:21:04 +q 13:21:06 CarlosIglesias: the data is what you have inside of the scv file 13:21:14 ... from my perspective they are metadata 13:21:34 BernadetteLoscio: we have different leves of metadata, that is why I think we should have an agreement on that 13:21:44 ... we can use vocabs to describe metadatas 13:21:58 ... to describe specific domains it is not the idea 13:22:18 q+ 13:22:23 ... defining vocabs would be interesting to understanding what kind of metadata 13:22:35 PhilA: we should talk with the CSV WG 13:22:38 q+ to talk about how we choose our vocabularies: grounding in the problems 13:22:58 PhilA +1 13:23:00 Vagner_Br: are we saying that metadata should be standarized and readable machine format? 13:23:18 q+ 13:23:28 ... are we saying that any kind of metadata standard is part of our scope or should we have at least a minimum to consider that? 13:23:30 I think there should be a joint telecon at some point PhilA 13:23:48 to ericstephan phila: we can definitely make that happen 13:24:07 deirdrelee: it is a challenge according to the use cases. Now we are discussing if this should be adopted by the wg 13:24:36 ack vagner 13:24:38 ... maybe the metadata should be generic, but should have an specific domain. That is what we should discuss with the challenges 13:24:50 ack me 13:24:50 PhilA, you wanted to mention something I though of earlier around BP doc 13:24:54 ... what is the requirment? What part of this challenges we whant to address 13:24:56 ack phila 13:24:57 q+ 13:25:20 PhilA: I wonder if it might be helpful to start writing best pracatices. 13:25:28 I guess a metadata in UML is out of our scope.. but yes, if it is in CSV , it could be ok for us... 13:25:44 ... if we know which are the best practices we want to write we might start writing them 13:26:01 ... metadata should be available in different formates. E.g. Json 13:26:20 ... we might find people who have implemented before we get to the end of the process 13:26:27 ... we must see the reality 13:26:28 ack laufer 13:26:40 laufer: I am thinking about the granularity 13:26:53 .... we have collections, catalogues, datasets, resources 13:27:06 ... how can I identify the resources and put semantic on them 13:27:21 nathalia has joined #dwbp 13:27:31 ... how do you describe resources 13:27:36 Hi nathalia 13:27:38 +1 to laufer's point 13:27:42 hello 13:27:51 ... we need a metadata to describe these things 13:28:07 the sound is not good here 13:28:16 +1 to Laufer, but I know Eric is about to talk about this point 13:28:19 ... if csv wants to describe this kind of metadata, it is a kind of transformation from scv file to another file 13:28:40 ... if I have xml file I have another kind of metadata to transform 13:28:43 q+ 13:28:46 ack ericstephan 13:28:46 ... How do we describe things? 13:28:57 ack eric 13:29:08 tks Caroline 13:29:15 I'm at Hangout 13:29:18 q+ 13:29:19 q+ to add from Laufer's comments a new bp: provide always a way to automatically associate data and metadata 13:29:22 ericstephan: I agree that the csv wg will be very helpful with some of the discussions 13:29:44 ... metadata is mentioned into the use cases and became very important 13:29:49 -> http://www.w3.org/blog/news/archives/3758 Outputs from CSVW WG 13:30:08 ... the second point is from my point of view vocab is a data model 13:30:13 ... as a tec agnostic 13:30:21 ... terms, relationships and definitions 13:30:25 +1 13:30:29 I always start vocabs that way 13:30:36 +1 to data models as the central point 13:30:43 HadleyBeeman: does anyone has comments about data models and vocabs? 13:30:58 q? 13:31:31 what we are calling vocabularies are data models with some level of sophistication 13:32:11 this is not all a "vocabulary" could be, but seems to be the prevalent meaning of the term as it is being used 13:32:36 Steve: we have a mandate to create data quality, comparability and vocab 13:32:39 ... in w3c setting 13:32:42 The two vocabs are data quality and data usage, not comparability 13:32:49 ... also to define what we expect 13:33:01 q+ to talk about provenance 13:33:08 i.e. provenance metadata? 13:33:21 ... I think we can do that in an open standard way so anybody can use any tec they want to 13:33:25 Steve: Talking about the vocabs we have to do. Quality and granularity etc. 13:33:42 http://www.w3.org/TR/2013/REC-prov-dm-20130430/ PROV model 13:33:45 PhilA: the providence is very important 13:33:52 +1 13:33:57 ... it is a huge subject and we don't have to define it 13:34:14 ... it is stuff we can point to 13:34:19 Provenance ontology is at http://www.w3.org/TR/prov-o/ 13:34:27 q- 13:34:38 Steve: after publishing it might just be indicated the archive 13:34:46 ack me 13:34:46 HadleyBeeman, you wanted to talk about how we choose our vocabularies: grounding in the problems 13:34:52 ... or having a metadata filled for that 13:34:57 ... that might be enough 13:35:02 ack adler 13:35:22 q+ 13:35:41 jeremy has joined #DWBP 13:35:46 s/providence/provenance/ 13:36:03 Steve: I keep bringing the open tec angle because when I talk with a city they say they are "only 4 guys" in the city and they don't have resources to study RDF, for e.g. 13:36:20 ... they don't have resources to do the perfect job, they just do what they can 13:36:27 q+ to answer Steve's RDF points 13:36:28 ... rdf is a little academic 13:36:40 ... the world we live people just do what they can 13:36:49 q? 13:37:09 ... I think we have a lot value to add and that is why I keep pushing to the group recommend what is useful 13:37:12 ack me 13:37:12 PhilA, you wanted to answer Steve's RDF points 13:37:39 q- 13:37:53 PhilA: LA is a big city. Of course they don't know how to use RDF. But they can specify what they want 13:38:25 philA: Because they are paying for a tool, they can specify how that tool works. 13:38:26 ... we are not going to say things aren't best practices only because some people won't use them 13:38:28 q+ also many companies need guidance on using (unfamiliar) Linked Data technologies - which tools?, which formats?, which vocabularies? how to verify whether they've done it right? 13:38:34 ... they have to provide the metadata 13:38:56 ... we must point that on the best practices 13:39:05 ... it might have different formats 13:39:06 q+ to point out that also many companies need guidance on using (unfamiliar) Linked Data technologies - which tools?, which formats?, which vocabularies? how to verify whether they've done it right? 13:39:31 laufer: any URI can be associated to a colum. 13:39:39 s/colum/column 13:39:43 ... you don't have to do it, but you may 13:39:54 ... they do it in Socrata 13:40:00 ack philt 13:40:01 ack philt 13:40:17 PhilT: we should only not overlap the previous work 13:40:18 ack gatemezi 13:41:13 gatemezi: I wanted to agree on metadata - we have to help the publishers to make their metadata at least in 3 star data 13:41:30 ... I think 5 star is better of course but 3 star is a good start 13:41:38 ... and we can refer to the CSVW 13:41:48 q- 13:41:48 ack carlos 13:41:50 we need to keep in mind that we need to offer a gradual path 13:41:50 q- 13:41:59 for implementers of the practices we recommend 13:42:26 perhaps we can be explicit on "levels" of compliance? (are we aiming at "compliance" at all? 13:42:56 CarlosIglesias: we should use metadata with data to make it machine readable 13:43:16 "machine readable" is too coarse a statement, we should be more specific in our communication 13:43:17 ... it is important not only to provide but also to llok at the demand side 13:43:30 a stream of bytes is "machine readable" 13:43:33 s/llok/lock/ 13:43:44 q+ 13:43:47 ... the good thing about all this is that both solutions can be done 13:43:53 ack deirdre 13:44:06 deirdrelee: lets try to refocus every on and then! 13:44:15 ... we spent 45min talking about one challenge 13:44:36 ... the other challenges on metadata are on metadata standards and how to bring them together 13:44:46 ... how often and regulary the data is publish 13:44:58 ... there are different challenges related with metadata 13:45:34 ... we are missing: are not available on machine readable format 13:45:46 ... we need agnostic models, not only RDF 13:45:59 ... what are the actual requirements on metadata? 13:46:22 Ig_Bittencourt_ has joined #DWBP 13:46:57 s/regulary/regularly/ 13:47:12 PhilA: would you find useful for each of these things to be treated of an issue? 13:47:27 deirdrelee: I think we could talk all together 13:47:35 q? 13:48:02 ... metadata should be machine readable. Would taht be enough for a requirement? 13:48:05 in my opinion that is not enough 13:48:10 q+ 13:48:16 HadleyBeeman: we might have to define machine readable at some point 13:48:23 again, a stream of bytes is machine readable (?) 13:48:26 PROPOSED: Include a requirement that metadata should be machine readable 13:48:37 CarlosIglesias: you can have notes on literature describing it 13:49:16 ... maybe we should be careful to use the official meanings of these terms 13:49:20 RRSAgent, draft minutes 13:49:20 I have made the request to generate http://www.w3.org/2014/03/31-dwbp-minutes.html PhilA 13:49:35 +1 13:49:38 PhilA: could you add both human and machine readable ? 13:49:38 +1 13:49:39 +1 13:49:41 +1 13:49:43 +1 13:49:44 +1 13:49:44 +1 13:49:45 +1 13:49:47 +1 13:49:52 +1 13:49:54 +1 13:49:56 +1 13:49:56 +1 13:49:59 +1 13:50:00 +1 13:50:02 +1 13:50:04 +1 13:50:08 +1 13:50:08 Resolved: Include a requirement that metadata should be machine readable 13:50:25 thanks for reading my comment :-) 13:50:37 HadleyBeeman: I would suggest that human readable is a separate discussion 13:50:54 JoaoPauloAlmeida what about “browser-readable”? hehe 13:51:06 Steve: we don't yet see streaming data as part of open data 13:51:10 ... but it might become 13:51:21 ... as telephone crossing might become also 13:51:25 q? 13:51:32 As far as I am understanding the definition of machine readable format is a separate discussion 13:51:45 ... use case example: we are measuring the trafiic, polution, all kind of things 13:51:51 ... these data can become open data 13:51:55 I agree with Vagner_BR 13:52:08 ... there should be metadata that came from there 13:52:17 but if we say is myst be machine readable, and we don't agree on what machine readable means then what we say seems vacuous 13:52:24 s/myst/must/ 13:52:33 HadleyBeeman: are we asking if anyone else that creates metadata should make it machine readable 13:52:46 -> http://www.w3.org/2005/Incubator/ssn/ssnx/ssn Semantic Sensor Network Ontology, *may* be standardised in near-future WG 13:52:49 PhilT: the best practices should add value in all use cases 13:52:58 ... can you mesaure the impact of best practices 13:53:11 ... in case of all them should be machine readable? 13:53:27 ... there might have use cases that data are not machine readable 13:53:37 machine readable just means not in natural language? have a minimum level of structuring? 13:53:46 ... we could understand that it could be regonized with any open standard 13:54:12 Steve: we often talked about the data we get from NYC are .pdfs 13:54:17 On streaming - XSLT 3 includes transformations for streaming data see http://www.w3.org/TR/xslt-30/ for more 13:54:33 ... we have to build new type of ??? that can understand metadata 13:54:39 PhilA: stop using pdf 13:55:19 PhilA: that's one of our bp message... ;) 13:55:23 PhilT: if you follow this example. Some organization will publish information with pdf. You could use internal standards to read the document with metadata 13:55:34 q? 13:55:39 q+ on PDFs 13:55:47 Steve: I guess the question is: does the metadata follow the document or the repository follows it? 13:56:06 ack markharrison 13:56:06 markharrison, you wanted to point out that also many companies need guidance on using (unfamiliar) Linked Data technologies - which tools?, which formats?, which vocabularies? how 13:56:09 ... to verify whether they've done it right? 13:56:19 HadleyBeeman: or can we say that because the data is on the web it does matter what format is inside or we should consider metadata 13:56:51 q+ 13:56:51 markharrison: wheter to put the metadata inline or rpovide it as a block 13:57:04 ... sometimes doing inline makes it more difficult 13:57:15 q- adler1 13:57:15 +1 mark 13:57:21 ack yaso 13:57:27 q- adler1 13:57:29 yaso: I just want to make a question 13:57:32 ack adler1 13:57:43 ... a requirement that each resource has its metadata to be data on the web 13:57:45 q- adler 13:58:10 ... I understand that is to naif, but can we say: having metada is a requirement? 13:58:30 ... if you publish a pdf should you make medatada about this content? 13:58:45 ? 13:58:47 q? 13:58:47 ... can this group recommend to use metadata in this case? 13:58:50 ack me 13:58:50 PhilA, you wanted to comment on PDFs 13:58:50 laufer: yes 13:59:04 PhilA: of course .pdf is going to be around for a long time 13:59:17 ... we had jimmy from adobe during the workshop 13:59:26 ... he said what you can do with a pdf 13:59:31 ... of course no one does it 13:59:40 ... as long as anyone can use it should be there 13:59:59 ... perhaps what we can say is taht if your pdf include tables, please use metadata 14:00:08 q+ to say that metadata needs to provide context (geographic scope, time range, type of data, domain-specific vocabularies used) so that similar / comparable datasets can be identified 14:00:23 ... give people an explation why pdf in its own it is only usable for humans 14:00:45 Steve: maybe a recommendation is when you scrape pdf it should have metadata 14:01:13 q? 14:01:17 PhilA: somebody publishes a pdf and I spend the next 3 weeks reading it and I create a table based on that 14:01:21 tracking... 14:01:27 ... then I have to refer beack to the pdf 14:01:41 ... and say that refers to the metadata I refered 14:01:54 scribenick: carlosiglesias 14:02:37 Zakim, who is speaking? 14:02:48 gatemezi, listening for 10 seconds I heard sound from the following: gatemezi (17%), ericstephan (100%), Steve (5%) 14:02:53 ericstephan: I'll take that back. We have a careful delineation in the CSV on the Web working group — if you scrape data from a PDF file, 14:03:14 … if you put it into a tabular format — that is the same as taking it from a database. 14:03:39 … I'll document this discussion. It fits with our other use cases where we're pulling data from an external source. 14:03:43 q? 14:03:51 ack deird 14:04:25 deirdrelee: any BPs editors yet? 14:04:36 ... we are discussing a lot about that 14:04:47 ... would be useful to have somebody nominated 14:05:15 phila: any volunteers? 14:05:36 I'd like to help out. Sounds attractive :-) 14:05:59 I suggest Deirdre ... 14:06:24 thanks Ghislain!! 14:07:36 Notes page for best practice https://www.w3.org/2013/dwbp/wiki/Best_practices_notes 14:07:37 steve: we should include not only best practices but also examples of why they are useful to give background 14:08:23 Thank you so much for writing down our relevant comments on that wiki page, ericstephan. You're amazing! 14:08:27 s/steve/adler1 14:08:41 PROPOSED: There should be metadata 14:08:53 +1 14:08:56 +1 14:08:56 +1 14:08:59 +1 14:08:59 +1 14:08:59 +1 14:09:00 +1 14:09:00 +1 14:09:01 +1 14:09:02 +1 14:09:03 +1 14:09:06 +1 14:09:09 +1 14:09:09 +1 14:09:12 +1 14:09:15 +1 14:09:15 +1 14:09:17 +1 14:09:27 +1 14:09:30 deirdrelee: machine readable? 14:09:45 everyone: already agreed 14:09:46 Resolved: There should be metadata 14:10:04 deirdrelee: should then include human readable requirement? 14:10:06 q+ 14:10:09 PROPOSED: That metadata should be human readable 14:10:16 +1 14:10:17 +1 14:10:19 +1 14:10:23 +1 14:10:24 -1 14:10:25 -1 14:10:30 -1 14:10:31 -2 14:10:43 +1 14:10:46 use pdf to describe metadata pdf to describe metadata pdf…. that’s a (infinite) loop :-) 14:11:04 zakim, who is speaking? 14:11:12 RESOLVED: There should be metadata 14:11:14 CarlosIglesias, listening for 10 seconds I could not identify any sounds 14:11:15 can we say something about minimal metadata: who, what, when, where? 14:11:25 who=the responsible org 14:11:29 q+ 14:11:35 +1 to MakxDekkers 14:11:42 what=at least a short description or name 14:11:43 hadleybeeman: lot of metadata is encoded 14:11:50 ... not human readable 14:11:53 Is it a best practice or common practice? 14:11:54 when=date of publication 14:11:56 ... but still useful 14:12:01 where=downlaod link 14:12:07 Sorry no voice connection 14:12:10 ... not to mandate to be human readable 14:12:32 ack mark 14:12:32 markharrison, you wanted to say that metadata needs to provide context (geographic scope, time range, type of data, domain-specific vocabularies used) so that similar / comparable 14:12:34 acck me 14:12:35 ... datasets can be identified 14:12:35 ack me 14:12:40 +q 14:13:12 the key point is that metadata should be defined in a format that is well described 14:13:17 adler1: can encourage human readability 14:13:18 there must be rules for interpretation 14:13:21 ... not require 14:13:27 Hadley just exemplified that 14:13:43 She used integers with clear interpretation rules (1 for school, 2 for ...) 14:13:44 ack antoine 14:13:53 q+ to say must be human readable at some point 14:14:16 antoine: if it is not human readable it won't be reused 14:14:24 it doesn't have to be human readable it has to be MEANINGFUL (sorry to shout I am far away :-)) 14:14:36 if it is machine-readable, the machine can make it human-readable 14:14:44 Is html document is human readable ? 14:14:55 good point Makx 14:15:13 discussion on what human readable means 14:15:20 q? 14:15:40 are we going to discuss human readable? we haven't finalized the discussion about machine readable? :-0 14:15:57 ... (the definition) 14:16:08 carlos: I think what we mean is that metadata should be comprehensible. 14:16:17 +1 to carlos that's UNDERSTANDLE 14:16:33 what I meant with MEANINGFUL 14:16:33 … At some point in the chain, that metadata should be expressed such that humans can read it. 14:17:06 carlosiglesias: human-readable vs. comprehensive metadata 14:17:09 q+ 14:17:23 adler1: these are different things 14:17:30 ack BernadetteLoscio 14:17:53 BernadetteLoscio: it's more about metadata documentation and not human readability 14:17:55 +1 14:17:58 ... metadata description 14:17:58 it's not an issue of cognitive limitations, it's an issue of having minimum descriptions that allows one to interpret it 14:18:00 +1 to Bernadette 14:18:04 Encourage development of tools that make machine-readable metadata understandable to humans (even non-technical humans that don't read XML) 14:18:09 to map the data to situations in reality, to interpret it 14:18:11 laufer: human understandable 14:18:18 +1 to Bernadette 14:18:25 the more requirements you put on metadata, the less you are going to get 14:18:37 s/UNDERSTANDLE/UNDERSTANDABLE/ 14:18:41 BernadetteLoscio: it's about metadata documentation 14:18:43 +1 to makxdekkers 14:18:54 thanks, Vagner_Br 14:18:59 q+ to talk about unreadable human readable textz 14:19:08 BernadetteLoscio: ... with description of metadata 14:19:10 q- 14:19:10 q+ 14:19:24 ack deirdre 14:19:33 I think it is just like add an rdf:about to that metadata 14:19:36 Note that not all of the requirements on metadata need to fall on the data / metadata publishers - third-party tool developers can help to make metadata more understandable. 14:19:38 Zakim, unmute me 14:19:38 JoaoPauloAlmeida should no longer be muted 14:19:53 q+ to make proposal that machine readable metadata should include or refer to human readable documentation 14:20:03 deirdrelee: human readable? well documented? easy to understand? comprenhesible? 14:20:04 Easy to understand or well defined? 14:20:37 adler1: nobody will understand the human-readable thing 14:20:39 q- 14:20:55 PROPOSAL: Metadata should be well-documented and easy to understand 14:20:57 q- 14:20:58 +1 14:21:01 PROPOSED: Metadata should be well-documented and easy to understand 14:21:02 +1 14:21:18 +1 14:21:21 we could mention: in such a way that it can be interpreted 14:21:25 +1 14:21:27 s/comprenhesible/comprehensible/ 14:21:30 q? 14:21:30 0 14:21:32 +1 14:21:34 philt: metadata should also be relevant 14:21:35 q+ to make proposal that machine readable metadata should include or refer to (*OR* be capable of being automatically transformed into) human readable documentation 14:21:39 -0 14:21:41 +1 14:21:44 +1 14:21:53 -1 14:22:01 -1 to mark 14:22:13 makxdekkers, why? 14:22:23 philt: ... documentation should be relevant to the data it describes 14:22:37 vagner: machine readable and well documented 14:22:44 general point: limit the reqs on metadata to the minimum 14:22:46 isn't that obvious (relevant?) 14:23:04 q+ 14:23:04 if someone publishes data that is not relevant, what are they doing? 14:23:23 I am sympathetic JoaoPauloAlmeida 14:23:29 overall metadiscussion about metadata discussion 14:23:29 it is in the interest of the publisher to provide information that helps people understand what it is! 14:23:53 https://www.lib.umn.edu/datamanagement/metadata 14:24:17 +1 to JoaoPauloAlmeida 14:24:26 could you hear me? 14:24:27 q+ 14:24:33 (batteries failing on laptop again) 14:24:50 +1 14:24:50 joaopauloalmeida: no, we couldn't. Sorry! 14:24:50 +1 14:24:57 +1 14:25:21 hadleybeeman: @mark and @joao please follow-up by irc 14:26:00 phila: like the purpouse but don't like the wording 14:26:20 phila: thinking on dublin core 14:26:33 easy to understand is not good; we should not use terms that suggest any level of cognitive effectiveness 14:26:45 scientific data is very hard to understand 14:26:56 +1 to PhilA 14:26:59 phila: it is something included in the metadata that makes it easy to understand 14:27:05 +1 to PhilA 14:27:12 PhilA isn't that obvious? 14:27:34 If you understand the vocabulary you have a better chance of understanding the dublin core records 14:27:53 the key issue is that there should be sufficient documentation such that the intended audience can extract the meaning 14:28:15 E.g a Chines publisher will provide a description in Chinese if that is the audience for it 14:28:15 ... several potential audiences 14:28:20 q+ 14:28:28 ... dna metadata may be not so easy to understand 14:28:35 I disagree that there is no intended audience. 14:28:45 I'm with you, joaopaulo 14:28:51 q- 14:28:55 adler1: if we want metadata to be used and the history of the data be understood 14:28:57 You could have a very wide intended audience ("the public") 14:29:02 q+ to talk about intended users 14:29:04 ... then metadata should be easy to understand 14:29:05 I still have trouble reading the metadata about the ingredients on my cereal box 14:29:34 ... same data can be reused by different audiences 14:29:37 ericstephan: I have a food allergy, so I've put many years into becoming an expert on that :) 14:29:38 cognitive effectiveness or "ease to understand" must not be unqualified without referring to the audience 14:29:48 ack mark 14:29:48 markharrison, you wanted to make proposal that machine readable metadata should include or refer to (*OR* be capable of being automatically transformed into) human readable 14:29:52 ... documentation 14:30:04 :-) Getting better over time Hadley :-) 14:30:21 q+ 14:31:00 ack antoine 14:31:09 adler1: make it possible to everyone if that's useful for them 14:31:20 +1 to JoaoPauloAlmeida metadata should be easy to understand to the "intendend audience" 14:31:22 ... specially important for governments 14:31:44 ack yaso 14:31:51 http://irsa.ipac.caltech.edu/applications/DDGEN/Doc/ipac_tbl.html 14:31:57 philt: include documentation with metadata 14:32:05 ... to avoid broken pointers 14:32:07 yaso: that link ^ is well-documented metadata 14:32:08 +1 to PhilT talking about persistent data and equally persistent documentation (I paraphrase) 14:32:21 ack philt 14:32:27 q+ 14:32:39 another useful document potentially http://www.agi.org.uk/storage/standards/uk-gemini/MetadataGuidelines1.pdf 14:32:40 yaso: we have standards for documentation and we can make use of them 14:32:50 ack HadleyBeeman 14:32:50 HadleyBeeman, you wanted to talk about intended users 14:33:19 +1 to Hadley 14:33:20 q+ to ask about ourrole for defining metadata 14:33:21 HadleyBeeman: I struggle to think in terms other than with a user in mind. You need a target audience in mind (developer/ public etc) 14:33:25 ack deirdre 14:33:29 hadleybeeman: it is important to know who you will be speaking to while writing documentation 14:33:34 maybe also useful https://joinup.ec.europa.eu/asset/dcat_application_profile/description 14:33:45 +1 to the 1st proposal 14:33:56 Option 1: Metadata should be well-documented and useful for the intended audience 14:33:56 which proposal? 14:33:56 can you put these in the IRC? 14:33:59 thanks 14:34:06 I like option 1 14:34:08 Option2: Metadata should be capable of being automatically transformed into human readable documentation 14:34:20 +1 to the 1st option 14:34:31 option 1: define welll-cdocumented 14:34:34 I feel like option 2 is more "it would be nice if". I suspect we'll have fewer use cases for it though. 14:34:36 s/proposal/option 14:34:38 +1 for option 1 14:34:44 +1 for option 1 14:34:48 option 2: not necessary 14:34:48 Option 3 - Metadata should include or refer to documentation useful for the intended audience 14:34:49 +1 for option 1 14:34:52 +1 for option 1 14:34:58 +1 option 1 14:34:58 +1 for option 1, +1 (nice to have) for option 2 14:35:04 I prefer option 1 14:35:09 antoine: if it is machine readable it will be easy to have human readable documentation 14:35:11 +1 for option 1 14:35:12 metadata IS a form of (structured) documentation 14:35:14 +1 for Option 2 14:35:18 +1 option 1 14:35:28 +1 option 1 14:35:29 ... drop option 2, not necessary if we have machine-readability 14:35:31 can we generalize this to data (which would include metadata)? 14:36:38 any data (including metadata) should be structured in such a way that it is possible for the intended audience to extract its meaning; one way of doing this is to supply documentation 14:36:40 +1 option3, it matches well philT's point 14:37:00 what is option 3? 14:37:01 philt: every description should include the provenance 14:37:19 phila: that will be coming 14:37:46 Provenance should be part of the metadata.. 14:38:05 ... the dataset should have metadata 14:38:06 +1 for provenance. it is the WHO I suggested earlier 14:38:13 PhilA, that's why I think we should generalize 14:38:16 Provenance is a type of metadata 14:38:28 data or metadata must be meaningful to the intended audiences 14:38:43 ... and on other hand data should be document 14:38:54 And provenance used to cover most of 75% of metadata .... 14:39:00 Why don't we generalize? we don't need to go infinitely meta 14:39:09 deidrelee: its more about metadata that could have different interpretations 14:39:32 ... to avoid ambiguity need good description, label is enough 14:39:37 Labels helps the intended audience to extract the meaning of data 14:40:30 vagner: metadata is also data 14:40:36 thanks for reading the comment (I am sorry I don't know your name) 14:40:50 ... the description of metadata should also follow data best practices 14:42:17 phila: when talking about metadata we don't restrict ourself about the vocabularies in scope of the wg 14:42:23 q? 14:42:26 ... but also any other 14:43:21 thanks Vagner_Br, I didn't realize it was you as the image in the hang out is fuzzy 14:43:43 zakim, close queue 14:43:43 ok, PhilA, the speaker queue is closed 14:44:46 hadleybeeman: can jump on the following challenges and come back to metadata later 14:45:32 q? 14:45:53 can you record what deirdre just said? 14:45:59 option 4: Metadata vocabulary, or values if vocabulary is not standardised, should be well-documented 14:46:02 ack antoine 14:46:02 antoine, you wanted to ask about ourrole for defining metadata 14:46:04 q- antoine 14:46:11 option 4 ++++ 14:46:14 +1 14:46:20 PROPOSED: Metadata vocabulary, or values if vocabulary is not standardised, should be well-documented 14:46:23 +1 14:46:23 +1 14:46:25 +1 14:46:25 +1 14:46:26 +1 14:46:29 +1 14:46:29 +1 14:46:30 +1 14:46:30 +1 14:46:31 +1 to coffee 14:46:32 +1 14:46:33 +1 14:46:35 +1 14:46:36 +1 14:46:36 +1 14:46:38 +1 14:46:39 +1 again 14:46:46 +1 happy 14:46:46 +1 14:46:49 +1 14:46:56 RESOLVED: Metadata vocabulary, or values if vocabulary is not standardised, should be well-documented 14:47:03 I hope somewhere we can produce a more general statement: Data must be produced using conventions that enable the intended audience to extract its meaning; usually, this is achieve through documentation 14:47:09 10 min brake 14:47:18 rrsagent, draft minutes 14:47:20 I have made the request to generate http://www.w3.org/2014/03/31-dwbp-minutes.html PhilA 14:47:25 == Break == 14:52:15 raphael has joined #dwbp 14:57:44 newton has joined #dwbp 15:00:15 nathalia has joined #dwbp 15:04:26 Deirdrelee I'm updating the best practices as follows, does this look okay https://www.w3.org/2013/dwbp/wiki/Best_practices_notes#guidance_on_the_provision_of_metadata 15:08:50 zakim, phila is really antoine 15:08:50 sorry, PhilA, I do not recognize a party named 'phila' 15:09:12 scribe: Phila 15:09:23 HadleyBeeman has joined #dwbp 15:10:30 Vagner_Br has joined #dwbp 15:11:21 ==restarting== 15:11:38 newton has joined #dwbp 15:11:45 zakim, who is here? 15:11:45 On the phone I see JoaoPauloAlmeida, gatemezi, ericstephan, Steve 15:11:48 Steve has jeremy 15:11:48 On IRC I see newton, Vagner_Br, HadleyBeeman, nathalia, raphael, Ig_Bittencourt_, PhilT, adler1, yaso, BernadetteLoscio, CarlosIglesias, deirdrelee, Caroline_, fkyanai, adrianov, 15:11:48 ... gatemezi, JoaoPauloAlmeida, MakxDekkers, antoine, laufer, markharrison, Zakim, RRSAgent, PhilA, ericstephan, trackbot 15:12:02 let's go! 15:12:36 deirdrelee: metadata should be strandardized 15:12:51 lol 15:12:53 option 15:12:55 HadleyBeeman: W3C has a definition for ' standardized'? 15:12:56 Do not agree! 15:12:59 jeremy has joined #dwbp 15:13:37 Maybe the format for representing the metadata should be standardized .. 15:13:51 PhilA: yes. using vocabularies with change management with certain level of persistence 15:14:07 HadleyBeeman: proposes UK govt def of standards [it's long] 15:14:31 foaf is an example 15:14:37 of useful vocabulary that is not "standardized" 15:14:53 Ig_Bittencourt has joined #DWBP 15:14:55 HadleyBeeman: it has some way to show people are using it 15:14:57 Option: Metadata should be standardised or in demonstrably common use 15:15:23 q+ 15:15:35 zakim, open queue 15:15:35 ok, antoine, the speaker queue is open 15:15:41 q+ 15:16:10 ack ber 15:16:33 PhilA + BernadetteLoscio: we've covered it in previous resolution, no? 15:16:52 I prefer the term community vocabulary 15:17:01 PhilA: there are vocabularies that are used a lot, but no standards. FOAF, schema.org 15:17:26 CarlosIglesias: we should consider consensus 15:17:41 phone reception really bad on my end, anyone else having problems hearing? 15:17:47 ... community aspects 15:17:50 also bad on my end 15:18:17 Another option? Option: Metadata should be (widely) adopted by a given community or experts and should demonstrate common use 15:18:33 +1 gatemezi 15:18:58 what about: Metadata VOCABULARY should be (widely) adopted by a given community or experts and should demonstrate common use 15:19:12 CarlosIglesias: developed with open approach 15:19:23 I don't want to mix metada and vocab.. 15:19:32 s/metada/metadata 15:19:42 adler1: de facto, market standards 15:19:56 q+ 15:19:56 how about: Data must be produced using conventions that are widely disseminated and agreed upon by the intended audience 15:20:08 Yes that makes more sense 15:20:24 deirdrelee: suggests to jump to vocabularies and come back to metadata later 15:20:41 Ig_Bittencourt_ has joined #DWBP 15:21:07 JoaoPauloAlmeida: your proposal is more generic.. and yes, makes sense 15:21:09 markharrison: LOD de-referencing for vocabularies allows metadata at granular level 15:21:16 s/LOD/LD 15:21:29 deirdrelee: challenges for vocs 15:21:44 ... 1 common vocs are not used 15:22:21 ... 2 added value comes from combining comparable datasets 15:23:24 CarlosIglesias: best practice could be to share own vocs with the rest of data managers 15:23:28 Dataset versioning can be moved to the "archiving/preservation" challenge 15:23:57 laufer: if a common voc is not used, it's not common 15:23:58 q+ to say that definitions in common vocabularies need to be unambiguous in order to be useful - specific example of nutritional info in schema.org - does not even specify the reference unit (e.g. per 100g / per serving / per pack / per ton? - Who knows?!) 15:24:48 carlos: exemple of reference vocs required by law in specific countries 15:24:59 ... these should be open with others 15:25:16 is ISO standards shared in an open way? 15:25:20 you have to pay to access them! 15:25:30 q+ 15:25:35 deirdrelee: so proposal is to share reference vocs in an open way 15:26:04 mark: definition of reference vocs need to be unambiguous to be useful 15:26:11 but what about licensing issues in vocabs? 15:26:21 Vagner_Br_ has joined #dwbp 15:26:23 @gatemezi: what about them? 15:26:32 ... pointing out deficiences in definition 15:26:41 (licenses will come later in the discussion) 15:26:54 Open and free are two different things aren't they? 15:27:08 markharrison makes an important point about the coventions used to produce data 15:27:16 nathalia_ has joined #dwbp 15:27:17 s/coventions/conventions 15:27:18 ericstephan +1 15:27:27 PhilA + markharrison: tradeoff between broad and specific 15:28:00 HadleyBeeman: some vocabs come for e.g. in apache license..others with open license.. what happen when you reuse terms with such different vocabs? 15:28:03 ... broade can be uselessly generic 15:28:18 Again, I am sorry to nag you guys with this but: "Data must be produced using conventions that enable the intended audience to extract its meaning" addresses precision/lack of ambiguity 15:28:24 markharrison: developing vocs should be part of the web, with feedback mechanims 15:28:41 ack me 15:28:44 ack mark 15:28:44 markharrison, you wanted to say that definitions in common vocabularies need to be unambiguous in order to be useful - specific example of nutritional info in schema.org - does not 15:28:47 ... even specify the reference unit (e.g. per 100g / per serving / per pack / per ton? - Who knows?!) 15:31:05 zakim, Andy Mabbett is a guest 15:31:05 I don't understand 'Andy Mabbett is a guest', HadleyBeeman 15:31:51 [group discussing the wording of proposal] 15:31:59 option1: If possible, reuse existing reference vocabularies. If not available or suitable, try to (a) extend existing vocabularies, (b) suggest to industry consortium to create a vocabulary, or (c) create your own 15:32:12 Guest:Andy Mabbett 15:32:30 q+ 15:32:36 present+ Andy Mabbett 15:32:52 deirdrelee: happy with ' industry consortia' ? 15:33:11 markharrison: we need a mechanism for identifying relevant vocs 15:33:17 (b) could be: create new vocabulary in a cooperative setting (such as industry consortia, standards body) 15:33:21 ... e.g. Linked Open vocabularies 15:33:44 ... but have we got soem process for defining a new voc? 15:33:58 s/soem/some 15:34:19 PhilA: there is the WebSchemas group 15:34:38 q+ 15:34:40 q? 15:34:44 q+ to ask what happen if you have a standard in UML standardized by ISO 191xx. and want to use it? Should you create it by your own? or wait for ISO 191XXX? 15:34:45 .... but this is turning into a chapter, not a single requirement 15:34:58 ack gate 15:34:58 gatemezi, you wanted to ask what happen if you have a standard in UML standardized by ISO 191xx. and want to use it? Should you create it by your own? or wait for ISO 191XXX? 15:35:14 PhiA is right, this discussion is too detailed 15:35:31 s/PhiA/PhilA/ 15:35:33 gatemezi: when a standard is ISO, it is in PDF 15:35:44 [???] 15:36:13 HadleyBeeman: deirdrelee, BernadetteLoscio, what do you need from us at that point? 15:36:22 ... we're entering into details 15:36:28 ack bern 15:36:43 option2: Existing reference vocabularies should be reused where possible 15:37:00 +1 to JoaoPauloAlmeida (b) - create new vocabulary in cooperative setting (where a vocabulary 'gap' exists) 15:37:19 BernadetteLoscio: it relates to using standardized, general vocs 15:37:26 PhilA: much is done already 15:37:37 ... for the metadata 15:38:21 deirdrelee: we didn't have a specific requirement for standardized 15:38:38 BernadetteLoscio: what is the difference between standardized and ref vocs? 15:38:51 HadleyBeeman: standardized is a subset of reference 15:39:38 laufer: standard implies process 15:39:59 convention might be better 15:40:06 PhilA mentioned public-vocabs@w3.org as a place to ask - and possibly by pointed to an existing relevant vocabulary (by users on that mailing list). Also mentioned Linked Open Vocabularies http://lov.okfn.org/dataset/lov/ 15:40:19 +1 to option 2 15:40:20 PROPOSED: Existing reference vocabularies should be reused where possible 15:40:22 +1 15:40:24 +1 15:40:24 +1 15:40:26 +! 15:40:26 +1 15:40:27 +1 15:40:28 +1 15:40:29 +1 15:40:31 +1 15:40:32 + 15:40:32 +1 15:40:33 +1 15:40:34 +1 15:40:36 +1 15:40:37 +1 15:40:37 +1 15:40:40 +1 15:40:52 Zakim requires machine readable votes 15:40:56 RESOLVED: Existing reference vocabularies should be reused where possible 15:41:28 option 3: If refernce vocabularies not available or suitable, try to (a) extend existing vocabularies, (b) suggest to industry consortium to create a vocabulary, or (c) create your own 15:41:47 q+ 15:41:58 let's leave the detail for later? 15:42:05 +1 15:42:17 ..to JoaoPauloAlmeida proposal 15:42:18 q+ to say that 3 is just part of the description of 2 15:42:18 HadleyBeeman: I have an issue with industry. academic consortia could be useful in some cases 15:42:25 ack me 15:42:31 ack carl 15:42:31 CarlosIglesias, you wanted to say that 3 is just part of the description of 2 15:42:55 carlos: option 3 reads like a description of option 2 rather than a best practice of its own 15:42:56 -JoaoPauloAlmeida 15:43:12 deirdrelee: Please modify (b) to: create a vocabulary in a cooperative setting 15:43:17 add to bp notes: If refernce vocabularies not available or suitable, try to (a) extend existing vocabularies, (b) suggest to cooperative setting to create a vocabulary, or (c) create your own 15:43:36 option4: Reference vocabularies should be shared in an open way 15:43:45 deirdrelee: reference vocabularies should be shared in an open way 15:44:00 I am trying to get back but Zakim says "this code is not valid" 15:44:09 HadleyBeeman: if we're not building them, it's out of scope 15:44:19 zakim, room for 4? 15:44:20 ok, antoine; conference Team_(dwbp)15:44Z scheduled with code 3927 (DWBP) for 60 minutes until 1644Z 15:44:25 or maybe “make it available” instead of “shared” 15:44:56 try that joaopaulo 15:45:11 HadleyBeeman: ' you' is who? 15:45:20 antoine, Zakim still does not let me in 15:45:38 q+ 15:45:46 laufer: can a vocabulary be copyrighted? 15:45:49 CarlosIglesias: yes 15:46:07 ... you need to pay to access 15:46:41 PhilA: W3C publishes royalty-free 15:47:16 ???: think of creative commons licenses 15:47:19 zakim, code? 15:47:19 the conference code is 3927 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), antoine 15:47:24 ... possibility of derivates, etc 15:47:29 s/???/AndyMabbett 15:47:36 I am using the right code but "this code is not valid" 15:47:42 CC-BY-SA licence mentioned 15:48:29 HadleyBeeman: should we split? 15:48:46 yaso: if we don't split it will be hard to reach objectives 15:49:15 BernadetteLoscio: we need to continue challenges anyway 15:49:25 yaso: do we have enough use cases? 15:49:25 hang out is gone 15:49:37 deirdrelee: we have enough towork with now, we can add later if needed 15:49:45 Sorry, Joaopaulo — we have run out of battery 15:49:56 PhilA is fixing it now 15:49:59 deirdrelee: are you there for the hangout? 15:50:02 ok, I wonder why I can't back on Zakim 15:50:13 We may not know if we have enough use cases until we come to agreement on challenges....just a thought 15:50:43 Sorry gatemezi, I'll plug you back in in a minute 15:50:45 HadleyBeeman, deirdrelee, BernadetteLoscio: point on reference vocs need more discussion 15:51:32 zakim, room for 4? 15:51:34 sorry, PhilA; could not schedule an adhoc conference; passcode overlap; if you do not have a fixed code you may try again 15:51:51 opendefinition.org 15:52:17 PROPOSED: Reference vocabularies should be shared in an Open way 15:52:21 +1 15:52:27 +1 15:52:30 +1 15:52:30 +1 15:52:32 +1 15:52:33 Will that exclude ISO? 15:52:34 +1 15:52:34 +1 15:52:35 +1 15:52:35 +1 15:52:40 +1 15:52:42 +1 15:52:43 +1 15:52:45 +1 15:52:47 +1 15:52:56 HadleyBeeman: we'll have to sort out what the definition of ' open' is 15:53:13 The climate community and OGC shares based on ISO in an open way today 15:53:18 +1 15:53:24 royalty-free for use, freely available? 15:53:29 +1 15:53:39 PhilA: it would be difficult to exclude ISO 15:54:05 Agreed PhilA 15:54:07 ACCEPTED: Reference vocabularies should be shared in an Open way 15:54:08 +1 15:54:20 Note, this needs further exploration of definition of Open 15:55:14 PhilA: it would be difficult to put in a document ' don't use ISO standards' 15:55:31 ok, I understand 15:56:01 markharrison: we need to define better the attributes we're expecting: whether the voc is royalty-free, etc... 15:56:18 But we can say things that can help them "opening their UML diagrams" 15:56:38 PhilA: as long as it is freely available, it should be ok 15:56:49 HadleyBeeman: session to be continued tomorro 15:56:55 s/tomorro/tomorrow 15:57:07 Unfortunately I have to run...see you all tomorrow. 15:57:21 See you ericstephan 15:57:23 -ericstephan 15:57:37 good night/morning ericstephan! 15:57:40 scribe: adrianov 15:57:48 Now to start my work day....ahhhh 15:58:07 HadleyBeeman, so tomorrow at 9am there will be a joint discussion session to define requirements? 15:58:58 thanks, PhilA, it will be 5am on my side, I will do my best 15:59:10 ?me if not I'll drop zakim 16:00:57 -Steve 16:01:57 bye 16:02:05 see you tomorrow 16:03:09 -gatemezi 16:03:10 Team_(dwbp)13:01Z has ended 16:03:10 Attendees were JoaoPauloAlmeida, gatemezi, ericstephan, bernadetteloscio, hadleybeeman, vagner_br, carlosiglesias, deirdrelee, Caroline_, Ig_Bittencourt, fkyanai, adrianov, newton, 16:03:10 ... antoine, laufer, markharrison, JohnGoodwin, PhilA, Rick, JohnG, Mark, Harrison, Vagner, Caroline, Ig, Bernadette, Flavio, PhilT, Adriano, Carlos, Deirdre, Yaso, Hadley, Jeremy, 16:03:11 ... Debattista, adler1 16:04:40 yaso has joined #dwbp 16:05:42 AM (Andy Mabbett) starts his talk on OpenStreetMap 16:06:33 rrsagent, draft minutes 16:06:33 I have made the request to generate http://www.w3.org/2014/03/31-dwbp-minutes.html PhilA 16:08:31 AM argued the group about how many of us know OSM (open street map) 16:08:50 AM: is a database of Points of Interest 16:09:56 AM, points of interest may correspond to different entity types 16:10:29 AM: points of interest may correspondo to different entity types 16:10:38 AM: OSM is more detailed than Google maps, and more up to date 16:11:37 AM: stating the differences between OSM and GoogleMaps 16:13:13 AM: interesting features of OSM, such as gritting maps 16:14:42 AM: showing different entities in london area, such as pubs, rivers, streets 16:15:06 s/london/Birmingham 16:15:40 tks HadleyBeeman 16:15:45 no problem :) 16:16:56 raphael has joined #dwbp 16:17:18 AM: Maperative is used to render the maps 16:17:39 AM: another possibility is Leaflet 16:18:19 AM: another possible tool is Mapbox 16:18:57 AM: Geofabrik is used to compare different maps 16:21:57 AM: OSM may provide information about specific points of interest (i.e., using wikipedia data) 16:22:24 Interesting that OSM wants to make its pages machine readable. RDFa to the rescue perhaps 16:23:21 And the CSVW stuff could be interesting for OSM too 16:25:03 AM: discussion on the importance of how information is provided to the user 16:26:06 Team_(dwbp)15:44Z has now started 16:26:13 +MakxDekkers 16:26:27 -MakxDekkers 16:26:28 Team_(dwbp)15:44Z has ended 16:26:28 Attendees were MakxDekkers 16:26:39 AM: OSM does not store the entire content, but is able to rebuild the corresponding URL 16:27:21 newton has joined #dwbp 16:27:26 PhilA: suggests different approaches 16:28:30 Team_(dwbp)15:44Z has now started 16:28:37 +MakxDekkers 16:29:26 -MakxDekkers 16:29:27 Team_(dwbp)15:44Z has ended 16:29:27 Attendees were MakxDekkers 16:29:40 AM: some references may be still undefined, either because they are new or because it does not attrack the interest of the community 16:30:45 AM: possibility to add values in order to solve undefined reference cases 16:32:44 Ig_Bittencourt has joined #DWBP 16:33:02 AM: OSM data is built in a way that facilitates reuse 16:33:58 Note to self - need to tell OSM about JSON-LD, i.e. easily add namespaces to terms 16:34:54 AM: examples on how data can be linked with other sources, such as wikipedia 16:36:00 AM: how to link an information in your database to something in OSM? 16:38:49 AM: discussing data consistency problems in OSM 16:41:57 AM: discussing problems in OSM due to fuzzy matches 16:42:59 AM: tags may be URIs or parts that compose URIs 16:43:42 AM: Andy is finishing his presentation 16:44:05 q? 16:44:11 q+ 16:45:58 ack laufer 16:46:03 PhilA: how hard it is to say the confidence associated with a specific point? 16:46:30 laufer: how data is accessed? 16:46:46 AM: there are APIs to use 16:47:03 q+ to ask if there are plans for a SPARQL endpoint or GeoSPARQL endpoint? 16:47:15 laufer: who defines the tags? community? 16:47:42 q+ to ask about dev doc 16:47:43 AM: everybody can define a tag. Andy clarifies this process 16:48:07 q+ 16:49:04 AM: the existing vocabulary has emmerged organically 16:49:16 q+ to talk about JSON-LD 16:49:24 q 16:49:26 q? 16:49:31 q- 16:50:44 AM: discussing the difficulties in acquiring a perfect vocabulary. Alternatively, a community-based vocabulary may be a good solution 16:50:44 ack mar 16:50:44 markharrison, you wanted to ask if there are plans for a SPARQL endpoint or GeoSPARQL endpoint? 16:50:52 ack mark 16:51:05 ack ant 16:51:05 antoine, you wanted to ask about dev doc 16:51:28 q+ 16:52:22 PhilA - I was thinking that with a DBpedia-like effort on OSM data, they could get to a stage where they could provide a SPARQL endpoint 16:52:39 Agreed mark 16:52:57 ack phil 16:52:57 PhilA, you wanted to talk about JSON-LD 16:53:15 PhilA: lots of things could be done 16:53:47 PhilA: suggests using JsonLD instead of Json 16:55:22 AM: not aware of DBpedia effort on OSM data 16:55:27 ack deirdrelee 16:55:28 ack deirdre 16:55:42 PhilA mentioned http://geoknow.eu/ 16:57:06 rrsagent, draft minutes 16:57:07 I have made the request to generate http://www.w3.org/2014/03/31-dwbp-minutes.html PhilA 16:59:25 rrsagent, generate minutes 16:59:25 I have made the request to generate http://www.w3.org/2014/03/31-dwbp-minutes.html PhilA 16:59:56 bye 17:00:03 -laufer 17:01:05 HadleyBeeman has joined #dwbp 17:02:45 PhilA has left #dwbp 19:02:40 Zakim has left #dwbp 21:04:08 HadleyBeeman has joined #dwbp