The use.id platform contains functionality that is not part of the Solid standard and is thus proprietary/closed functionality. In addition, the use.id platform also implements fixes to support requirements that are currenlty not supported because the corresponding parts of the Solid specification meeting those requirements are still in flux.
Each time such functionality will be used in these guides, it will be clearly indicated by the following boxes:
Functionality of use.id that is complementary to Solid
Functionality so companies can use Solid to build apps, easily sync data from Solid pods, .... For example, use.id provides API endpoints so developers can reduce friction when onboarding new users.
Whenever such functionality is used in the tutorials, it will be indicated by a grey box with a padlock icon.
Fixes awaiting finalisation of the Solid spec
Some parts of the Solid specification are still under construction. However, some of these parts are essential to use the Solid standard in production environments (e.g. currently, Solid has no final rules on how applications should ask users for access to specific data attributes). use.id created propriatery endpoints to temporarily support such functionality. When the parts of the Solid spec pertaining to this functionality are finalised, these endpoints will be deprecated. Legacy users will remain supported.
Whenever such functionality is used in the tutorials, it will be indicated by an orange box with an under construction icon.
Updated 4 months ago