{'fraction_non_alphanumeric': 0.026530612244897958, 'fraction_numerical': 0.0, 'mean_word_length': 5.628378378378378, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Proteus: Objectifying the DBMS User Interface

Our thesis it that the external representation of all components of a database system should be under programmer control: objects, schemes, commands, even the representation specifications themselves. Here we give the rationale and design for the PROTEUS interface system that sits atop an object-oriented DBMS. After introducing the model, TEDM, for the DBMS, we describe the classes of objects that model components of the database of interest to PROTEUS: type definitions, representation definitions, layouts, commands, and representation mappings. The advantage of “objectifying” everything is three-fold: the database itself can manage all the information of interest to PROTEUS, representations can be changed via database updates, and the representation mappings themselves can be expressed as database commands or rules. We conclude by showing how the pieces fit together, and outline some of our current research directions.