# SolidOS Team Meeting

* Date: 05.03.2023 18:00 (UTC+2)
* Call: [https://meet.jit.si/solid-operating-system](https://meet.jit.si/solid-operating-system)
* [Previous meeting link]()
* [Next meeting link]()
* Chat: [https://gitter.im/solidos/solidos](https://gitter.im/solidos/solidos)
* Repository: [https://github.com/solidos/solidos](https://github.com/solidos/solidos)
* Meetings home: [https://solidos.solidcommunity.net/public/SolidOS%20team%20meetings/](https://solidos.solidcommunity.net/public/SolidOS%20team%20meetings/)
----

## Present attendees

* Timea, Angelo, Noel, Tim, Rahul (CxRes), Jon, Alain, Jeff

### Scribes

* Angelo

---

## Topics

### Round Table

#### Noel
* Trying [Nextcloud Solid](https://github.com/pdsinterop/solid-nextcloud/) - to use it you need to be an admin of the server. I thought by only having an account one can use it. Not the case.
* Angelo: the Solid integration?
* Noel: Yes, it is a plugin for Nextcloud and only an admin can add it.
* Angelo: I am running my own NextCloud and I would be interested in your findings.
* Tim: If you do something as admin - if you activate the Solid Plugin do you activate it for all users?
* Noel: Yes I think so. It created the NextCloud files in your folder -> good experience. Maybe my next server will be this one. Because my personal server is NSS old one. I need to upgrade it.
* Umai works and Media Kraken should work too.

#### Angelo
* I met with Jeff and exchnaged ideas on how to build components that work on Solid Pods. We are going to integrate these ideas

#### Tim

* Inrupt all-hands in Barcelona

#### Jon

* Working on website for meetup
* Should include links to documentation
* Wants to contribute to onboard new developers
* Will sync with Timea on where to start

#### Rahul

* Going to start on a new demo for his app
* Site: https://syntropize.com
* Code: <https://gitlab.com/syntropize/syntropize>
* Release: <https://gitlab.com/syntropize/syntropize/-/releases>

using linked data.
* Technical questions about organizing data.

#### Timea

- has also been to Barcelona
- nothing new regarding solid-ui
- working on a ChatGPT demo, that is firing SPARQL queries to a pod and translate it back to natural language

#### Alain

- working on chat proof (chat messages signed with keys)
- can demo, but not fully ready to merge
- two issues:
1. where to store the keys? keys container? profile doc?
2. WebID may be outside of the Pod
- looking into the 302 redirect issues, but could not find issues in rdflib
- Angelo: Problem is in SolidOS as well, see https://solidos.github.io/mashlib/dist/browse.html?uri=https%3A%2F%2Fbourgeoa.solidcommunity.net%2Fchats, so I assume it is a rdflib problem

#### Jeff

- converting solid-uix components to webcomponents
- moved repo to SolidOS org

### Main topics

#### Solid-UI
* nothing new

#### Solid Chat
* see Alain's update
* Sharon is doing some tests and she needs some help to mock a fetch load.
* Angelo: can help.

### Technical topics

#### SOLID protocol 0.9 to 0.10
URL: https://solidproject.org/TR/protocol
URL: https://solidproject.org/TR/protocol#change-log

* Noel was looking into the changes
* Many things are optional / non-normative
* Will pod providers then implement it?
* Confusion about non-normative section about `constrainedBy` in Link headers (https://solidproject.org/TR/protocol#constraints-problem-details)
* Tim: This thing is worring because it encourages servers to be incompatible to the spec as long as they communicate it via this header
* Noel: Aggree! As an app developer I expet my Solid Apps to work, if they follow the Solid Spec
* Rahul: Servers may use 404 or redirect, which is also ambiguous for the client

#### Rahul: Syntropize with Linked Data

- Rahul: How shall I organize data that is partially in a container hierarchy, but also links to other data outside that hierarchy? Example: Car->Engine->Converter-> ...
- Noel: Define relationships with RDF, not with containment relationships. Containers should not matter, e.g. my app should find recipes wherever they are in the pod, not only in one container
- Tim: I tend to differ: Recipe collection is socially important. I want to share different collections with different people. It is important for access control. You can use both, containment as well as relations like `subPartOf`
- Noel: I might have to lists: vegan recipes & my favorite recipes, and they might overlap, so those cannot be containers
- Tim: Same problem with address books where contact cards to be shared are in multiple groups
- Noel's conclusion: containers are for organizing data, links are for semantics. Apps follow their nose, they should not assume anything about the structure of the data
- Tim: Look at desktop apps: they have some of the same contraints. Like iPhoto has a hidden folder where it organizes stuff, like putting your photos into albums etc.
- Jeff: You can organize access based on groups
- Timea: data is represented in multiple ways: Structure (LDP), Indexes (Type Index), Access control (what can the user see, the groups the user is part of) -> on top of these options, a user gets like a personalized window in the data, like a data view based on the type of data and access control.

#### Alain Demo

- next week

---

This template is based on the [W3C meeting template](https://github.com/solid/specification/blob/main/meetings/template.md)

[Code of conduct](https://github.com/solid/process/blob/main/code-of-conduct.md)