Comitting after merge; cleaned up bibliography.

doc/paper3/LLADD.bib

@@ -65,7 +65,7 @@
 @inproceedings{ejbCritique,
   author    = {Raul Silaghi and Alfred Strohmeier},
   title     = {Critical Evaluation of the {EJB} Transaction Model},
-  booktitle = {Proceedings of FIDJI},
+  booktitle = {FIDJI},
   year      = {2002},
   pages     = {15-28},
   OPTee        = {http://link.springer.de/link/service/series/0558/bibs/2604/26040015.htm},
@@ -79,7 +79,7 @@
                Alexander B. Romanovsky},
   title     = {Open Multithreaded Transactions: Keeping Threads and Exceptions
                under Control.},
-  booktitle = {Proceedings of  WORDS},
+  booktitle = {WORDS},
   year      = {2001},
   pages     = {197-205},
   OPTee        = {http://doi.ieeecomputersociety.org/10.1109/WORDS.2001.945131},
@@ -113,7 +113,7 @@
   title = 	 {Open Nested Transactions: Semantics and Support},
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings of WMPI},
+  booktitle = {WMPI},
   OPTpages = 	 {},
   year = 	 {2006},
   OPTeditor = 	 {},
@@ -131,11 +131,11 @@
 @inproceedings{SNS,
     author = "Armando Fox and Steven D. Gribble and Yatin Chawathe and Eric A. Brewer and Paul Gauthier",
     title = "Cluster-Based Scalable Network Services",
-    booktitle = "Symposium on Operating Systems Principles",
+    booktitle = "SOSP",
     pages = "78--91",
     year = "1997"}
 
-@misc{ bent04explicit,
+@comment{ bent04explicit,
   author = "J. Bent and D. Thain and A. Arpaci-Dusseau and R. Arpaci-Dusseau",
   title = "Explicit control in a batch-aware distributed file system",
   text = "J. Bent, D. Thain, A. Arpaci-Dusseau, and R. Arpaci-Dusseau. Explicit control
@@ -150,7 +150,7 @@
   title = 	 {Map{R}educe: Simplified Data Processing on Large Clusters},
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings of OSDI},
+  booktitle = {OSDI},
   OPTpages = 	 {},
   year = 	 {2004},
   OPTeditor = 	 {},
@@ -227,7 +227,7 @@
   title = 	 {Conceptual-to-internal mappings in commercial database systems},
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings of the 3rd SIGACT-SIGMOD symposium on Principles of database systems},
+  booktitle = {PODS},
   pages = 	 {70-78},
   year = 	 {1984},
   OPTeditor = 	 {},
@@ -245,7 +245,7 @@
 @InProceedings{streaming,
   author = "S. Chandrasekaran and M. Franklin",
   title = "Streaming Queries over Streaming Data",
-  booktitle = {Proc. of VLDB},
+  booktitle = {VLDB},
   year = "2002"
 }
 
@@ -254,7 +254,7 @@
   title = 	 {An Array-Based Algorithm for Simultaneous Multidimensional Aggregates},
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings of SIGMOD},
+  booktitle = {SIGMOD},
   pages = 	 {159-170},
   year = 	 {1997},
   OPTeditor = 	 {},
@@ -353,7 +353,7 @@
   title = 	 {The Architecture of the {EXODUS} Extensible {DBMS}},
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings on the 1986 international workshop on Object-oriented database systems},
+  booktitle = {OODS},
   pages = 	 {52-65},
   year = 	 {1986},
   OPTeditor = 	 {},
@@ -410,12 +410,49 @@
 
 
 
