EPER: Efficient Parallel Encoding Rules for ASN.1

ions that do not fully grasp the underlying dynamics often create artif “exceptions,” that is, certain cases do not fit smoothly into the framework. The notio a “role” of a person is one example of such an exception, which arises from the fac subjecthood is treated as ontologically prior to the interaction by which it might o come into being. “Roles” are then invented to try to fix this problem by discretizing jecthood. Subject-Object Conceptualizations Having laid out the Lampson matrix, text books would then usually note that this g matrix is impractical to implement directly, and that there are two ways of realizing abstract formulation, which correspond to the two fundamental conceptualizations have been investigated in much detail over the past 25 years: 1. (by column) Object-Centered Realization: For each object, specify which subject have which access rights to it. 2. (by row) Subject-Centered Realization: For each subject, specify which objects can access with which rights. Subject-Subject Conceptualization Shifting to a communication model and making explicit the fact that rights are alw granted by owners of objects, we see that a third logical possibility for realizing Lampson matrix is along the lines of the relationships between the owner of an o and the holder of a right about this object (cf. Figure 9): 3. (by rights relationship) Relationship-Centered Realization: For each relationship between object owners and interested users (“licensees”), specify which rights party holds about the objects covered by this relationship. In other words, we introduce an explicit third entity, a relationship object, as show Figure 9. In the object-centered (ACLs) approach, there are three control objects; subject-centered (capabilities) approach, we get three control objects; and in the tionship-centered (commpacts) approach, we have two control objects in this exa (one for each relationship). 1 So far we have only considered the abstract organizations of control information objects; we have not yet examined the orthogonal question where to place such o 1. The example happens to create fewer objects for the relationship-based realization of this typically sparse matrix than for the other ones. We do not wish to claim that this is necessarily a general property of this realization though. In general, the relationship-based form will have a smaller number of control objects if a lot of objects are governed by a few relationships. A Network-Centric Design for Relationship-Based Rights Management 29 A Network-Centric Architecture for Managing Control Information