The articles in this directory relate to the LINCKS system.  All are
compressed with GNU's zip (gzip):

   * 	jss.ps.gz - 	a 17 page article.  The abstract reads:

	This paper discusses the development and management of
	object-oriented database applications using an approach where
	the user interface management is abstracted out from the
	underlying database, but nevertheless encapsulated in general
	purpose software --- a user interface management module. We
	identify a list of requirements that this application domain
	introduces and then present the LINCKS object-oriented database
	system and the UIMS which was designed to meet these
	requirements. After introducing the architecture of the system,
	we illustrate by means of an example how an application is
	built and executed. We finally discuss our approach and
	identify several features stemming from the specialization of
	the UIMS to the area of object-oriented databases. These
	features include multiple views of application objects and
	encapsulated runtime behavior on the task level. Our conclusion
	is that the design of specialized UIMS for different
	application domains is a valuable alternative to the maximally
	general UIMS approach.

   *	cscw.ps.gz - 	a 11 page article. The abstract reads:

   	This paper presents the object-centered database system LINCKS as a
   	platform for applications in Computer Supported Cooperative Work 
	(CSCW). LINCKS is an object-centered database management system 
	with extended support for multiple views, temporal data handling and 
	composite objects. Several features, such as the parallel editing 
	support, make sharing and reuse of objects and cooperation between 
	users  easy. The current main application interface to the database 
	is a document editing environement under X11 with a hypertext like 
	browser. 

   * 	www94.ps.gz -	a 11 page article. The abstract reads:

	We have created a prototype World Wide Web (WWW) front end to an
	OODBMS, LINCKS.  LINCKS is a multi user object store with support for
	composite objects, database histories, multiple views, information
	sharing by linking, and parallel editing notification.  The prototype
	generates HTML documents on the fly from information pieces in the
	database.  A document's logical structure is described by a simple
	grammar, as well as where in the database the different parts of the
	logical structure should be retrieved.  We can use LINCKS for tracking
	owner, source, and creation date of information pieces and documents.
	Instead of using ``copy-and-paste'' for information duplication, we
	are using links to the real source and thus maintain trace-ability.
	Moreover, by applying different views to the same document root object
	we are able to provide: abstract; table of contents (of different
	levels); a chapter, a section, or a subsection; the full article; with
	or without footnotes; or any combination of the above.  Using any of
	the current crops of server (CERN, NCSA, Plexus, etc) we must create
	several different files for each of these views.  These files must be
	created by hand or created by a program like LaTeX2HTML which makes it
	yet more difficult to maintain the documents.

   *    thoha92.ps.gz - a 67 page reports. The abstract reads:

	In this report we develop and implement a partially ordered
	command history for the multi-user LINCKS system. We examine
	two approaches of how to represent the temporal order in the command
	history (forward vs backward linking). The backward linking is chosen,
	because it results in a faster update of the command history and also
	contains the forward links indirectly. We define two types of
	commands: workspace commands and database commands. Workspace commands
	only affect objects in the workspace and database commands store or
	retrieve objects from the database. The different user sessions (LOGIN
	to LOGOUT) are grouped together in session objects. Temporal ordering
	between sessions exists as a temporal ordering between database
	commands of different sessions. This ordering is represented through
	backward links in the commands. A query function is implemented. The
	function takes two commands (A and B) and determines the temporal
	order between them.

   *	patla92.ps.gz - a 71 page licentiate thesis. The abstract reads:

	An important aspect of object oriented database systems is the
	ability to build up composite objects from object parts.  This
	allows modularity in the representation of objects and reuse of
	parts where appropriate.  It is also generally accepted that
	object-oriented database systems should be able to handle temporal 
	data.  However little theoretical work has been done on temporal 
	behavior of composite objects, and only relatively few systems attempt
	to incorporate both historical information and composite objects in 
	a multi-user environment.

	We argue that the support for handling temporal information 
	provided by other systems addresses only one of two important kinds 
	of historical information. We describe the notions of temporal history 
	and edit history.

	In this work we also make a first step in formalizing historical
	information of composite objects. We identify different kinds
	of compositions and give formal synchronization rules between
	a composition and its components to induce the desired behavior
	of these compositions in a database setting. We also discuss 
	the transitivity property for the part-of relation with respect
	to the newly defined compositions.

	Finally we address the problem of maintaining consistent historical
	information of a composition using the historical information of
	its components. This problem occurs as a result of sharing objects 
	between several compositions. We propose a solution and show
	an implementation in the LINCKS system.