solidproject.org
solidproject.org copied to clipboard
solid
Solidifying the Solid Project
This issue is a place to discuss the long term goal of a one hundred percent Solid sp.org website and a write-up helping other organizations to solidify their traditional websites. Being served from a pod is only one step in that process. Another key step is generating structured data (lists of people or things such as are found in Solid Process) from semantically organized data (RDF). This might sound like a technical goal, however it is also impacts workflow and especially conceptualization of the project. It isn't about having data stored in a given format, it's about having the display and linkages be generated from the meaning of the data.
In terms of workflow - eventually we will replace our current Markdown -> Jekyl -> Website workflow with an RDF -> Something -> Website workflow. That's in the future (though a proof-of-concept should be available soon).
The part we need to think about now is - how do we represent the meaning of sp.org the project and use that to generate portions of sp.org the website.
We need to think of that now for several reasons. We want the categories we use to 1) reflect the project goals and values 2) be easily understandable to users 3) be organized in a way that supports us querying and displaying in ways that further project goals.
The organization of the information relates to the survey and apps template. I've made a preliminary way to conceptualize Solid stakeholders but we'll have to completely revisit that once we have data from the survey. This also relates indirectly to the apps template and other forms we use - we should think about not only what data we want to display but what data we want to store. An example - someone suggests app X for the list, we decide no we don't want to display it. Later, in the forum, someone using app X from some other source is in trouble. Wouldn't we want to have a way to contact the developer? Maybe not, but it's worth thinking about.
The Solid Process lays down a good framework for describing the roles in the Solid Community but is lacking some key concepts especially in the areas of outreach to other organizations. Here's a very preliminary possible reorganization. We can address the separate question of ontologies to represent this later.
What role do they play in the Solid Community?
| Role | Description | Subclasses |
|---|---|---|
| Contributors | build the Solid specifications, core software, and community | Panels, Research Labs, Teams (DEI-Team,SolidOS) |
| Providers | provide services and resources for Solid users | Developers, Pod Providers, ID Providers, Trainers |
| Stakeholders | use Solid to meet their needs and the needs of their communities | Individuals, Non-Profit Orgs, Public Orgs, Enterprises |
| Allies | work on related projects | Decentralization, Privacy, Semantic Data, Identity, Policy-Legal. DEI |
| Facilitators | manage the Solid Project | Administrators, Editors, Creators, DEI-chairs, System Operators |
What action might the Solid Project take towards them?
| Recruit | draw people and projects into the Solid community |
| Onboard | provide targeted onboarding materials or site pathways for a person or group |
| Place | facilitate placement of people in Solid teams, jobs and volunteer opportunities |
An example : an academic department might be one or more of
| Role | Subclass | Example | Action |
|---|---|---|---|
| Contributor | Research Lab | a team working on Solid | Place |
| Provider | Pod Provider | pods for students and faculty | Place, OnBoard |
| Stakeholder | Non-profit Oranization | using Solid for administration | Place, OnBoard |
| Ally | Related Privacy Project | a team working on privacy | Recruit |
@jeff-zucker Is this the same as #248 or am I missing something?
@poef / @sjoerdvangroning Wasn't this something you guys were talking about recently?
@Potherca - There are three parts. 1) physically moving the site to a pod. It might be the same HTML or something generated differently. 2) Decide on ontologies and predicates for creating RDF data for everything on solidproject.org 3) Develop a system to generate a new site from RDF data. This first point is issue #248, the second two points are this issue.
Thank you for the clarification! At Muze (the parent company behind a part of PDS Interop) we're thinking about hosting websites from Solid Pods.
In the flow of replacing the Markdown -> Jekyl -> Website workflow with an RDF -> Something -> Website workflow we're thinking hard about the "something" step, as well as point 1) of getting the site to a pod.
If a proof-of-concept is in the making, we'd be very interest, especially @poef as he's currently also working on a PoC (I think).
This should really be a discussion rather than an issue. I've moved it here : https://github.com/solid/solidproject.org/discussions/783. Closing this issue.