Again, it can be said that Clique Space defines the self. This "selfness" quality is asserted primarily through an Account.
Clique Space Accounts are used to express the individual operator behind adaptations of the how the user wishes to represent themselves to others; collections of Client Device Connections and role-based Affiliations. A connection is the first access level to a Client Device in a Clique Space. Such a Client Device may activate itself, or may be activated by another Client Device which is a Participant, and has the ability to activate such a Client Device through a Client Device which is registered in a Clique as a Participant with the Clique Space Owner. Usually such a Active Affiliation will be granted through authorisation from an Active Affiliation of a Clique Space administrator Client Device that is being used by the same Account (denoting the same operator) as that to which the access is being granted.
Clique Space, per se, is useless. Any Clique Space only becomes useful when it can model the interactions over different media as described in its Media Profile hierarchy. The more comprehensive this hierarchy, the more devices can be modelled, and hence, the more useful a Clique Space can potentially be either to those who choose to connect directly to it, or to those who choose to participate in Cliques that span their own Clique Space and the specific Clique Space in question. Connections associate an Account with a Media Profile, and one Connection represents one particular Client Device instance in Clique Space.
Affiliations are defined by associating a particular Account to (at least one, but possibly more) Account Profiles. Account Profiles are primarily the way by which privacy settings for a particular Account can be Asserted. An Account Profile hierarchy can define, for instance, a business hierarchy. Instances of Affiliations can be (depending on the permission settings - expressed through Limiting Constraints - of the Account Profile to which a particular Affiliation may associate) freely assigned to different Connections through the process known as Client Device activation. Each Active Affiliation is the apex of the set of six elements just described: Active Affiliation, Connection, Affiliation, Media Profile, Account, and Account Profile. These six elements aggregate a collection of Limiting Constraints.
Activation is the second access level; it is an association between a particular Connection and a particular Affiliation, and is itself, represented with an Active Affiliation. A Client Device that holds an Active Affiliation can, depending on the compatibility between Limiting Constraints between the two Client Device stacks, participate in Clique Space with other Client Devices which are likewise active.
Participants are the seventh element of the Client Device stack and are the third and final access level to a Client Device. Participants represent a Client Device's membership of a particular Clique; a group of collaborating Client Devices which are being modelled. The Clique's media is a collection of Enabling Constraints (parameters through which Limiting Constraints can shape) shared by all Client Devices. The media is determined by one of the Participants known as the Clique Owner.
A UML diagram is so much more compact.
I continue to see that this page gets a lot of hits. If people like this page so much, then maybe they should get back to me, and I might supply them with a UML diagram.
ReplyDeleteThis page still accurately describes the implementation in its current state. However, the Active Affiliation has been renamed to Identity because the Active Affiliation looks and quacks like an Identity, and the Account has been renamed the Axle because this term was a better description of the Element's purpose.
ReplyDelete