Rename 'Server' to something more specific 'Resource Server' or 'Storage Server' or ...
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
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.
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.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 110
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
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.
More from solid/specification
-
new-work-item
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#806 · 11 comments · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#804 · 9 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
solid/specification#799 · 1 reaction ·
-
topic: resource access
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#797 · 4 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#788 · 4 comments · 1 reaction ·
All issues in solid/specification
Similar issues
-
area:dictation documentation P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
uttrflow/uttrflow-swift#1180 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
falcosecurity/falco-website#1601 ·
-
specification
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
WICG/webmonetization#729 ·