Comments for MyData 2016 http://mydata2016.org Tue, 23 Aug 2016 07:34:25 +0000 hourly 1 https://wordpress.org/?v=4.9.16 Comment on New legal framework – towards My Data? by Geoff Revill http://mydata2016.org/2016/08/17/new-legal-framework-towards-my-data/#comment-96 Tue, 23 Aug 2016 07:34:25 +0000 http://mydata2016.org/?p=5335#comment-96 Simple article with seemingly a call for insurmountable solutions. The re-use of portable personal data, especially the ever valuable meta-data and derived data from analytics (do we have rights for portability of that? unclear in the GDPR), creates a new technical requirement – INTEROPERABILITY. This is a scary term for online businesses that be default seek to build walled gardens around “their” data assets. Allowing that data over the wall because you have to under the law is one thing, building an open doorway with no lock into the wall so the data can freely leave (or enter), requires a new business model and a fundamental cultural mindset change in online commercial business models.
However at the technical level, real interoperability through semantical defined data that delivers inherent interoperability is viable TODAY! I am speaking at the event on trust in digital engagement – but if anyone wants to chat about Interoperability let me know, its another area of passionate commitment.

]]>
Comment on Participatory programme planning by Adrian Gropper http://mydata2016.org/2016/01/29/participatory-programme-planning/#comment-25 Tue, 09 Feb 2016 19:23:13 +0000 http://mydata2016.blog.okf.fi/?p=1188#comment-25 The ability for individuals to delegate access to service provider APIs is paramount. This needs to be done in a person-centric rather than institution-centric way. Much about this is being done in the Kantara User Manged Access (UMA) workgroup. But we’re not home with a person-centered architecture until UMA explicitly allows the individual API subject to specify _any_ Authorization Server without restriction or certification by the data holders. This includes dynamic client registration under the Authorization Server’s control.

]]>