+@Manual{vms,
+  title = 	 {OpenVMS Record Management Services Reference Manual},
+  key = 	 {OpenVMS},
+  OPTauthor = 	 {},
+  OPTorganization = {},
+  OPTaddress = 	 {},
+  OPTedition = 	 {},
+  month = 	 {June},
+  year = 	 {2002},
+  OPTnote = 	 {},
+  OPTannote = 	 {}
+}
+
+@inproceedings{oneSizeFitsAll,
+  author    = {Michael Stonebraker and
+               Ugur \c{C}etintemel},
+  title     = {"{One} Size Fits All": An Idea Whose Time Has Come and Gone},
+  booktitle = {ICDE},
+  year      = {2005},
+  pages     = {2-11},
+  ee        = {http://doi.ieeecomputersociety.org/10.1109/ICDE.2005.1},
+  OPTcrossref  = {DBLP:conf/icde/2005},
+  bibsource = {DBLP, http://dblp.uni-trier.de}
+}
+
+@comment{DBLP:conf/icde/2005,
+  title     = {Proceedings of the 21st International Conference on Data
+               Engineering, ICDE 2005, 5-8 April 2005, Tokyo, Japan},
+  booktitle = {ICDE},
+  OPTpublisher = {IEEE Computer Society},
+  year      = {2005},
+  isbn      = {0-7695-2285-8},
+  bibsource = {DBLP, http://dblp.uni-trier.de}
+}
+
+
+
 @inproceedings{newDBtypes,
   author    = {Michael Stonebraker},
   title     = {Inclusion of New Types in Relational Data Base Systems},
-  booktitle = {Proceedings of the Second International Conference on Data Engineering,
+  booktitle = {ICDE},
-               February 5-7, 1986, Los Angeles, California, USA},
+  OPTfoo    = {February 5-7, 1986, Los Angeles, California, USA},
-  publisher = {IEEE Computer Society},
+  OPTpublisher = {IEEE Computer Society},
   year      = {1986},
   isbn      = {0-8186-0655-X},
   pages     = {262--269}
@@ -498,7 +535,7 @@
   title = 	 {{LIBTP}: Portable, Modular Transactions for {UNIX}},
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings of the 1992 Usenix Conference},
+  booktitle = {Usenix},
   OPTpages = 	 {},
   year = 	 {1992},
   OPTeditor = 	 {},
@@ -574,7 +611,7 @@
   title = 	 {Rethinking Database System Architecture: Towards a Self-tuning RISC-style Database System},
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings of the 26th International Conference on Very Large Databases},
+  booktitle = {VLDB},
   OPTpages = 	 {},
   year = 	 {2000},
   OPTeditor = 	 {},
@@ -624,8 +661,7 @@
   OPTeditor    = {Peter Buneman and
                Sushil Jajodia},
   title     = {The {OO7} Benchmark},
-  booktitle = {Proceedings of the 1993 ACM SIGMOD International Conference on
+  booktitle = {SIGMOD International Conference on Management of Data},
-               Management of Data},
   OPTpublisher = {ACM Press},
   year      = {1993},
   pages     = {12-21},
@@ -638,7 +674,7 @@
   title = 	 {Linear Hashing: A New Tool for File and Table Addressing },
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings of the 6th Conference on Very Large Dabatases},
+  booktitle = {VLDB},
   pages = 	 {224-232},
   year = 	 {1980},
   OPTeditor = 	 {},
@@ -664,7 +700,7 @@
                Yahiko Kambayashi},
   title     = {Object and File Management in the {EXODUS} Extensible Database
                System},
-  booktitle = {VLDB'86 Twelfth International Conference on Very Large Data Bases},
+  booktitle = {VLDB},
   OPTfoo    = {       August 25-28, 1986, Kyoto, Japan, Proceedings},
   OPTpublisher = {Morgan Kaufmann},
   year      = {1986},
@@ -693,7 +729,7 @@
   title = 	 {The {G}oogle file system},
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings of the 19th ACM Symposium on Operating Systems Principles},
+  booktitle = {SOSP},
   pages = 	 {29-43},
   year = 	 {2003},
   OPTeditor = 	 {},
@@ -713,7 +749,7 @@
   author = 	 {Mendel Rosenblum and John K. Ousterhout},
   OPTcrossref =  {},
   OPTkey = 	 {},
-  booktitle = {Proceedings of the 13th ACM Symposium on Operating Systems Principles},
+  booktitle = {SOSP},
   OPTpages = 	 {},
   year = 	 {1992},
   OPTeditor = 	 {},
@@ -793,7 +829,7 @@
   author    = {Eugene J. Shekita and
                Michael J. Zwilling},
   title     = {Cricket: A Mapped, Persistent Object Store.},
-  booktitle = {Proceedings of POS},
+  booktitle = {POS},
   year      = {1990},
   pages     = {89-102},
   OPTee        = {db/conf/pos/ShekitaZ90.html},
@@ -807,9 +843,9 @@
                Jie-Bing Yu},
   title     = {Storage Reclamation and Reorganization in Client-Server Persistent
                Object Stores},
-  booktitle = {Proceedings of the Tenth International Conference on Data Engineering},
+  booktitle = {ICDE},
   OPTfoo =   {February 14-18, 1994, Houston, Texas, USA},
-  publisher = {IEEE Computer Society},
+  OPTpublisher = {IEEE Computer Society},
   year      = {1994},
   OPTisbn      = {0-8186-5400-7},
   pages     = {120-131},

