Basic Definitions for Solid-OIDC Providers

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 🥳

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.