Access transparency    (2KEL)
A distribution transparency which masks differences in data representation and invocation mechanisms to enable inter-working between objects. ---> Key requirement needed to be addressed by DRM    (2KEN)
Failure transparency    (2KEP)
A distribution transparency which masks, from an object, the failure and possible recovery of other objects (or itself), to enable fault tolerance. ---> Out of Scope for DRM - Requirement on the Data Transfer Mechanism    (2KEQ)
Location transparency    (2KER)
A distribution transparency which masks the use of information about location in space when identifying and binding to interfaces. ---> Out of Scope for DRM - Requirement on the Data Transfer Mechanism    (2KES)
Migration transparency    (2KET)
A distribution transparency which masks, from an object, the ability of a system to change the location of that object. Migration is often used to achieve load balancing and reduce latency. ---> Out of Scope for DRM - Requirement on the Data Transfer Mechanism    (2KEU)
Relocation transparency    (2KEV)
A distribution transparency which masks relocation of an interface from other interfaces bound to it. ---> Out of Scope for DRM - Requirement on the Data Transfer Mechanism    (2KEW)
Replication transparency    (2KEX)
A distribution transparency which masks the use of a group of mutually behaviorally compatible objects to support an interface. Replication is often used to enhance performance and availability. ---> Out of Scope for DRM - Requirement on the Data Transfer Mechanism    (2KEY)
Persistence transparency    (2KEZ)
A distribution transparency which masks, from an object, the deactivation and reactivation of other objects (or itself). Deactivation and reactivation are often used to maintain the persistence of an object when a system is unable to provide it with processing, storage and communication functions continuously. ---> ?Out of Scope for DRM - Requirement on the Data Transfer Mechanism    (2KF0)
Transaction transparency    (2KF1)
A distribution transparency which masks coordination of activities amongst a configuration of objects to achieve consistency. ---> Out of Scope for DRM - Requirement on the Data Transfer Mechanism    (2KF2)
  1. E. Conclusion    (2KF3)
    • The main points of this review are that the DRM is not specific enough to be adopted – it generates more questions than it answers. Our recommendations are summarized below:    (2KF4)
      • Specify complete data structuring model;    (2KF5)
      • Provide specific model of parties, roles and information exchange;    (2KF6)
      • Consider collaboration as a 1st class construct for information exchange;    (2KF7)
      • Make the relationships between the DRM and the BRM specific;    (2KF8)
      • Consider PRISM and related standards for provenance;    (2KF9)
      • Consider Digital Rights Management;    (2KFA)
      • Specify explicit relationship between DRM and XSD;    (2KFB)
      • Consider ISO RM-ODP for policies;    (2KFC)
      • Investigate impact of Adobe XMP models on DRM adoption;    (2KFD)
      • Partition DRM into different areas of concern    (2KEO)