13:08:48 RRSAgent has joined #dwbp 13:08:48 logging to http://www.w3.org/2014/08/29-dwbp-irc 13:09:04 rrsagent, set log public 13:09:14 topic: minutes from last week 13:09:17 Today's agenda: https://www.w3.org/2013/dwbp/wiki/Meetings:Telecon20140829 13:09:31 +??P17 13:10:07 +??P18 13:10:09 PROPOSED: approve last week minutes http://www.w3.org/2013/meeting/dwbp/2014-08-22 13:10:12 markharrison has joined #dwbp 13:10:28 +1 13:10:33 0 - wasn't on the call 13:10:40 +1 13:10:41 +1 13:10:48 +1 13:10:54 +1 13:10:54 +1 13:10:58 0 13:11:05 0 13:11:05 RESOLVED: approved last week minutes 13:11:09 zakim, mute me 13:11:09 laufer should now be muted 13:11:26 No 13:11:31 yes 13:11:32 TOPIC: TPAC 13:11:33 scribe: cgueret 13:11:48 how many participants of the group are going there? 13:11:56 deirdrelee: not registered yet, not sure will go 13:12:08 I will probably be there. 13:12:17 ivan: best to register only if you know you'll really go ;-) 13:12:56 Zakim, who is speaking ? 13:13:09 cgueret, listening for 12 seconds I heard sound from the following: deirdrelee (32%), EricKauz (7%), adler1 (19%) 13:13:19 -??P17 13:13:19 EricKauz: not sure I will go either 13:13:42 deirdrelee: will there be remote participation ? 13:13:55 https://www.w3.org/2002/09/wbs/35125/TPAC2014/registrants#DWBP 13:13:56 ivan: not sure for video, phone will be available for sure 13:14:04 +??P17 13:14:30 Zakim, ??P17 is me 13:14:30 +jerdeb; got it 13:15:06 ivan: advance reg closes on Oct 8, late is open until the day of the conference 13:15:59 Topic: open issues and raised issues 13:16:48 deirdrelee: there is a lot of properties we re-used across all the documents 13:17:05 ... applied in different contexts 13:17:17 ... made a table to visualise the situation 13:17:36 ... let's talk about it and from there look at all the issues 13:18:21 ... for instance for metadata we have all the keywords 13:18:59 ... shall all the concepts have all the properties associated to them ? 13:18:59 http://lists.w3.org/Archives/Public/public-dwbp-wg/2014Aug/att-0081/DWBP_Requirements_Matrix.csv 13:19:16 ... or is there that, e.g. do not need to be machine readable 13:19:43 EricKauz: machine readable should be a req for all 13:19:54 I've tried to summarize my points at http://lists.w3.org/Archives/Public/public-dwbp-wg/2014Aug/0083.html 13:20:31 ... difference between metadata and vocabs ? 13:21:02 deirdrelee: metadata are descriptions, vocabularies are things such as DCAT and OWL 13:21:13 EricKauz: vocabularies are fields of metadata, right ? 13:21:21 not me talking. 13:21:29 sorry :/ 13:21:34 s/EricKauz/steve 13:21:40 zakim, unmute me 13:21:40 laufer should no longer be muted 13:21:44 adler1 is talking, I think 13:21:50 Q? 13:22:30 adler1: the vocabulary is a single instance used by all the metadata 13:22:34 +1 to this def 13:22:51 Ig_Bittencourt has joined #DWBP 13:22:58 -1: refering to vocabularies as 'instance' is confusing 13:23:07 ... but otherwise the intention is good 13:23:19 ... in practice metadata, formats and vocabularies are three facets of the same thing 13:23:40 ... is "provenance" lineage ? 13:23:53 ... should be then a field in the metadata ? 13:23:54 +q to say that interoperability is a desirable outcome and that machine-readable + standardised are things we can do (as best practices) in order to support this desired outcome. 13:23:54 q+ 13:25:02 adler1: SLA may be a clause in a license 13:25:14 ... whereas provenance can be a string 13:25:35 ... need many fields than can be all recorded in metadaat 13:25:48 q+ 13:26:33 markharrison: looking at the table I think "interoperable" could be dropped as "machine-readable" is a req for this 13:26:57 adler1: so remove interoperable column ? 13:27:16 markharrison: can not be practicaly implemented unless you do machine readable and standardised 13:28:01 Q+ to ask if differeint standard application-profile still implies interoperability? 13:28:06 ack markharrison 13:28:06 markharrison, you wanted to say that interoperability is a desirable outcome and that machine-readable + standardised are things we can do (as best practices) in order to support 13:28:09 ... this desired outcome. 13:28:15 ack antoine 13:28:22 q- 13:29:22 antoine: had licence provenance and SLA has type of metadata 13:29:27 s/has/as 13:29:47 adler1: vocabulary is the template of the metadata to describe the data 13:30:00 ... SLA is a form of a licence term 13:30:07 +q to say provenance is closer to being an intrinsic property of the data - its sources and transformations, irrespective of how it is licenced. Both are aspects of metadata (data about the data). Of course, there may be a provenance aspect of licence, e.g. for GPL licenced components that have impacts on the resulting licence for derived works. 13:30:30 vocabulary is the language to describe the metadata 13:30:36 deirdrelee: ok to drop available and interoperable 13:30:43 well said laufer 13:31:11 MakxDekkers has joined #dwbp 13:31:16 q+ 13:31:46 ack deirdrelee 13:31:46 deirdrelee, you wanted to ask if differeint standard application-profile still implies interoperability? 13:32:09 antoine: if someone creates an application profiles that is not interop it is probably because this was needed 13:32:27 ... application profiles should then be a minimal level of compatibility 13:32:52 q+ 13:33:35 proposed: drop interoperable 13:34:23 q+ 13:35:01 ?: license can be changed without changing provenance 13:35:18 s/?/markharrison 13:35:37 ack markharrison 13:35:37 markharrison, you wanted to say provenance is closer to being an intrinsic property of the data - its sources and transformations, irrespective of how it is licenced. Both are 13:35:37 +q to respond to Deidre that the interoperability of two application profiles that are both machine-readable and aligned with standardised terms may also depend on intersection of the machine-readable standards used - if no intersection in format or vocabulary, they may not be interoperable 13:35:41 ... aspects of metadata (data about the data). Of course, there may be a provenance aspect of licence, e.g. for GPL licenced components that have impacts on the resulting licence 13:35:41 ... for derived works. 13:35:47 adler1: lot of good points but those are vocabulary issues 13:35:59 CarlosIglesias has joined #dwbp 13:35:59 +1 in respect to drop interoperable 13:36:05 +1 too 13:36:18 ack antoine 13:36:30 +1 to drop interoperable 13:36:37 antoine: agree with Mark about what he said on provenance 13:36:49 ... license prov and SLA should be kept explicit somewhere 13:36:55 +??P20 13:36:58 +1 13:37:12 zakim, ??P20 is really me 13:37:12 +CarlosIglesias; got it 13:37:26 laufer: we have to talk about standardized instead of just interop 13:37:33 ... interopable is about standardd]\ 13:38:08 ... see what is interop with what thing 13:38:11 q 13:38:16 q? 13:38:16 q? 13:38:19 ack laufer 13:38:21 +??P22 13:38:32 q+ 13:38:52 zakim, ??P22 is me 13:38:52 +MakxDekkers; got it 13:39:03 markharrison: interoperability is about profiles that are machine readable and aligned with vocabularies 13:39:15 ... interop depends on vocabularies used 13:39:30 ... machine readable without same vocabularies used is not interopable 13:39:59 PROPOSED Remove 'interoperability' as a separate requirement 13:40:08 +1 13:40:09 +1 13:40:11 +1 13:40:13 +1 13:40:14 +1 13:40:16 +1 13:40:17 deirdrelee: we agree to remove interopable as a specific req and instead merge it with machine readable 13:40:17 +1 13:40:18 +1 13:40:19 +1 13:40:33 RESOLVED Remove 'interoperability' as a separate requirement 13:40:55 deirdrelee: second proposal about avbailability 13:41:06 q+ 13:41:13 ... maybe we can include it into another req 13:41:18 q- 13:41:21 q- 13:41:47 antoine: available should apply to licenses, prov and SLA to record that they should be provided 13:41:56 ... and that would be the only req for these 13:42:10 what about data schema 13:42:18 deirdrelee: do not agree, for some of them there are more reqs 13:42:54 q+ 13:43:39 deirdrelee: prov. sla and license could inherint everything from metadata 13:43:46 ... so we don't repeat it 13:44:05 adler1: of course metadata should be available but it's not implying all the fields should be there 13:44:16 ack antoine 13:44:20 q+ 13:44:22 ack adler 13:44:22 ... someone may have a license but chosen not to create an SLA clause 13:44:49 ... you can't insist everything is available 13:45:54 ... strugling a bit with the meaning of "available" actually 13:46:11 it sounds like a may, should and must issues... 13:46:26 deirdrelee: that's something to work on, suggesting remove metadata as available req 13:46:35 PROPOSED Remove 'metadata-availability' as a separate requirement 13:46:48 +1 13:46:49 +1 13:46:52 +1 13:46:53 +1 13:46:54 +1 13:46:56 +1 13:46:56 +1 13:47:15 RESOLVED Remove 'metadata-availability' as a separate requirement 13:47:22 +1 13:47:51 deirdrelee: SLA, prov and licenses are type of metadata 13:48:10 q+ 13:48:24 ... we can remove all of those in the table 13:48:48 antoine: they should be available when applicable 13:48:54 +1 to Antoine's e-mail suggesting to fold availability into other requirements e.g. 'should be made available as/in....' 13:48:57 ... if it's there it should be expressed 13:49:01 +1 to Antoine 13:49:31 deirdrelee: best practice should be there should always be a license there 13:50:48 ... maybe something to do through all the documents, see which keyword to use where 13:51:22 laufer: most important thing is the schema 13:51:27 Q+ 13:51:28 ... this is the first meta-data 13:51:43 q+ 13:51:56 ... why don't we have it as a type of metadata ? 13:52:09 -MakxDekkers 13:52:23 ack antoine 13:52:30 ack laufer 13:52:34 antoine: that relates to the req for vocabularies 13:52:48 deirdrelee: the metadata schema is adressed through all the reqs 13:53:05 ... there all applied to the metadata schema 13:53:12 +q to propose that licence info should be stated explicitly where possible, since this helps data consumers and application developers to know whether they can use that data as a source. It the licence is unspecified, there may be too much risk of using the dataset (if the data consumer cannot work with whatever licence might be specified in future) 13:53:14 +??P8 13:53:27 ... license prov and SLA are mentionned explicitely as they were highlihted in the UCR document 13:53:39 ... this is why they are specified 13:54:19 laufer: ok but why having vocabularies and not schema ? 13:55:25 adler1: we don't have to worry about omitting licenses 13:55:39 ... it's an obvious req 13:55:59 ok, antoine 13:56:05 ... the interesting discussion is about the SLA 13:57:10 +1 to adler1 re lack of stable SLA and licence potentially limiting reliance on open data 13:57:29 PROPOSED Remove metadata repeated requirements from License, SLA and provenance, and specify they are types of metadata 13:57:48 +1 13:57:48 +1 13:57:50 +1 13:57:50 +1 13:57:51 +1 13:57:52 +1 13:57:53 +1 13:57:54 +! 13:57:56 +1 13:57:59 -??P8 13:58:05 +1 13:58:22 RESOLVED Remove metadata repeated requirements from License, SLA and provenance, and specify they are types of metadata 13:58:42 adler1: thx deirdrelee for a great table that focused a lot of discussion 13:58:59 deirdrelee: close issues via e-mail ? 13:59:36 ... is that ok with W3C practices ? 13:59:59 -Ivan 14:00:17 bye, nice weekend for all 14:00:20 deirdrelee: end of meeting 14:00:23 -EricKauz 14:00:25 bye 14:00:25 bye! 14:00:29 bye! 14:00:29 bye 14:00:31 -RiccardoAlbertoni 14:00:32 -laufer 14:00:33 -adler1 14:00:34 -jerdeb 14:00:36 -antoine 14:00:39 bye! 14:01:03 -CarlosIglesias 14:01:12 deirdrelee: do we need to launch any command before closing the chat ? 14:01:13 we have to close issues in calls but we can record proposal and agreement of people involved in issue 14:01:34 -??P18 14:01:40 cgueret, just checking 14:02:08 -cgueret 14:02:37 -deirdrelee 14:02:37 DATA_DWBP()9:00AM has ended 14:02:37 Attendees were antoine, EricKauz, deirdrelee, cgueret, +1.516.353.aaaa, adler1, RiccardoAlbertoni, laufer, Ivan, jerdeb, CarlosIglesias, MakxDekkers 14:03:38 no, they seem to be here already http://www.w3.org/2013/meeting/dwbp/2014-08-29 14:03:54 bye 14:04:00 great 14:04:02 bye 17:37:58 ivan has joined #dwbp