On 2 February 2010 11:13, Owen Thomas <owen.paul.thomas@gmail.com> wrote:

IoS model foresees ability to be your own identity and personal data
storage provider, even to the point of running the PDS on your phone.
That being said, it should still be noted that for majority of people
a network side hosted PDS may be easier.

In that case, a PDS sounds mildly similar to a Clique Space's Agent Device.

[...]

How does the term Agent Device PDS sound to you?

I've had time to read over IoS and TAS3. What I'm about to suggest appears a little too obvious to me, but basically showcases how Clique Space can be integrated with a PDS.

This is a hypothetical situation.

An individual's PDS is Connected to Clique Space using the individual's Account through a Media Profile named DeviceActivityLogger. Clique Space will capture the Client Device activity of any Client Device connected under the same Account, and this activity will be persisted in the PDS. Obviously, persisting PDS device activity concerning the storage of Client Device activity to the PDS would be suppressed because this would generate an infinite loop.

In the public Clique Space, this suppression would be a Limiting Constraint applied to the Account Profile "Self", which is the topmost accessible Account Profile in the hierarchy for any Account except for those Accounts that possess and Affiliation to the "CliqueSpaceAdministrator" Account Profile. This Limiting Constraint is associated to a corresponding Enabling Constraint for the DeviceActivityLogger.

  Owen.