Getting VCs is now possible for other Pods than Vera and Koos. Upon login, the page will show the information which was collected from the public info (vcard) from the Solid Pod. A check is performed to see if the person is known in the mock overheid service (MOS). If this is not the case, a button appears ("Data klaarzetten"), which sends the vcard info to the MOS. This data will be used to create entries in the BRP and BRK.
As filling in profile info is optional in Solid, missing info will be complemented with fake data. This way, we can issue VCs for every logged in WebId.
Note: it is not still possible the complete the demo with an account other than Vera, as it is not possible to dynamically create a koopovereenkomst. This will be added in a later PR.
Note 2: there is no database for the MOS, all data is in-memory. This means that after restarting the backend all BRP and BRK data is lost (except for Vera and Koos, which are hardcoded). This means that a later "Data Klaarzetten" might yield different contents in the VCs.
Figure 1: Public profile info for Verkoper Vera
Figure 2: Public profile info for some Solid Community Pod
Figure 3: Public profile info for a new Pod containing no public info
Figure 4: VC containing fake data for the Pod creating in figure 3.
Getting VCs is now possible for other Pods than Vera and Koos. Upon login, the page will show the information which was collected from the public info (vcard) from the Solid Pod. A check is performed to see if the person is known in the mock overheid service (MOS). If this is not the case, a button appears ("Data klaarzetten"), which sends the vcard info to the MOS. This data will be used to create entries in the BRP and BRK.
As filling in profile info is optional in Solid, missing info will be complemented with fake data. This way, we can issue VCs for every logged in WebId.
Note: it is not still possible the complete the demo with an account other than Vera, as it is not possible to dynamically create a koopovereenkomst. This will be added in a later PR.
Note 2: there is no database for the MOS, all data is in-memory. This means that after restarting the backend all BRP and BRK data is lost (except for Vera and Koos, which are hardcoded). This means that a later "Data Klaarzetten" might yield different contents in the VCs.
Figure 1: Public profile info for Verkoper Vera
Figure 2: Public profile info for some Solid Community Pod
Figure 3: Public profile info for a new Pod containing no public info
Figure 4: VC containing fake data for the Pod creating in figure 3.