doc/paper3/LLADD.tex

@@ -258,7 +258,14 @@ support long-running, read-only aggregation queries (OLAP) over high-dimensional
 array format would be more appropriate~\cite{OLAP,molap}.  Although both
 OLTP and OLAP databases are based upon the relational model they make
 use of different physical models in order to serve
-different classes of applications efficiently.
+different classes of applications efficiently.  
+
+Streaming databases have the opposite problem; a set of relatively
+straightfoward primitives apply to many streaming data systems, but
+current conceptual mappings do not generalize across
+applications.  The authors of StreamBase argue that ``one size fits
+all'' interfaces are inappropriate for today's
+diverse applications~\cite{oneSizeFitsAll}.
 
 A basic claim of this paper is that no known physical data model can
 efficiently support the wide range of conceptual mappings that are in
@@ -270,12 +277,12 @@ DBMSs no longer works~\cite{OneSize}.
 
 Instead of attempting to create such a unified model after decades of
 database research has failed to produce one, we opt to provide a
-bottom-up transactional toolbox that supports many different models
+bottom-up transactional toolbox that supports many models
-efficiently.  This makes it easy for system designers to implement
+efficiently.  This makes it easy for system designers to
-most of the data models that the underlying hardware can support, or
+implement most data models that the underlying hardware can
-to abandon the database approach entirely, and forgo a top-down model.
+support, or to abandon the database approach entirely, and forgo 
-
+%structured physical models and abstract conceptual mappings.
-
+a top down model.
 
 \subsection{The Systems View}
 \label{sec:systems}
@@ -735,7 +742,8 @@ managers that \yads allocation routines use.  Applications that want
 conventional transactional isolation (serializability) can make 
 use of a lock manager.  Alternatively, applications may follow 
 the example of \yads default data structures, and implement 
-deadlock prevention, or other custom lock management schemes.\rcs{Citations here? Hybrid atomicity, optimistic/pessimistic concurrency control, something that leverages application semantics?}
+deadlock prevention, or other custom lock management 
+schemes~\cite{hybridAtomicity, optimisticConcurrencyControl}.
 
 Note that locking schemes may be
 layered as long as no legal sequence of calls to the lower level
@@ -769,17 +777,16 @@ Note that both lock managers have implementations that are tied to the
 code they service, both implement deadlock avoidance, and both are
 transparent to higher layers.  General-purpose database lock managers
 provide none of these features, supporting the idea that
-special-purpose lock managers are a useful abstraction.\rcs{This would
+special-purpose lock managers are a useful abstraction.  Locking
-be a good place to cite Bill and others on higher-level locking
+schemes that interact well with object oriented programming
-protocols}
+schemes~\cite{billOOlockingProtocols} and exception
+handling~\cite{omtt} extend these ideas to larger systems.
 
 Although custom locking is important for flexiblity, it is largely
 orthogonal to the concepts described in this paper.  We make no
 assumptions regarding lock managers being used by higher-level code in
 the remainder of this discussion.
 
-
-
 \section{LSN-free Pages}
 \label{sec:lsn-free}
 
@@ -1449,7 +1456,7 @@ not naturally structured in terms of queries over sets.
 \subsubsection{Modular databases}
 
 \eab{shorten and combine with one size fits all}
-
+\rcs{already worked one size fits all in above; merge them, and place here?}
 The database community is also aware of this gap.  A recent
 survey~\cite{riscDB} enumerates problems that plague users of
 state-of-the-art database systems, and finds that database
@@ -1634,7 +1641,7 @@ layout that we believe \yad could eventually support.
 Some large object storage systems allow arbitrary insertion and deletion of bytes~\cite{esm}
 within the object, while typical file systems
 provide append-only allocation~\cite{ffs}.
-Record-oriented allocation, including Multics' segments~\cite{multics}\rcs{remove multics comment?} and GFS~\cite{gfs}, is an alternative.
+Record-oriented allocation, such as in VMS Record Managment Services~\cite{vms} and GFS~\cite{gfs}, is an alternative.
 Write-optimized file systems lay files out in the order they
 were written rather than in logically sequential order~\cite{lfs}.  
 
@@ -1746,7 +1753,7 @@ Additional information, and \yads source code is available at:
 {\footnotesize \bibliographystyle{acm}
 
 \rcs{Check the nocite * for un-referenced references.}
-
+\rcs{What's ``SIGMOD International Conference on Management of Data'' vs ``SIGMOD Record''?}
 \nocite{*}
 \bibliography{LLADD}}