Are relative links in Solid-OIDC Client Identifier Document supported?

We recently ran into an situation where a client added some metadata to its Client ID Document, in particular a logo_uri. The value for this property was relative URL, which isn't something that is explicitly prevented by the specification, and can make sense in the context of a dereferencable Client ID.

The Client Metadata semantics in Solid-OIDC are aligned with the underlying OpenID Dynamic Client Registration specification, but in the context of that specification, relative URLs don't make sense, so this isn't called out.

In order to remain aligned with the underlying Client Metadata specification, the Solid-OIDC specification could add another requirement on the Client in its Client ID Document section, such as "URIs provided as values for parameters in the Client ID Document MUST be absolute".

The alternative would be to add a requirement on the OP conformance class to support relative URIs, but I think it moves away from the underlying specification and would potentially open up possibilities for more misalignments.

Start by reading the Solid-OIDC Client ID Document section and compare its URI requirements with the linked OpenID Dynamic Client Registration Client Metadata specification. Decide whether the specification should require absolute URIs or require relative-URI support, then update the relevant Solid-OIDC requirement and any affected conformance guidance.