15:38:16 RRSAgent has joined #md-odrl-profile 15:38:16 logging to https://www.w3.org/2021/03/17-md-odrl-profile-irc 15:38:18 RRSAgent, make logs Public 15:38:19 please title this meeting ("meeting: ..."), jo_ 15:38:38 Meeting: Market Data Rights Automation Teleconference 15:38:45 chair: Jo 15:38:53 regrets: renato 15:39:30 agenda: https://w3c.github.io/market-data-odrl-profile/agendas/md-odrl-profile-agenda-2021-03-17.html 15:54:25 belen has joined #md-odrl-profile 16:00:49 Ian_ has joined #md-odrl-profile 16:00:51 joshuaCornejo has joined #md-odrl-profile 16:00:57 ben has joined #md-odrl-profile 16:02:16 mark_bird has joined #md-odrl-profile 16:02:26 michelleR has joined #md-odrl-profile 16:03:20 Kyle has joined #md-odrl-profile 16:04:21 scribe: joshuaCornejo 16:04:35 Topic: Admin 16:04:59 https://w3c.github.io/market-data-odrl-profile/agendas/md-odrl-profile-agenda-2021-03-17.html 16:05:44 RESOLUTION: Accept minutes of last meeting 16:06:25 Jo: noticing that there are guests today, it is good to notice the formality 16:07:10 NigelP has joined #md-odrl-profile 16:07:35 Ben: trying to share my screen 16:07:37 Topic: Compliance and Redistribution PoC 16:07:51 ... we wanted to do an end-to-end demo 16:08:04 From a consumer to a provider/provider-administrator 16:08:37 ... we looked for something that has lots of cross-supply chain interactions 16:08:51 ... and if we could replace those with web-based or M2M requests 16:09:06 ... we also wanted to look at the end value of this, can we implement some kind of enforcement 16:09:23 ... the final area we thought it could touch was the overhead of maintenance 16:09:31 ... because there is a significant overhead 16:09:38 ... and looking to automate those kinds of changes 16:09:47 ... we picked out one particular use case: redistribution 16:09:56 ... we know that causes certain amount of heartache 16:10:09 ... looking to automating consent of redistribution 16:10:22 ... 16:11:15 present: jo, ben, josh, michelle, belen, markb, nigelp, kyle, ian, paul 16:13:12 present+ michael_aagon, alex, ali, justinas_alisaukas, andrew_dunkley, atiq, ian_bone, jorge_di_pasqua 16:13:50 Marko: need to share my screen 16:14:17 ... 16:15:26 Mark: and you just sucked in this from DataBP via ODRL ? 16:15:29 Marko: yes 16:15:53 present+ elizabeth_pritchard, emily, wilson_ferrer, richard_folsom, jeremy, gerardo_kilmurray, laura, letitia, jairy_meneses, mevan, fernando_nitz, roy, ilya 16:16:04 zakim, who is here? 16:16:04 Present: jo, ben, josh, michelle, belen, markb, nigelp, kyle, ian, paul, michael_aagon, alex, ali, justinas_alisaukas, andrew_dunkley, atiq, ian_bone, jorge_di_pasqua, 16:16:07 ... elizabeth_pritchard, emily, wilson_ferrer, richard_folsom, jeremy, gerardo_kilmurray, laura, letitia, jairy_meneses, mevan, fernando_nitz, roy, ilya 16:16:07 On IRC I see NigelP, Kyle, michelleR, mark_bird, ben, joshuaCornejo, Ian_, belen, RRSAgent, Zakim, jo_, notwendy 16:17:19 present+ marko, paul 16:17:55 Caspar: we've got a fake client application 16:18:13 ... the distribution component can understand the ODRL coming from the policy 16:18:38 ... 16:19:49 Mark: what Caspar has done is initiating a request to the content source 16:20:00 ... saying "can we distribute data to this 3rd party" 16:20:15 ... at this stage we send a "deny" 16:20:30 What could happen is that the user could go and create an approval 16:20:57 ... 16:23:20 Caspar: you can see we are still in pending state, waiting for consent 16:23:42 ... in the background the access has been pulled down and now it has been granted 16:24:02 ... 16:24:10 Ben: do you want to change the updating text? 16:24:17 Mark: it is very dramatic 16:24:41 ... 16:25:27 Caspar: now that we re-request, we can see the text has been updated 16:25:41 Ben: would be worth showing other use cases ? 16:26:27 Caspar: 16:26:55 Ben: we are speaking about a deontic state 16:27:51 ... 16:28:16 Mark: maybe stating the obvious, but we have 3 systems in play, moving in real-time 16:28:30 Atiq: demo worked first time, brilliant ! 16:29:18 ... the real value is the workflow in the exchange between dataBP, deontic and Goldman Sacks 16:29:23 ... which is quite an achievement 16:29:58 ... 16:30:07 ... and here we are building an API and how it might work 16:30:28 ... the reason why it is important is the business processes and what are the boundaries of responsibilities 16:30:50 ... 16:31:26 ... the final part is maintenance/changes ... building that into the process will be a timesaver 16:31:56 Ben: we will pick up some issues later in the meeting, what kind of testing we will be doing moving forward 16:32:17 ... 16:32:43 Jo: fantastic and successful demo 16:34:29 Emily: 16:34:47 Caspar: 16:35:41 Emily: paraphrasing - there is some uplifting into the apps, and going forward there will be a minimum threshold of how that uplift will take place 16:35:50 Caspar: 16:36:02 Michelle: you were talking about real-time update in policies 16:36:19 ... do you see this as going directly to the exchange? 16:36:40 Atiq: we still have to workout what the right model is 16:36:51 ... 16:38:32 Ben: we are working in a temporal model: in some cases we will receive a message today "this change will happen in 6 months time" ... and the system will work then it is effective 16:39:04 Mark: you can see from the demo I chose a date, but that could have been in the future 16:39:14 .. 16:39:36 Michelle: that is an interesting concept, that it could happen systematically 16:39:48 Atiq: if it reduce toil of the repetitive things we do 16:40:02 Laura: I had the same question as Michelle 16:40:17 ... there maybe other requirements that they might put in 16:40:54 Michelle: if you look at exchanges now and that you can add a new subscription, this model could be very useful 16:41:01 Jo: thank you everybody 16:41:24 ... you can add more questions via the email list 16:42:13 Topic: FISD Webinar in June 16:43:14 Ben: spoke to FISD on the topic of digital rights, my own sense is that the June timing is very good 16:43:41 ... rather than talking about the standard itself, focus on what the next steps are 16:43:56 ... whether people think a presentation in June is worth it 16:44:00 Jo: and demos 16:44:04 Ben: many demos ! 16:45:47 ... 16:46:05 ... and if we can show some demos, that's the most potent message 16:46:21 Jo: anyone disagrees ? 16:46:42 Ilya: we should tailor the message carefully for the wider community that haven't been so involved 16:46:56 RESOLUTION: We should pick up on the opportunity to present at FISD 16:46:59 Jo: I completely agree with that 16:47:37 Mark: a lot of the good work we've done has been defining test cases 16:48:02 ... and put some of that and communicate it to the broader audience 16:48:27 Olga has joined #md-odrl-profile 16:48:33 ACTION: Ben to call first coordination meeting to prepare for FISD 16:49:27 Ben: commits to deliver feedback in 2 weeks 16:50:06 Topic: Interoperability Testing 16:50:52 Ben: one of the things that the work has emphasise is the importance of validation - validating policies, knowing what is mandatory and what doesn't have to be there. I think that as people start doing implementations and PoC's and pull that work and publish it as part of the report on the standard 16:51:08 ... and another thing that is on a very early stages is the compliance API's that we are using in this PoC 16:51:43 ... and it would be worth to address if the API is also a standard and where is its home 16:52:13 ... the work we've done over the past few weeks have shown the importance of validation and compliance. Atiq do you have any thoughts? 16:52:45 Atiq: yes, we should find a way to keep the compliance and not just the ODRL component, the API works and behaves 16:52:58 ... and have a clear standard and change management works around it 16:53:09 ... so far it has been largely around desktop 16:53:20 ... but we should do an analysis on that 16:53:27 Ben: Ilya what is your sense on this 16:53:42 Ilya: you are probably talking code and a definition 16:54:21 ... 16:54:38 Ben: should we keep collaboration in the test cases 16:54:47 Ilya: such an interesting question for this group 16:55:07 ... there will be some interest in legacy organisations depending on the types of problems solved by this specification 16:55:35 ... depending on whether or not those API's are wide reaching enough 16:56:11 ... what maybe worth exposing is what data exchange is part of this API, so each group can work in what each part means for "them" 16:56:30 ... there are many implications and we haven't specify and can run into rabbit holes 16:57:16 Jo: it strikes me that API is a specific technology - we should get the models and try to specify in the context of flows and when (flows) people will be interested in things 16:57:53 Atiq: on the subject of an API as a framework, should we form a breakout group? 16:58:16 Jo: I'll action you for that 16:58:28 ACTION: Atiq to arrange break out session on APIs 16:58:35 Topic: AOB 16:59:51 scribe: jo 17:00:31 jo: Meeting reverts to 1100 US Eastern 1600 UK next time 17:00:44 ... congrats again to demo-ers 17:01:04 ... many thanks once again to Josh for scribing 17:01:14 --- meeting closed 17:01:26 rrsagent, make minutes 17:01:26 I have made the request to generate https://www.w3.org/2021/03/17-md-odrl-profile-minutes.html jo_ 17:01:42 present+ olga 17:04:32 rrsagent, make minutes 17:04:32 I have made the request to generate https://www.w3.org/2021/03/17-md-odrl-profile-minutes.html jo_ 17:07:02 ScribeOptions: -oldStyle -nodraft 17:07:05 rrsagent, make minutes 17:07:05 I have made the request to generate https://www.w3.org/2021/03/17-md-odrl-profile-minutes.html jo_ 17:08:53 joshuaCornejo has joined #md-odrl-profile 17:09:00 s/Ben: trying to share my screen// 17:09:26 s/... we wanted to do an end-to-end demo/Ben: we wanted to do an end-to-end demo 17:09:44 s/From a consumer/... From a consumer 17:09:53 rrsagent, make minutes 17:09:53 I have made the request to generate https://www.w3.org/2021/03/17-md-odrl-profile-minutes.html jo_ 17:10:48 s/noticing that there/noting that there 17:11:38 s/What could happen is that the user could go and create an approval/... What could happen is that the user could go and create an approval/ 17:13:39 rrsagent, make minutes 17:13:39 I have made the request to generate https://www.w3.org/2021/03/17-md-odrl-profile-minutes.html jo_ 17:20:26 present+ david_sarkis, elizabeth, emily, wilson, richard_F, jeremy_bock, gerardo, laura, letitia, jairy, fernando, roy, Ilya 17:20:31 rrsagent, make minutes 17:20:31 I have made the request to generate https://www.w3.org/2021/03/17-md-odrl-profile-minutes.html jo_ 17:22:10 present+ paulC, andrew_mor, caspar 17:22:16 rrsagent, make minutes 17:22:16 I have made the request to generate https://www.w3.org/2021/03/17-md-odrl-profile-minutes.html jo_ 17:24:06 present+ caspar 17:24:21 present+ paulc 17:24:39 present+ andrew_mor 17:24:44 rrsagent, make minutes 17:24:44 I have made the request to generate https://www.w3.org/2021/03/17-md-odrl-profile-minutes.html jo_ 17:25:23 zakim, byte 17:25:23 I don't understand 'byte', jo_ 17:25:28 zakim, bye 17:25:28 leaving. As of this point the attendees have been jo, ben, josh, michelle, belen, markb, nigelp, kyle, ian, paul, michael_aagon, alex, ali, justinas_alisaukas, andrew_dunkley, 17:25:28 Zakim has left #md-odrl-profile 17:25:31 ... atiq, ian_bone, jorge_di_pasqua, elizabeth_pritchard, emily, wilson_ferrer, richard_folsom, jeremy, gerardo_kilmurray, laura, letitia, jairy_meneses, mevan, fernando_nitz, roy, 17:25:31 ... ilya, marko, olga, david_sarkis, jeremy_bock, paulC, andrew_mor, caspar 17:25:50 ben has left #md-odrl-profile 17:25:51 rrsagent, byte 17:25:51 I'm logging. I don't understand 'byte', jo_. Try /msg RRSAgent help 17:25:58 rrsagent, bye 17:25:58 I see 2 open action items saved in https://www.w3.org/2021/03/17-md-odrl-profile-actions.rdf : 17:25:58 ACTION: Ben to call first coordination meeting to prepare for FISD [1] 17:25:58 recorded in https://www.w3.org/2021/03/17-md-odrl-profile-irc#T16-48-33 17:25:58 ACTION: Atiq to arrange break out session on APIs [2] 17:25:58 recorded in https://www.w3.org/2021/03/17-md-odrl-profile-irc#T16-58-28