12th September 2019
Hello and welcome to another edition of This Week in Solid!
Solid is a set of open specifications, built on existing open standards, that describes how to build applications in such a way that users can conveniently switch between data storage providers and application providers and take the data generated along.
This is a weekly summary of Solid progress.
Want something mentioned? Contact the Solid Manager at email@example.com. This Week in Solid is openly developed on GitHub. If you find any errors in this week’s issue please submit a pull request.
Want to get involved? Contributions are welcome.
Every Thursday there is an hour-long public call where newcomers can introduce themselves, anyone can ask general questions about Solid, and we recap the weeks’ works on Solid.
Tune in at this line:
- on the 2nd January 2020 at 16:00.
- on the 9th January 2020 at 10:00.
- on the 16th January 2020 at 16:00.
- on the 23rd January 2020 at 10:00.
- (and so on, alternating at 10:00 CET and 16:00 CET, unless otherwise noted here)
Weekly Solid Call
Every Thursday there is an hour long public call where newcomers can introduce themselves, anyone can ask general questions about Solid, and we recap the weeks works on Solid. This week the call was cancelled so there are no minutes but next weeks call will be on the 19th September at 1000 CEST on this line.
Talks & Articles
Have you seen any articles or talks about Solid this week? If you’ve seen any talks, articles, or written blog posts about Solid please do send them over for next week.
- Mitzi L to speak at the Nextcloud conference on the 15th September
Solid Events are run by members of the Solid community like you. If you are interested in organising a Solid Event you may be interested in reading the tips for a organising successful Solid events here.
|12-09-2019||Solid Berlin||Christian Buggedei|
|10-10-2019||Solid Amsterdam||Jeroen van Beele|
Solid Data Workers
NLNet Foundation has accepted the application to the NGI0 PET Fund for the Solid Data Workers project, which aims to populate and enrich the personal linked data graph hosted in a Solid pod by fetching data from existing sources through dedicated applications (called “Workers”). You can find progress notes about the various components involved in the project - still in a very early stage - at https://semantic.builders/ If you have any new apps, Pods, or identity providers or there are updates to existing Solid implementations make sure to add them to the list so they get included in next weeks edition. There are no updates on Solid implementations this week.
Have you ever heard about Startin’blox?
Startin’blox is a french community of freelancers developing a framework of web components to be used in the creation of applications. TA DA! On September 4th Happy Dev has published its brand new web site entirely made with Startin’blox ! Happy Dev is a European network of 500+ digital freelancers: https://happy-dev.fr. And guess what, all Startin’blox components are Solid compatible. This is the 5th Startin’blox application running in production, and more coming soon!
- Minutes from Panel Meeting #3 on 2019-09-09, which was focused on reviewing proposed Use Cases for Data Validation
Updates on Solid Projects
Solid projects are activities happening on the Solid GitHub other than panels. Below are the links to where there were active conversations on each of the projects.
These releases do not contain major changes; rather, marking them as v1 merely represents the reality of trying not to introduce breaking changes to them.
Introducing user types Developer and Power User
The data browser team at inrupt is dedicated to improving the Solid data browser. As part of this work, we wanted to improve the onboarding experience for new users, and we identified the number of views (aka panes) as one of the challenges for new users. Some of these views are also difficult to use, and we concluded that it might be prudent to limit some of the views shown.
To address this we’ve introduced the concept of user types. These are opt-in and saved in user’s preferences, which are private by default. The idea is that the various views can describe which user types they consider as their audience, and the data browser will hide these views if the user hasn’t self-assigned that user type.
An exception to this rule is that if a given resource is about a very specific thing, the data browser will still include the most relevant view for this, even thought the view have indicated an audience that you’re not part of (this is useful when resources are shared with other users that have other or no user types self-assigned).
How will this affect my experience of the data browser
If the Solid server that hosts your Pod is using a version of the data browser that includes this feature (note: solid.community and inrupt.net will upgrade to this as soon as we’ve fixed some bugs, probably by early October, 2019), you may notice that some views disappear. To access these views, you will have to set user roles for yourself. You can do this through Preferences, which you can access through your Dashboard (which is globally available through your user menu, or on the root of your Pod).
To get a complete list of views and which ones that are connected to the various user roles, please refer to this document that describes the current state of the data browser (work in progress).
Until next week!