Rename 'Server' to something more specific 'Resource Server' or 'Storage Server' or ...
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
The current product class Server doesn't really specify what role the server plays. Solid relies on more than one type of server:
- Solid-OIDC Provider (Solid-OIDC)
- Authorization Server (Solid-OIDC & #504)
- Subscription Server (Solid Notifications)
- Notifications Sender (Solid Notifications)
As well as drafts not included in Solid Protocol v0.11
- Authorization Agent (SAI)
- WebID Provider <-- some deployments run it as a separate service and there are ongoing discussions in WebID-Profile panel
I think the closest matching term for the Server defined in the Solid Protocol would be Resource Server. It is also already used in Solid Notifications and well established by the OAuth community.
My next choice would be Storage Server since hosting solid storage is its primary (only?) responsibility.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the product class “Server” is defined in the Solid Protocol and compare it with the roles listed in Solid-OIDC, Solid Notifications, and issue #504. Evaluate the proposed terms “Resource Server” and “Storage Server” against those roles; done means the specification adopts a clearly agreed, more specific name.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100