http://ods-qa.openlinksw.com:8896/sparql?query=define%20sql%3Adescribe-mode%20%22CBD%22%20%20DESCRIBE%20%3Chttp%3A%2F%2Fods-qa.openlinksw.com%3A8896%2Fproxy-iri%2F376191290f929269bd68a6a511bbd7bf918a5e96%3E&output=application%2Fatom%2Bxml2024-03-28T10:14:02.594452ZOData Service and Descriptor Documenthttp://ods-qa.openlinksw.com:8896/proxy-iri/376191290f929269bd68a6a511bbd7bf918a5e962024-03-28T10:14:02.594452Z
Usually, when I go to some sort of web-application provider, I
must create a login/account with them and register to user their
paid services.
But with Solid we expect users to authenticate with thier WebId,
meaning users already have an account elsewhere - do we then want
them to create yet another account for the specific
web-application? Potentially meaning they need to login twice to
access the service?
It seems to me that there should be an easy-to-use standard
Solid way of linking accounts, such that the web-app service
provider can detect a new login from a WebId, inform the user
immediately that they are newcomers to the service and would they,
please, fill-out the payment details (or select the free plan),
fetch as much information as possible from the WebId profile, and
then automatically link the WebId account with their own
automatically generated account.
Maybe this is all well-known, but perhaps it was worth having
this kind of workflow well defined in the Solid “best practice”
documentation.
Embedded HTML5 Microdata Statement 13