This is a brainstorming between:
Maria Dimou - CERN-Solid collaboration manager
Michiel de Jong - Solid developer
Pedro Ferreira - Indico project leader
Adrian Moennich - Indico chief developer
Jan Schill - MSc student
The purpose of this meeting is to discuss point 3 of Jan's project, namely give some inside info of the Indico code, structure, philosophy, update methods and advice on how to:
Adrian, Jan, Maria, Michiel, Pedro discussing Jan's MSc project HERE
For Jan to do for Point 3:
Tackling the "Comments in user's pod" first:
Tackling the "Registration form" module expansion to keep user's personal data out of Indico:
About point 4 in Jan's project, namely:
comparing the Solid approach with the design principles adopted by the relevant CERN applications
Pedro said that some of Indico data, e.g. material attached to an event, must be kept centrally for archiving purposes and data integrity, they can't be left to Solid and the user's pod.
Michiel said that other applications like Calendar and Contacts can live in the user's pod.
These are some of the elements that can be reported as output of the approaches' comparison.
About point 2 in Jan's project, namely:
evaluating the first Solid implementations,
Other Solid implementations can be found HERE. Links to their internals by Michiel:
https://github.com/michielbdejong/empty-solid-app https://empty-solid-app.5apps.com/ https://github.com/linkeddata/rdflib.js
At CERN we use owncloud with the in-house development cernbox.cern.ch. Project CS3-MESH is listed in the CERN-Solid collaboration index, as one of the candidate applications to be influenced by Solid.
Outside the CERN-Solid project:
Jan and co-student have to study security frameworks for the software engineering course. The idea is to use Indico for this study. This will give in-depth Indico knowledge to Jan. Adrian, being a security expert, will be of great help. He suggests, as a first step, to define, what a security framework is.
Notes by Maria - please comment/fix
Notes by Jan can be found HERE