Basic Definitions for Solid-OIDC Providers
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- authentication, documentation
Research direction
Start by reading the Solid-OIDC specification and the Solid-OIDC WebID document context described in the issue. Review the existing discussion before proposing a decision on which basic-information predicates belong in the standard; done means the intended predicates and their normative SHOULD or MUST requirements are agreed and documented.
Written by the indexing model from the issue text.
Description
Hi everyone!
- TL;DR: Suggestion to add a SHOULD or MUST in the spec for declaring basic information like the label or icon of a Solid-OIDC.
After a very interesting and productive conversation with @elf-pavlik about retrieving basic information like a Solid-OIDC provider's label and icon based on a WebID, I've found that there is no standard for our providers to declare this basic information.
I would like to suggest the addition to a few but standard and useful predicates to a Solid-OIDC WebID document, such as: label, description, icon, and those that you think would be valuable.
These labels and icons could be used in our applications' user interfaces to improve user experience in many scenarios such as:
- Choosing the Solid-OIDC provider for Login/Registration
- Rendering information about Solid-OIDC providers programatically, reducing the need for manual information retrieval
- & more
We'd love to know what you think 🤓
In the meantime thanks and cheers 🥳
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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/solid-oidc
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
solid/solid-oidc#258 ·
-
doc: solid-oidc-primer editorial
Difficulty 1/5 Under an hour Newbie friendliness 75/100
solid/solid-oidc#144 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
solid/solid-oidc#238 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
solid/solid-oidc#237 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
solid/solid-oidc#231 · 1 comment ·
All issues in solid/solid-oidc
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AXERA-TECH/ax-llm#75 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security impact:ux-friction issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100