10 citations found. Retrieving documents...
T. Lougenia Anderson, Earl F. Ecklund,Jr., and David Maier. PROTEUS: objectifying the DBMS user interface. In Intl. Workshop on Object-Oriented Database Systems, 1986.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Visualizing Queries and Querying Visualizations - Consens, Cruz, Mendelzon (1992)   (8 citations)  (Correct)

....as a graph, a hygraph, a bar chart, a temporal chart, etc. Querying and Transforming Visualizations In the previous subsection we expressed a query as a function mapping databases to visualizations; more generally, we can think of the visualizations themselves as part of the database (as in [AEM86], and use our visual language to query the visualizations and produce different visualizations as result. Figure 6 (i) shows a template in our visual language that transforms a graph to a temporal chart. A temporal chart consists of two or more parallel axes and a set of lines between these ....

T. Lougenia Anderson, Earl F. Ecklund,Jr., and David Maier. PROTEUS: objectifying the DBMS user interface. In Intl. Workshop on Object-Oriented Database Systems, 1986.


User-Defined Visual Languages for Querying Data - Cruz (1993)   (2 citations)  (Correct)

....from a database point of view, and stay within the bounds of the formal database field. doodle also differs from other query languages for object oriented databases (e.g. GSKZ85, Cru90, GPV90] in that the user defines how to visualize and query the data. A related approach is PROTEUS [AEM86]. However, there are important differences: In doodle, visualizations (mappings from data to pictures) are specified visually, and the query languages are user defined, while in PROTEUS visualizations are specified textually. PROTEUS is object oriented in the usual sense, while in doodle the ....

T. Lougenia Anderson, Earl F. Ecklund,Jr., and David Maier. PROTEUS: Objectifying the DBMS User Interface. In Intl. Workshop on Object-Oriented Database Systems, 1986.


Model, Language and Implementation Aspects of a Logic-Based.. - Zhu (1989)   (Correct)

....command, which essentially limits the kind of manipulations one can do with the stored commands, such as sharing of code and dynamic construction of commands. 1.4. TEDM Overview This section is an overview of TEDM, a data model designed and described in [Maier85] Other related documents are [Anderson86, 89, Ecklund87, Maier89, Ohkawa87, Zhu86, 88, 89]. Features from both object oriented methodology and logic methodology are integrated into the data model. Several other extensions are also made to enhance the model. In particular, it embeds such notions as object identities, object classifications and structural inheritance, from ....

....creating objects, a language for defining types, a language for querying and manipulating existing data, and a language for deducing information. We anticipate that other languages would be added in the future. For example, a language for display format specification for objects, as proposed in [Anderson86, Flynn88]. But as we pointed out, the language for object definition (creation) will subsume the capabilities of the other languages combined. In other words, although on the surface we provide different languages to describe different categories of database objects, only the object definition language is ....

Anderson, T. L., Ecklund, E. F. Jr. and Maier D., "PROTEUS: Objectifying the DBMS User Interface," Proceedings of the International Workshop on Object-Oriented Database Systems, 1986.


User-Defined Visual Query Languages - Cruz (1994)   (2 citations)  (Correct)

....point of view, and both visualizations and transformations perform database queries visually. doodle also differs from other query languages for databases (e.g. SNAP [2] ISIS [8] G [3] GOOD [10] in that the user defines the pictures to query the data. The closest approach is PROTEUS [1]. However, there are important differences: In doodle, visualizations and transformations are specified visually by the user, and database queries are visual. In PROTEUS visualizations are specified textually, and the query language is also textual. PROTEUS is object oriented in the usual sense, ....

T. Lougenia Anderson, Earl F. Ecklund,Jr., and David Maier. PROTEUS: Objectifying the DBMS User Interface. In Intl. Workshop on Object-Oriented Database Systems, 1986.


Creating and Filtering Structural Data Visualizations using.. - Consens (1994)   (8 citations)  (Correct)

....The third column describes the processing of the graphic data to obtain an image. Several systems dealing with the problem of presenting data and their relationships to users have been developed recently in the database and user interface communities (e.g. BOS91, Dea91, Row92, KN92] Proteus [AEM86] Humanoid [Sze90, SLN93] ODDS [FM92] and ACE[JNZM93, NZ93] are representative of model based interface tools. These systems support constructing a declarative model of how the interface should look and behave. This model is constructed by describing how the components (widgets) that represent ....

T. Lougenia Anderson, Earl F. Ecklund,Jr., and David Maier. PROTEUS: Objectifying the DBMS User Interface. In Intl. Workshop on Object-Oriented Database Systems, 1986.


PESTO: An Integrated Query/Browser for Object Databases - Carey, Haas, Maganty.. (1996)   (5 citations)  (Correct)

.... whose focus is on tools for building graphical database interfaces; these include FaceKit, Freeform, and DBFace [King87, King89, King92] Other related efforts include GOOD [Gyss90] which suggested an interesting set of graphical primitives and operations for object data, the work on Proteus [Ande86], and O2Look and ToonMaker from O2 [Borr92] Finally, there has also been recent work on novel ways of viewing data, e.g. DOODLE [Cruz92] and InfoCrystal [Spoe93] While interesting, these papers are of less direct relevance to PESTO. 2.3 What s New About PESTO There are two key differences ....

L. Anderson, E. Ecklund, and D. Maier, "Proteus: Objectifying the DBMS User Interface," Proc. Int'l. Workshop on Object-Oriented Databse Sys., Sept. 1986.


CLASSIC: A Structural Data Model for Objects - Borgida, Brachman, McGuinness, .. (1989)   (205 citations)  (Correct)

.... not, by using the ind aspect operator, which behaves similarly to concept aspect but in addition recognizes the invocations ind aspect[ ind , FILLS, role ] and ind aspect[ ind , CLOSE, role ] We plan to develop a morepowerfuland integrated query language, possibly based on the notation used in [ 5 ] . 3.5.3 Queries about class membership An arbitrary concept expression can be viewed as a query requesting information about all the individuals in the DB that satisfy it (i.e. individuals that are members of the class defined by the concept) Thus, PERSON asks for all individuals known to be ....

Anderson, T. L., Ecklund, E., and Maier, D. PROTEUS: Objectifying the DBMS user interface. In Dittrich, K., and Dayal, U., editors, Proc. 1986 International Workshop on Object-Oriented Database Systems, Asilomar, CA, 1986. IEEE Computer Society Press.


The POSTGRES Data Model - Rowe, Stonebraker (1987)   (67 citations)  (Correct)

....models that contain non first normal form relations [Bae86, Dae86, Dee86] The POSTGRES data model can be used to support non first normal form relations with procedure types. Consequently, POSTGRES seems to contain a superset of the capabilities of these proposals. Object oriented data models [Ane86, CoM84] have modeling constructs to deal with uncertain structure. For example, GemStone supports union types which can be used to represent subobjects that have different types [CoM84] Sharing of subobjects is represented by storing the subobjects as separate records and connecting them to a parent ....

T. Anderson and et. al., "PROTEUS: Objectifying the DBMS User Interface", Proc. Int. Wkshp on Object-Oriented Database Systems, Asilomar, CA, Sep. 1986.


A Shared Object Hierarchy - Rowe (1986)   (4 citations)  (Correct)

....cache in the application process so that subsequent references to the object will not require another database retrieval. Object updates by the application are propagated to the database and to other processes that have cached the object. Other research groups are also investigating this approach [AbW86, Ane86, KeS86, Mae87, Mey86, Ske86]. The main difference between our work and the work of these other groups is the object cache in the application process. They have not addressed the problem of maintaining cache consistency when more than one application process is using an object. Research groups that are addressing the object ....

T. Anderson and et. al., "PROTEUS: Objectifying the DBMS User Interface", Proc. Int. Wkshp on Object-Oriented Database Systems, Asilomar, CA, Sep. 1986.


[Hutchins86] E. Hutchins, J. Hollan, D. Norman, "Direct.. - User Centered (1992)   Self-citation (Maier)   (Correct)

No context found.

T.L. Anderson, E.F. Ecklund, Jr., and D. Maier, "PROTEUS: Objectifying the DBMS User Interface", Proceedings of the International Workshop on Object-Oriented Database Systems, ed. D. Dittrich and U. Dayal, Pacific Grove, California, September, 1986.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC