PROBLEM TO BE SOLVED: To solve the problem, wherein it is impossible for an electronic content information provider to provide commercially secure and effective method, for a configurable general-purpose electronic commercial transaction/distribution control system. SOLUTION: In this system, having at least one protected processing environment for safely controlling at least one portion of decoding of digital information, a secure content distribution method comprises a process for encapsulating digital information in one or more digital containers; a process for encrypting at least a portion of digital information; a process for associating at least partially secure control information for managing interactions with encrypted digital information and/or digital container; a process for delivering one or more digital containers to a digital information user; and a process for using a protected processing environment, for safely controlling at least a portion of the decoding of the digital information. COPYRIGHT: (C)2006,JPO&NCIPI

https://apps.dtic.mil/dtic/tr/fulltext/u2/a423264.pdf

Systems and Methods for Secure Transaction Management and Electronic Rights Protection

With increasing size and complexity of the implementations of information systems, it is necessary to use some logical construct (or architecture) for defining and controlling the interfaces and the integration of all of the components of the system. This paper defines information systems architecture by creating a descriptive framework from disciplines quite independent of information systems, then by analogy specifies information systems architecture based upon the neutral, objective framework. Also, some preliminary conclusions about the implications of the resultant descriptive framework are drawn. The discussion is limited to architecture and does not include a strategic planning methodology.

A framework for information systems architecture

A federated database system (FDBS) is a collection of cooperating database systems that are autonomous and possibly heterogeneous. In this paper, we define a reference architecture for distributed database management systems from system and schema viewpoints and show how various FDBS architectures can be developed. We then define a methodology for developing one of the popular architectures of an FDBS. Finally, we discuss critical issues related to developing and operating an FDBS.

Federated database systems for managing distributed, heterogeneous, and autonomous databases

Data analysis applications typically aggregate data across many dimensions looking for unusual patterns. The SQL aggregate functions and the GROUP BY operator produce zero-dimensional or one-dimensional answers. Applications need the N-dimensional generalization of these operators. The paper defines that operator, called the data cube or simply cube. The cube operator generalizes the histogram, cross-tabulation, roll-up, drill-down, and sub-total constructs found in most report writers. The cube treats each of the N aggregation attributes as a dimension of N-space. The aggregate of a particular set of attribute values is a point in this space. The set of points forms an N-dimensionaI cube. Super-aggregates are computed by aggregating the N-cube to lower dimensional spaces. Aggregation points are represented by an "infinite value": ALL, so the point (ALL,ALL,...,ALL, sum(*)) represents the global sum of all items. Each ALL value actually represents the set of values contributing to that aggregation.

/pdf/data-cube-a-relational-aggregation-operator-generalizing-59vkepw6rd.pdf

Data cube: a relational aggregation operator generalizing GROUP-BY, CROSS-TAB, and SUB-TOTALS

In a high level query and data manipulation language such as SQL, requests are stated non-procedurally, without reference to access paths. This paper describes how System R chooses access paths for both simple (single relation) and complex queries (such as joins), given a user specification of desired data as a boolean expression of predicates. System R is an experimental database management system developed to carry out research on the relational model of data. System R was designed and built by members of the IBM San Jose Research Laboratory.

/pdf/access-path-selection-in-a-relational-database-management-24mjd6l5pv.pdf

Access path selection in a relational database management system

From the Publisher:
For over 25 years, C. J. Date's An Introduction to Database Systems has been the authoritative resource for readers interested in gaining insight into and understanding of the principles of database systems. This revision continues to provide a solid grounding in the foundations of database technology and to provide some ideas as to how the field is likely to develop in the future.. "Readers of this book will gain a strong working knowledge of the overall structure, concepts, and objectives of database systems and will become familiar with the theoretical principles underlying the construction of such systems.

An Introduction to Database Systems

A Guide to the SQL Standard

Read more and get great! That's what the book enPDFd relational database selected writings will give for every reader to read this book. This is an on-line book provided in this website. Even this book becomes a choice of someone to read, many in the world also loves it so much. As what we talk, when you read more every page of this relational database selected writings, what you will obtain is something great.

Relational Database: Selected Writings

From the Publisher:
Temporal database systems are systems that provide special support for storing, querying, and updating historical and/or future data. Current DBMSs provide essentially no temporal features at all, but this situation is likely to change soon for a variety of reasons; in fact, temporal databases are virtually certain to become important sooner rather than later, in the commercial world as well as in academia. This book provides an in-depth description of the foundations and principles on which those temporal DBMSs will be built. These foundations and principles are firmly rooted in the relational model of data; thus, they represent an evolutionary step, not a revolutionary one, and they will stand the test of time. 
This book is arranged in three parts and a set of appendixes: * Preliminaries: Provides a detailed review of the relational model, and an overview of the Tutorial D language.
* Laying the Foundations: Explains basic temporal data problems and introduces fundamental constructs and operators for addressing those problems.
* Building on the Foundations: Applies the material of the previous part to issues of temporal database design, temporal constraints, temporal query and update, and much more.
* Appendixes: Include annotated references and bibliography, implementation considerations, and other topics.
KEY FEATURES: * Describes a truly relational approach to the temporal data problem.
* Addresses implementation as well as model issues.
* Covers recent research on new database design techniques, a new normal form, new relational operators, new update operators, a new approach to the problem of granularity, support for cyclic pointtypes, and other matters.
* Includes review questions and exercises in every chapter.
* Suitable for both reference and tutorial purposes.

Temporal Data And The Relational Model

Preface. I. OVERVIEW. 1. What's the Problem? 2. Business Rules Are the Solution! 3. Presentation Rules. 4. Database and Application Rules. 5. The Data Model. 6. Potential Advantages. 7. Potential Disadvantages. 8. Summary of Part I. II. A RELATIONAL PERSPECTIVE. 9. Some Technical Preliminaries. 10. Views, Base Tables, and Stored Tables. 11. Integrity Constraints. 12. A Closer Look at Relational Databases. 13. What Relations Mean. 14. Business Rules and the Relational Model. 15. Summary of Part II. References and Bibliography. Index. 0201708507T04062001

C. J. Date

Papers

An Introduction to Database Systems

A Guide to the SQL Standard

Relational Database: Selected Writings

Temporal Data And The Relational Model

What not how : the business rules approach to application development