CERN-Solid planning meeting

Wednesday 6 May 2020, 16:00 → 18:00 Europe/Zurich

Maria Dimou (CERN)

The aim of this  meeting is to discuss on the areas identified during the very first February 7th brainstorming and decide what exactly we propose to the developers and how they communicate.

Due to the COVID-19 teleworking conditions, the proposals and estimated effort have to be concrete. Current operational conditions are very requiring on the teams.

Participants: Sarven Capadisli (input on notifications),  Maria Dimou (notes),  Michiel de Jong (diagramme), Mitzi László (moderator - present for sometime).

Meeting held in Zoom.

Present: Maria, Michiel, Mitzi (for some time), Sarven.

Summary:

1. Apply incremental changes  to CERN applications to make them Solid-compatible. Indico and CS3MESH are good candidates.
2. Alternative approach would be for CERN to join W3C Working Groups who do Solid standardisation work. Maria wrote this proposal which includes Web Access Control (a Solid activity today). Maybe Maria to revive that proposal?...
3. Indico  & C3MESH: Michiel drew this workflow for restricted data, when Web access control is needed via WebID. Candidate applications are Indico and C3MESH. Reasons and method (by Michiel):
   Solid is all about a three-way separation between identity, storage, and applications.
    
   Both CS3Mesh and Indico could benefit from exposing a storage API that Solid applications can access. The access control could be handled by a Web Access Control (WAC) proxy that sits in front of your system's data API. The Access Control Lists that drive the decisions of the WAC proxy would also be stored inside your system.
    
   What makes Solid Access Control Lists quite unique is that they refer to users with URIs that can live anywhere on the web, not necessarily within any particular walled garden.
4. New CERN SSO: Michiel is interested in the new SSO internals (Maria will find a doc which requires no CERN login to access).
5. Notifications: Sarven sent, after the meeting, the various Solid-specified notification protocols based on web sockets:
   In the Solid project, we are generally working with and looking into the interaction between different actors (servers and/or clients). It generally touches on the following protocols:
   1. Linked Data Notifications: https://www.w3.org/TR/ldn/ Interaction between senders, receivers, and consumers. Sender sends to Receiver. Consumer pulls from Receiver. Part of the Solid specification.
   2. The WebSocket Protocol: https://tools.ietf.org/html/rfc6455 Interaction between server and client. Client initiates communication. Bi-directional messaging while keeping connection open. In the process of being integrated into the Solid specification. These two protocols are not interchangeable. They address different needs. However, they can be interoperably combined to meet different scenarios. Authentication and Authorization remain orthogonal. One of the contributions of my PhD thesis is the Linked Data Notifications protocol: https://csarven.ca/linked-research-decentralised-web#linked-data-notifications Have a glance at the sub-sections ( comparisons, interoperability, considerations..) as they situate LDN as part of a wider ecosystem. There is a Solid Notifications Panel: https://github.com/solid/notifications-panel It is intended to tackle next steps - it may seem inactive but it is in our radar once we get through some of the other requirements in the Solid specification. See the use cases mentioned in this issue to get a glimpse: https://github.com/solid/notifications-panel/issues/1
      Solid is active in https://gitter.im/solid/specification for anything pertaining to the Solid specifications.

   On the CERN side, Maria asked Eduardo, who inherited the notifications' project, after the meeting:

   1. for more recent status of the notifications project as this presentation  is out of date:

      Pablo Roncero has finished the first iteration implementation of the tentative notifications portal (aka the frontend), https://test-notifications-service.web.cern.ch/ (only accessible within CERN network)

      
      We are now starting the investigation on backend options for the message pipeline and delivery at scale. We are a bit behind my expectations at this moment, so it's important to focus on having the prototype by summer with enough functionality to show the idea but without over complicate things.

       

   2. for confirmation that these are push notifications project something like this https://cern.ch/dimou/it-us/zephyr.shtml (info on service status pushed to all users, platform-agnostic):

      Indeed this use case could be also covered by the Notifications service (probably also mixed with Mattermost) I foresee indeed a set of official channels that users can subscribe to in order to receive news. These news can certainly be Service oriented ones, alarms, ... And the important difference here compared with Mail is the ability for the user to decide when and how they receive the information.

   3. Is it like https://mattermost.web.cern.ch/it-dep/channels/itstatusboard (service status board - requires CERN login)?

      Certainly there are a lot of similar functionalities between both systems. Probably Notifications service will be more used for notifications, while Mattermost offers more a bi-directional communication. I think both systems should be linked and integrated together for a bigger success.

   4. Do we wish to archive the notifications content?

      Yes, I foresee users will be interested in access previous content sent through the notifications service. We foresee two levels of data. Live data kept up to X months (to be defined) to be stored directly on the backend system chosen. And archived notifications stored for long preservation on a different place (archive static web application) Probably something similar of what Emmanuel is implementing for the E-groups archive replacement for Sharepoint.

6. Chat: Maria created https://gitter.im/cern-solid/community on suggestion by Michiel. Reasons: We need a functional chat tool for the CERN-Solid project:
   1. Mattermost is out because it requires CERN login.
   2. One can see existing Solid chats groups on the right banner of the CERN-Solid Indico category that Maria created to facilitate newcomers to this collaboration. CERN developers may not join on-going chats. People will give time if it is inline with their own projects.
   3. Email is out, except for rare things like calling a meeting.

 

 

 

16:00 → 16:10 Agree on this agenda

Maria made this list of items to discuss based on areas mentioned at the February 7th brainstorming meeting.

The question is what can we actually do together at the current stage.

Speaker: Maria Dimou (CERN)

16:10 → 16:40 Identify a collaboration area from the candidates discussed

Maria's intro for the discussion. Check conclusions in the Minutes!

During the February 7th brainstorming meeting one finds also in the Summary:

Sarven suggests to take individual notions under the Solid umbrella, that can be adopted by CERN projects, and evolve the specifications based on the problems encountered and documented. The area of notifications is worth exploring further.

Further in the last February notes, the following areas were mentioned as possible candidates for mutual interest, in the framework of WebID-OIDC:
a. Indico
b. CS3MESH
c. the new CERN SSO
d. notifications

As discussed in email:
a. Sir Tim and Michiel saw a collaboration potential for Indico. Michiel wrote about WebID and OIDC. Lets discuss what/how.
c. Solid partners have no access to the Auth/AuthZ White Paper. The question is whether the new CERN SSO (Single Sign On) is important in the coming 6 months for common technical exchanges. If yes, I'll have to introduce our activity to the new CERN SSO developers' team and bring them on-board, because they were not in our meeting... The project won't be operational probably before February 2021. Then I'll check what is the most recent material to send you.
d. You asked about the push notifications service concept. The concept is to inform everyone cross-platform, especially on service incidents with large community impact, independently of each user's working platform. Like Zephyr messages if you remember...

What is realistic to tackle first, knowing the very special period we are living with COVID-19 and the difficulties to fire-fight during teleworking?

cern-solid.png

16:40 → 17:10 Solid specification and communication channel

Find a way to communicate between CERN and Solid developers. Nobody will do email. We use mattemost in CERN IT internally. Impossible to use it without CERN login.

Existing Solid chat and even the chat dedicated to the specification work have general activities that will discourage the CERN developers, due to lack of time.

Discussion on a dedicated chat channel for CERN and Solid collaborators only.

CERN-Solid chat channel

17:10 → 17:30 Conclusions & what now?

Maria summarises and all conclude and confirm what the next step is.
You can see the conclusions in the Minutes of this event.

Speaker: Maria Dimou (CERN)

17:30 → 17:35 A.O.B.