Further considerations about the Agent Collaboration.

Many of the posts I put up on this blog are hypothetical deliberations about imminent or important complicated Clique Space(TM) implementation issues. Here's some of what I've been thinking...

The Agent Collaboration is a collaboration of one or more Agent Devices. Agent Collaborations are modelled by Cliques in the same way that a collaboration by any other set of devices are. A Clique Space Clique is a Clique that models an Agent Collaboration that is the manifestation of a Clique Space. Every Clique Space has a Clique Space Clique. Every Agent Device uses the Clique Space's Media Profile spine to generate all spinal Elements (Media Profile, Connection, Active Affiliation and Participant; or maybe in the future just the Media Profile, Connection and Participant) necessary to become Participants in a Clique Space's Clique.

Now, we can consider Agent Collaborations that represent Client Devices (of which the Agent Device is one) except the Agent Device.

First, a refresher on what Participants and Cliques are. In general, Participants represent each device/individual/role of each Client Device in the corresponding collaboration of the "real" device's medium. The device's medium is represented in Clique Space by the Clique's medium, which is decided firstly at Clique formation, and then perhaps at any appropriate time thereafter in the scope of the Clique's existence by the Clique Owner's Participant. So, for instance, a conference call of six people, three from one company, and three from another will be represented accordingly in a Clique of six participants; the Clique's Owner might also be the conference call's moderator.

Consider the Agent Collaboration underlying this Clique. For instance, all devices might actually be connected to the same Agent Device. Hence, all Client Devices, each of which correspond to a given device would be represented by a Participant (each of these Participants is the Owner of a bipartite serving Agent Device's Clique) that registers, as a spinal component, a Connection that lists the same Agent Device as the serving Agent Device. Hence, there would be no actual Agent Collaboration representing the Agent Collaboration's Clique - there would just be a Clique with two Participants representing the same Agent Device; the Owner and its twin.

Now consider a slight variation in the make-up of the Agent Device's Clique: perhaps four of the Participants from the conference call Clique are connected to one Agent Device, and the remaining two are each connected to other Agent Devices. There are a total of three Agent Devices siphoning and controlling the state of all devices of the conference call collaboration, and hence the Agent Collaboration's Clique has four Participants; three representing each connected Agent Device, and one representing the Agent Collaboration Clique Owner's twin.

But what if some device not involved in the conference call was controlled by someone who wanted to observe this conference call Clique? As they're not a Participant, they cannot get information about the Clique. If (which is most probably the case) they were a Participant in the conference call, but their phone does not possess a View, there would be no value in using Clique Space to record or control activity in this Clique.

To be valuable, Clique Space must allow a user the ability to view and persist the activity of any Clique to which they have sufficient Limiting Constraint affinity. To understand how this information is made available, one must remind one's self about the underlying Agent Collaboration, and how this collaboration, like any other device collaboration, can be modelled as a Clique.

The underlying Agent Collaboration can be modelled in a Clique that includes the participating Agent Devices as well as other non-participating Agent Devices. These extra "non-participating" Agent Devices would acquire Participants to the Agent Collaboration Clique when a connected Client Device had a View mechanism, and was connected by a user who may have had to activate an Affiliation with sufficient Limiting Constraint affinity to view a Clique in which they are not a member, and wants to observe and/or interact with this Clique in some way.

I have already developed an ideal candidate Media Profile spine for modelling this underlying Agent Collaboration's Clique: the Agent Device's Media Profile. Currently, this Media Profile generates Participants that appear in the serving Agent Device's Clique; a bipartite Clique. The other Participant in this serving Agent Device's Clique is the Client Device; it is the owner. I envisage every Client Device will create a serving Agent Device's Clique with the Agent Device to which it is connected. However only the administrator's Client Device creates these Cliques - because the administrator's Client Device is the only Client Device developed for Clique Space so far.

Agent Devices will collaborate in relation to a specific Clique. These multipartite Cliques might be best labelled after what they represent: Agent Collaboration Cliques. These Agent Collaboration Cliques contain Participants representing the Agent Devices to which are connected at least one View or persistence mechanism enabled Client Device which has expressed an interest in at least one View of the given Clique - either to observe, persist, or perhaps even to control the activity of the devices modelled as Participants within the given Clique. Hence, it appears that the Agent Device's Media Profile spine can generate Participants for a multipartite Clique function in which these Agent Device's Participants might be these Cliques' Owners.

I have earlier referred to Clique Spaces as a form of Agent Collaboration Clique. Usage of this term to only describe Clique Spaces appears too restrictive; a Clique Space is an Agent Collaboration which is centrally managed by a group of one or more users possessing an Affiliation to the Clique Space's administrator Account Profile. Clique Spaces themselves provide domains for Element and Clique life-cycle management, Clique ownership as well as user security and privacy etc. Other Agent Collaborations are more fluid; they form grow, shrink and disband in accordance with the capacity by which users can form and disband, join and leave, or cede ownership of Cliques. Hence, a Clique's Participants may reside on the same Clique Space, or different Clique Spaces where the given Clique Spaces allow - through mutual agreement which can be modelled by a Clique - other Cliques to span theses Clique Spaces.

Something else that becomes apparent with these Agent Collaboration Cliques. They appear to be recursive; maybe even, and perhaps nonsensically, circular. They may be recursive if one has a need to observe people who are observing people who are ... observing a Clique of a conference call: beautiful big bro. They may be circular if I'm watching you watching me (ah huh..), but I think this has about as much utility as a similarly named Abba song suggests.

We'll see...