Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
PDS 2.0
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
The Personal Data Store itself as well as PDS client libraries that can be used to access it are shown in blue in the diagram below. Access to the PDS requires that the PDS client first get an access token from the Authentication Service 2.0 shown to the left of the PDS.
.png)
The Personal Data Store is a web service that stores personal data on behalf of an individual. In the long run it will also contain both a UMA Authorization Manager (AM) as shown above, however the first versions will not contain an AM. The non-AM part of the PDS is a variant of the IdAS Proxy Service, with the following changes:
- The UDI Resolver is configured to support sync:// UDIs.
- The IdAS Registry is configured to include the RDF2 Context Provider.
The Personal Data Store provides a user with an arbitrary number of personal Contexts adhering to the Higgins Context Data Model, which can be used for storing arbitrary (identity) data. UDIs can be used for representing "links" between Contexts, both inside the Personal Data Store and to external data sources.
The Personal Data Store can be accessed by sending XDI messages to its endpoint. The following Higgins components facilitate this task:
- Org.eclipse.higgins.idas.client (Java IdAS Client)
- Org.eclipse.higgins.idasclient.cpp.core (C++ IdAS Client)
We are working on packaging the above as well as additional components into the PDS Client shown in the diagram above.