| { | |
| "paper_id": "H01-1039", | |
| "header": { | |
| "generated_with": "S2ORC 1.0.0", | |
| "date_generated": "2023-01-19T03:31:14.993693Z" | |
| }, | |
| "title": "Integrated Information Management: An Interactive, Extensible Architecture for Information Retrieval", | |
| "authors": [ | |
| { | |
| "first": "Eric", | |
| "middle": [], | |
| "last": "Nyberg", | |
| "suffix": "", | |
| "affiliation": { | |
| "laboratory": "", | |
| "institution": "Language Technologies Institute Carnegie Mellon University Pittsburgh", | |
| "location": { | |
| "postCode": "15213", | |
| "region": "PA" | |
| } | |
| }, | |
| "email": "" | |
| }, | |
| { | |
| "first": "Hal", | |
| "middle": [], | |
| "last": "Daume", | |
| "suffix": "", | |
| "affiliation": { | |
| "laboratory": "", | |
| "institution": "Carnegie Mellon University Pittsburgh", | |
| "location": { | |
| "postCode": "15213", | |
| "region": "PA" | |
| } | |
| }, | |
| "email": "" | |
| } | |
| ], | |
| "year": "", | |
| "venue": null, | |
| "identifiers": {}, | |
| "abstract": "", | |
| "pdf_parse": { | |
| "paper_id": "H01-1039", | |
| "_pdf_hash": "", | |
| "abstract": [], | |
| "body_text": [ | |
| { | |
| "text": "Most current IR research is focused on specific technologies, such as filtering, classification, entity extraction, question answering, etc. There is relatively little research on merging multiple technologies into sophisticated applications, due in part to the high cost of integrating independently-developed text processing modules.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": "1." | |
| }, | |
| { | |
| "text": "In this paper, we present the Integrated Information Management (IIM) architecture for component-based development of IR applications 1 . The IIM architecture is general enough to model different types of IR tasks, beyond indexing and retrieval. Rather than providing a single framework or toolkit, our goal is to create a higherlevel framework which is used to build a variety of different class libraries or toolkits for different problems. Another goal is to promote the educational use of IR software, from an \"exploratory programming\" perspective. For this reason, it is also important to provide a graphical interface for effective task visualization and realtime control.", | |
| "cite_spans": [ | |
| { | |
| "start": 134, | |
| "end": 135, | |
| "text": "1", | |
| "ref_id": "BIBREF0" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": "1." | |
| }, | |
| { | |
| "text": "Prior architecture-related work has focused on toolkits or class libraries for specific types of IR or NLP problems. Examples include the SMART system for indexing and retrieval [17] , the FIRE [18] and InfoGrid [15] class models for information retrieval applications, and the ATTICS [11] system for text categorization and machine learning. Some prior work has also focused on the user interface, notably FireWorks [9] and SketchTrieve [9] 2 . Other systems such as GATE [4] and Corelli [20] have centered on specific approaches to NLP applications.", | |
| "cite_spans": [ | |
| { | |
| "start": 178, | |
| "end": 182, | |
| "text": "[17]", | |
| "ref_id": "BIBREF16" | |
| }, | |
| { | |
| "start": 194, | |
| "end": 198, | |
| "text": "[18]", | |
| "ref_id": "BIBREF17" | |
| }, | |
| { | |
| "start": 212, | |
| "end": 216, | |
| "text": "[15]", | |
| "ref_id": "BIBREF14" | |
| }, | |
| { | |
| "start": 285, | |
| "end": 289, | |
| "text": "[11]", | |
| "ref_id": "BIBREF10" | |
| }, | |
| { | |
| "start": 417, | |
| "end": 420, | |
| "text": "[9]", | |
| "ref_id": "BIBREF8" | |
| }, | |
| { | |
| "start": 438, | |
| "end": 441, | |
| "text": "[9]", | |
| "ref_id": "BIBREF8" | |
| }, | |
| { | |
| "start": 473, | |
| "end": 476, | |
| "text": "[4]", | |
| "ref_id": "BIBREF3" | |
| }, | |
| { | |
| "start": 489, | |
| "end": 493, | |
| "text": "[20]", | |
| "ref_id": "BIBREF19" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": "1." | |
| }, | |
| { | |
| "text": "The Tipster II architecture working group summarized the requirements for an ideal IR architecture [6] , which include:", | |
| "cite_spans": [ | |
| { | |
| "start": 99, | |
| "end": 102, | |
| "text": "[6]", | |
| "ref_id": "BIBREF5" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": "1." | |
| }, | |
| { | |
| "text": "Standardization. Specify a standard set of functions and interfaces for information services. Evaluation. Isolate and test specific modules side-by-side in the same application.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": "1." | |
| }, | |
| { | |
| "text": "One of the visions of the Tipster II team was a \"marketplace of modules\", supporting mix-and-match of components developed at different locations. The goals of rapid deployment and flexibility require an excellent user interface, with support for drag-and-drop task modeling, real-time task visualization and control, and uniform component instrumentation for cross-evaluation. The modules themselves should be small, downloadable files which run on a variety of hardware and software platforms. This vision is in fact a specialized form of component-based software engineering (CBSE) [14] , where the re-use environment includes libraries of reusable IR components, and the integration process includes realtime configuration, control, and tuning. Section 2 summarizes the architectural design of IIM. Section 3 provides more detail regarding the system's current implementation in Java. In Section 5 we describe three different task libraries that have been constructed using IIM's generic modules. Current instrumentation, measurement, and results are presented in Section 6. We conclude in Section 7 with some relevant comparisons of IIM to related prior work.", | |
| "cite_spans": [ | |
| { | |
| "start": 585, | |
| "end": 589, | |
| "text": "[14]", | |
| "ref_id": "BIBREF13" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": "1." | |
| }, | |
| { | |
| "text": "IIM uses a flow-based (pipe and filter [16] ) processing model. Information processing steps are represented as nodes in a graph. Each edge in the graph represents a flow connection between a parent node and a child node; the documents produced by the parent node are passed to each child node. In IIM, the flow graph is referred to as a node chain. A sample node chain is shown in Figure 1 . The IIM class model includes six basic node types, which can be used to model a variety of IR problems:", | |
| "cite_spans": [ | |
| { | |
| "start": 39, | |
| "end": 43, | |
| "text": "[16]", | |
| "ref_id": "BIBREF15" | |
| } | |
| ], | |
| "ref_spans": [ | |
| { | |
| "start": 382, | |
| "end": 391, | |
| "text": "Figure 1", | |
| "ref_id": "FIGREF3" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "ARCHITECTURAL DESIGN", | |
| "sec_num": "2." | |
| }, | |
| { | |
| "text": "1. Source. Generates a document stream (from a static collection, web search, etc.) and passes documents one at a time to its child node(s).", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "ARCHITECTURAL DESIGN", | |
| "sec_num": "2." | |
| }, | |
| { | |
| "text": "Filter. Passes only documents which match the filter to its child node(s).", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "2.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Annotator. Adds additional information to the document regarding a particular region in the document body. The IIM class model is embedded in a Model-View-Controller architecture [5] , which allows the system to be run with or without the graphical interface. Pre-stored node chains can be executed directly from the shell, or as a background process, completely bypassing all user interaction when optimal performance is required. The Controller subsystem and interface event dispatching subsystem must run as separate threads to support dynamic update of parameters in a running system. The View (user interface) should support: a) plug-and-play creation of new node chains; b) support for saving, loading and importing new node chains; c) dynamic visualization of a task's status; and d) direct manipulation of a node's parameters at any time.", | |
| "cite_spans": [ | |
| { | |
| "start": 179, | |
| "end": 182, | |
| "text": "[5]", | |
| "ref_id": "BIBREF4" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "3.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "In addition to the nodes themselves, IIM supports two other important abstractions for IR task flows:", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "3.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Macro Nodes. Certain sequences of nodes are useful in more than one application, so it is convenient to store them together as a single reusable unit, or macro node. IIM allows the user to export a portion of a node chain as a macro node to be loaded into the Node Library and inserted into a new chain as a single node. The user may specify which of the properties of the original nodes are visible in the exported macro node (see Figure 3 ).", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 432, | |
| "end": 440, | |
| "text": "Figure 3", | |
| "ref_id": "FIGREF5" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "3.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Controllers. Some IR tasks require iteration through multiple runs; the system's behavior on each successive trial is modified based on feedback from a previous run. For example, a system might wish to ask for more documents or perform query expansion if the original query returns an insufficient number of relevant documents. IIM includes a Controller interface, which specifies methods for sending feedback from one node to another. The user can implement a variety of controllers, depending on the needs of the particular application.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "3.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "In the IIM Java implementation, nodes are specified by the abstract interface Node and its six abstract subinterfaces: Source, Filter, Annotator, Transformer, Sink and Renderer (see Figure 2 ). Any user-defined Java class which implements one of the Node subinterfaces can be loaded into IIM and used in a node chain. The visualization of a node is represented by a separate Java class, Box, which handles all of the details related to drawing the node and various visual cues in the node chain display.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 182, | |
| "end": 190, | |
| "text": "Figure 2", | |
| "ref_id": "FIGREF4" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "JAVA IMPLEMENTATION", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "The graphical user interface ( Figure 1 ) is implemented as a set of Java Swing components:", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 31, | |
| "end": 39, | |
| "text": "Figure 1", | |
| "ref_id": "FIGREF3" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "JAVA IMPLEMENTATION", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "Node Chain Display. The canvas to the right displays the current node chain, as described in the previous section. While the node chain is running, IIM provides two types of visual feedback regarding task progress. To indicate the percentage of overall run-time that the node is active, the border color of each node varies from bright green (low) to bright red (high). To indicate the amount of output per node per unit of time spent (throughput), the system indicates bytes per second as a text label under each node. A rectangular meter at the right of each node provides a graphic visualization of relative throughput; the node with the highest throughput will have a solid red meter, while other nodes will have a meter level which shows their throughput as a percentage of maximum throughput.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "JAVA IMPLEMENTATION", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "Node Library. The tree view to the upper left displays the library of nodes currently available on the user's machine for building and extending node chains. New nodes or node directories can be downloaded from the web and added while the system is running. The component loader examines each loaded class using Java's reflection capabilities, and places it in the appropriate place(s) in the component tree according to which of the Node subinterfaces it implements.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "JAVA IMPLEMENTATION", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "Node Property Editor. The Property Editor (table view) to the lower left in Figure 1 displays the properties of a selected node, which the user can update by clicking on it and entering a new value.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 76, | |
| "end": 84, | |
| "text": "Figure 1", | |
| "ref_id": "FIGREF3" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "JAVA IMPLEMENTATION", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "Node Chain Editor. IIM supports dynamic, interactive manipulation of node chains. The left side of the toolbar at the top of the IIM Window contains a set of chain editing but-tons. These allow the user to create, modify and tune new node chains built from pre-existing components.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "JAVA IMPLEMENTATION", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "Transport Bar. IIM uses a tape transport metaphor to model the operation of the node chain on a given data source. The \"Play\", \"Pause\" and \"Rewind\" buttons in the toolbar (right side) allow the user to pause the system in mid-task to adjust component parameters, or to start a task over after the node chain has been modified.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "JAVA IMPLEMENTATION", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "The run-time Controller subsystem is implemented as a Java class called ChainRunner, which can be invoked with or without a graphical interface component. ChainRunner is implemented as a Thread object separate from the Java Swing event dispatching thread, so that user actions can be processed concurrently with the ongoing operation of a node chain on a particular task.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "JAVA IMPLEMENTATION", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "The current IIM system includes a variety of nodes which implement the different IIM component interfaces. These nodes are described in this section.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "IIM COMPONENTS", | |
| "sec_num": "4." | |
| }, | |
| { | |
| "text": "EditableSource. Prompts the user to interactively enter sample documents (used primarily for testing, or entering queries).", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Source Nodes", | |
| "sec_num": "4.1" | |
| }, | |
| { | |
| "text": "WebSource. Generic support for access to web search engines (e.g., Google). Includes multithreading support for simultaneous retrieval of multiple result documents.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Source Nodes", | |
| "sec_num": "4.1" | |
| }, | |
| { | |
| "text": "NativeBATSource. Generic support for access to document collections stored on local disk. Implemented in C, with a Java wrapper that utilized the Java Native Interface (JNI).", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Source Nodes", | |
| "sec_num": "4.1" | |
| }, | |
| { | |
| "text": "SizeFilter. Only passes documents which are above a userdefined size threshold.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Filter Nodes", | |
| "sec_num": "4.2" | |
| }, | |
| { | |
| "text": "RegexpFilter. Only passes documents which match a userdefined regular expression; incorporates the GNU regexp package.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Filter Nodes", | |
| "sec_num": "4.2" | |
| }, | |
| { | |
| "text": "NameAnnotator. Locates named entities (currently, person names) in the body of the document, and adds appropriate annotations to the document.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Annotator Nodes", | |
| "sec_num": "4.3" | |
| }, | |
| { | |
| "text": "IVEAnnotator. For each named entity (person) annotation, checks a networked database for supplemental information about that individual. An interface to a database of information about individuals, publications, and organizations, created as part of the Information Validation and Evaluation project at CMU [12] . Implemented using Java Database Connectivity (JDBC).", | |
| "cite_spans": [ | |
| { | |
| "start": 307, | |
| "end": 311, | |
| "text": "[12]", | |
| "ref_id": "BIBREF11" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Annotator Nodes", | |
| "sec_num": "4.3" | |
| }, | |
| { | |
| "text": "BrillAnnotator. Accepts a user-defined annotation (e.g., PAS-SAGE) and adds a new annotation created by calling the Brill Tagger [1] on the associated text. Implemented via a TCP/IP socket protocol which accesses a remote instance of the tagger running as a network service.", | |
| "cite_spans": [ | |
| { | |
| "start": 129, | |
| "end": 132, | |
| "text": "[1]", | |
| "ref_id": "BIBREF0" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Annotator Nodes", | |
| "sec_num": "4.3" | |
| }, | |
| { | |
| "text": "ChartAnnotator. Accepts a user-defined annotation, and adds new annotations based on the results of bottom-up chart parsing with a user-defined grammar. The user can select which linguistic categories (e.g., NP VP, etc.) are to be annotated.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Annotator Nodes", | |
| "sec_num": "4.3" | |
| }, | |
| { | |
| "text": "RegexpAnnotator. Annotates passages which match a userdefined regular expression.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Annotator Nodes", | |
| "sec_num": "4.3" | |
| }, | |
| { | |
| "text": "BrillTransformer. Similar to the BrillAnnotator (see above), but operates directly on the document body (does not create separate annotations).", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Transformer Nodes", | |
| "sec_num": "4.4" | |
| }, | |
| { | |
| "text": "and retrieves a set of documents from the Inquery search engine [2] . Accesses an Inquery server running as a networked service, using TCP/IP sockets.", | |
| "cite_spans": [ | |
| { | |
| "start": 64, | |
| "end": 67, | |
| "text": "[2]", | |
| "ref_id": "BIBREF1" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Inquery. Accepts a query (represented as an input document)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "WordNet. Accepts a document, and annotates each word with a hypernym retrieved from WordNet [19] . Accesses a Word-Net server running as a networked service, using TCP/IP sockets.", | |
| "cite_spans": [ | |
| { | |
| "start": 92, | |
| "end": 96, | |
| "text": "[19]", | |
| "ref_id": "BIBREF18" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Inquery. Accepts a query (represented as an input document)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Ranker. Collects documents and sorts them according to a user-defined comparator. The current implementation supports sorting by document size or by annotation count.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Sink Nodes", | |
| "sec_num": "4.5" | |
| }, | |
| { | |
| "text": "CooccuranceSink. Builds a matrix of named entity associations within a given text window; uses NAME annotations created by the NameAnnotator (see above). The output of this node is a special subclass of Document, called Matrix-Document, which stores the association matrix created from the document collection.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Sink Nodes", | |
| "sec_num": "4.5" | |
| }, | |
| { | |
| "text": "QAnswer. Collects a variety of annotations from documents relevant to a particular query (e.g., \"What is Jupiter?\"), and uses them to synthesize an answer.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Sink Nodes", | |
| "sec_num": "4.5" | |
| }, | |
| { | |
| "text": "StreamRenderer. Outputs any documents it receives to a user-specified file stream (or to standard output, by default).", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Renderer Nodes", | |
| "sec_num": "4.6" | |
| }, | |
| { | |
| "text": "DocumentViewer. Pops up a document display window, which allows the user to browse documents as they are accepted by this node.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Renderer Nodes", | |
| "sec_num": "4.6" | |
| }, | |
| { | |
| "text": "MatrixRenderer. A two-dimensional visualization of the association matrix created by the CoocurrenceSink (see above). Accepts instances of MatrixDocument.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Renderer Nodes", | |
| "sec_num": "4.6" | |
| }, | |
| { | |
| "text": "The initial set of component nodes has been used as the basis for three experimental applications:", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "IIM APPLICATIONS", | |
| "sec_num": "5." | |
| }, | |
| { | |
| "text": "Filtering and Annotation. An interactive node chain that allows the user to annotate and collect documents matching any regular expression; the resulting collection can then be viewed interactively (with highlighted annotations) in a popup viewer window.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "IIM APPLICATIONS", | |
| "sec_num": "5." | |
| }, | |
| { | |
| "text": "Named Entity Association. A node chain which performs named-entity annotation using a phi-square measure [3] , producin a MatrixDocument object (a user-defined Document subclass, which represents the association matrix). Note that the addition of a specialized Document subclass does not require recompilation of IIM (although the user must take care that specialized document objects are properly handled by user-defined nodes).", | |
| "cite_spans": [ | |
| { | |
| "start": 105, | |
| "end": 108, | |
| "text": "[3]", | |
| "ref_id": "BIBREF2" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "IIM APPLICATIONS", | |
| "sec_num": "5." | |
| }, | |
| { | |
| "text": "Question Answering. A node chain which answers \"What is\" questions by querying the web for relevant documents, finding relevant passages [8, 10] , and synthesizing answers from the results of various regular expression matches 3 .", | |
| "cite_spans": [ | |
| { | |
| "start": 137, | |
| "end": 140, | |
| "text": "[8,", | |
| "ref_id": "BIBREF7" | |
| }, | |
| { | |
| "start": 141, | |
| "end": 144, | |
| "text": "10]", | |
| "ref_id": "BIBREF9" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "IIM APPLICATIONS", | |
| "sec_num": "5." | |
| }, | |
| { | |
| "text": "In order to support accurate side-by-side evaluation of different modules, IIM implements two kinds of instrumentation for runtime performance data:", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "PERFORMANCE", | |
| "sec_num": "6." | |
| }, | |
| { | |
| "text": "Per-Node Run Time. The ChainRunner and Box classes automatically maintain run-time statistics for every node in a chain (including user-defined nodes). These statistics are printed at the end of every run.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "PERFORMANCE", | |
| "sec_num": "6." | |
| }, | |
| { | |
| "text": "Node-Specific Statistics. For user-defined nodes, it may be useful to report task-specific statistics (e.g., for an Annotator, the total number of annotations, the average annotation size, etc.). IIM provides a class called Options, which contains a set of optional interfaces that can be implemented to customize a node's behavior. Any node that wishes to report task-specific statistical data can implement the ReportsStatistics interface, which is called by the ChainRunner when the chain finishes.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "PERFORMANCE", | |
| "sec_num": "6." | |
| }, | |
| { | |
| "text": "An example of the statistical data produced by the system is shown in Figure 4 . The system is careful to keep track of time spent \"inside\" the nodes, as well as the overall clock time taken for the task. This allows the user to determine how much overhead is added by the IIM system itself.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 70, | |
| "end": 78, | |
| "text": "Figure 4", | |
| "ref_id": "FIGREF6" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "PERFORMANCE", | |
| "sec_num": "6." | |
| }, | |
| { | |
| "text": "The throughput speed of the prototype system is acceptably fast, averaging better than 50M of text per minute on a sample filtering task (530M of web documents), running on a typical Pentium III PC with 128M RAM. IIM requires about 10M of memory (including the Java run-time environment) for the core system and user interface, with additional memory requirements depending on the size of the document stream and the sophistication of the node chain 4 . Although the core system is implemented in Java, we have also implemented nodes in C++, using appropriate wrapper classes and the Java Native Interface (JNI). This technique allows us to implement critical, resource-intensive nodes using native code, without sacrificing the benefits of the Java-based core system.", | |
| "cite_spans": [ | |
| { | |
| "start": 450, | |
| "end": 451, | |
| "text": "4", | |
| "ref_id": "BIBREF3" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "PERFORMANCE", | |
| "sec_num": "6." | |
| }, | |
| { | |
| "text": "The preliminary results of the IIM prototype are promising. IIM's drag-and-drop component library makes it possible to build and tune a new application in a matter of minutes, greatly reducing the amount of effort required to integrate and reuse existing modules. \u00a3 We are currently expanding this application to include part of speech tagging and syntactic parsing, both of which are straightforwardly modeled as examples of the Annotator interface. \u00a4 Node chains which create a high volume of annotations per document use more memory, as do node chains which create new collections, transform documents, etc. In the future, we hope this high degree of flexibility will encourage greater experimentation and the creation of new aggregate systems from novel combinations of components, leading to a true \"marketplace of modules\".", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "DISCUSSION", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "Building extensible architectures as \"class library plus application framework\" is not a new idea, and has been discussed before with respect to information retrieval systems [7, 18, 9] . One might claim that any new IR architecture should adopt a similar design pattern, given the proven benefits of separating the modules from the application framework (flexibility, extensibility, high degree of reuse, easy integration, etc.). To some extent, IIM consolidates, refines and/or reimplements ideas previously published in the literature. Specifically, the following characteristics of the IIM architecture can be directly compared with prior work:", | |
| "cite_spans": [ | |
| { | |
| "start": 175, | |
| "end": 178, | |
| "text": "[7,", | |
| "ref_id": "BIBREF6" | |
| }, | |
| { | |
| "start": 179, | |
| "end": 182, | |
| "text": "18,", | |
| "ref_id": "BIBREF17" | |
| }, | |
| { | |
| "start": 183, | |
| "end": 185, | |
| "text": "9]", | |
| "ref_id": "BIBREF8" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "DISCUSSION", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "The IIM classes Renderer, Document, MultiDocument, and annotations on Document can be considered alternative implementations of the InfoGrid classes Visualizer, Document, DocumentSet and DocumentPart [15] . However, in IIM annotations are \"lightweight\", meaning that they do not require the instantiation of a separate user object, but can be modeled as simple String instances in Java when a high degree of annotation requires optimal space efficiency.", | |
| "cite_spans": [ | |
| { | |
| "start": 200, | |
| "end": 204, | |
| "text": "[15]", | |
| "ref_id": "BIBREF14" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "DISCUSSION", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "The use of color to indicate status of a node is also used in the SketchTrieve system [18] . IIM's visualization of the document flow as a \"node chain\" can be compared to the \"wire and dock\" approach used in other IR interfaces [9, 4, 13] .", | |
| "cite_spans": [ | |
| { | |
| "start": 86, | |
| "end": 90, | |
| "text": "[18]", | |
| "ref_id": "BIBREF17" | |
| }, | |
| { | |
| "start": 228, | |
| "end": 231, | |
| "text": "[9,", | |
| "ref_id": "BIBREF8" | |
| }, | |
| { | |
| "start": 232, | |
| "end": 234, | |
| "text": "4,", | |
| "ref_id": "BIBREF3" | |
| }, | |
| { | |
| "start": 235, | |
| "end": 238, | |
| "text": "13]", | |
| "ref_id": "BIBREF12" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "DISCUSSION", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "The use of a Property Editor to customize component behavior is an alternative approach to the IrDialogs provided by the FireWorks toolkit [9] for display and update of a component's state.", | |
| "cite_spans": [ | |
| { | |
| "start": 139, | |
| "end": 142, | |
| "text": "[9]", | |
| "ref_id": "BIBREF8" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "DISCUSSION", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "Nevertheless, IIM is at once simpler and more general than systems such as InfoGrid [15] and FIRE [18] . One could claim that IIM supports a higher degree of informality [9] than FIRE, since it enforces no type-checking on node connectivity. Since all tasks are modeled abstractly as document flows, nodes need only implement one of the Node sub-interfaces, and each node chain must begin with a Source. Another point of comparison is the task-specific detail present in the FIRE class hierarchy. In IIM, task-specific objects are left up to the developer (for example, representing particulars of access control on information sources, or details of indexing and retrieval, such as Index, Query, etc.).", | |
| "cite_spans": [ | |
| { | |
| "start": 84, | |
| "end": 88, | |
| "text": "[15]", | |
| "ref_id": "BIBREF14" | |
| }, | |
| { | |
| "start": 98, | |
| "end": 102, | |
| "text": "[18]", | |
| "ref_id": "BIBREF17" | |
| }, | |
| { | |
| "start": 170, | |
| "end": 173, | |
| "text": "[9]", | |
| "ref_id": "BIBREF8" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "DISCUSSION", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "Hendry and Harper [9] have used the degree of user control as a dimension of comparison for IR architectures. At one extreme are systems which allow dynamic view and access to the run-time state of components, while at the other lie systems which hide implementation detail and perform some functions automatically, for improved performance. In their comparison of SketchTrieve and InfoGrid, Hendry and Harper note that \"a software architecture should provide abstractions for implementing both these\". In IIM, the use of macro nodes can hide component details from the end user, especially when the component's parameter values have been tuned in advance for optimal performance.", | |
| "cite_spans": [ | |
| { | |
| "start": 18, | |
| "end": 21, | |
| "text": "[9]", | |
| "ref_id": "BIBREF8" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "DISCUSSION", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "While the initial results reported here show promise, we are still evaluating the usability of IIM in terms of trainability (how fast does a novice learn the system), reusability (how easily a novice can build new applications from existing node libraries) and ease of integration (effort required to integrate external components and systems). The current version of IIM lacks the explicit document management component found in systems like GATE [4] and Corelli [20] ; we are in the process of adding this functionality for the official release of IIM.", | |
| "cite_spans": [ | |
| { | |
| "start": 448, | |
| "end": 451, | |
| "text": "[4]", | |
| "ref_id": "BIBREF3" | |
| }, | |
| { | |
| "start": 464, | |
| "end": 468, | |
| "text": "[20]", | |
| "ref_id": "BIBREF19" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "ONGOING RESEARCH", | |
| "sec_num": "8." | |
| }, | |
| { | |
| "text": "The IIM system (source code, class documentation, and node libraries) will be made available via the web as one of our final project milestones later in 2001. Anyone interested in using the system or participating in ongoing research and development is invited to visit the IIM web site and join the IIM mailing list: ", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "ONGOING RESEARCH", | |
| "sec_num": "8." | |
| }, | |
| { | |
| "text": "EQUATION", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [ | |
| { | |
| "start": 0, | |
| "end": 8, | |
| "text": "EQUATION", | |
| "ref_id": "EQREF", | |
| "raw_str": "\u00a5 \u00a7 \u00a6 \u00a6 \u00a9 \u00a7 \u00a5 \u00a7 \u00a6 !\" # \u00a6 $ !% ' & ( !% $ \" # ) 0 !1", | |
| "eq_num": "( 2 )" | |
| } | |
| ], | |
| "section": "ONGOING RESEARCH", | |
| "sec_num": "8." | |
| } | |
| ], | |
| "back_matter": [ | |
| { | |
| "text": "The authors would like to thank Jamie Callan for his guidance on the architecture design, and Krzysztof Czuba for providing networked instances of the Brill Tagger, Inquery, and WordNet.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "ACKNOWLEDGEMENTS", | |
| "sec_num": "9." | |
| } | |
| ], | |
| "bib_entries": { | |
| "BIBREF0": { | |
| "ref_id": "b0", | |
| "title": "A simple rule-based part of speech tagger", | |
| "authors": [ | |
| { | |
| "first": "Eric", | |
| "middle": [], | |
| "last": "Brill", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1992, | |
| "venue": "Proceedings of the Third Conference on Applied Natural Language Processing", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Brill, Eric (1992). \"A simple rule-based part of speech tagger\", Proceedings of the Third Conference on Applied Natural Language Processing.", | |
| "links": null | |
| }, | |
| "BIBREF1": { | |
| "ref_id": "b1", | |
| "title": "The INQUERY Retrieval System", | |
| "authors": [ | |
| { | |
| "first": "J", | |
| "middle": [ | |
| "P" | |
| ], | |
| "last": "Callan", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "W", | |
| "middle": [ | |
| "B" | |
| ], | |
| "last": "Croft", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "S", | |
| "middle": [ | |
| "M" | |
| ], | |
| "last": "Harding", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1992, | |
| "venue": "Proceedings of the 3rd International Conference on Database and Expert Systems", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Callan, J. P., W. B. Croft, and S. M. Harding (1992). \"The INQUERY Retrieval System\", Proceedings of the 3rd International Conference on Database and Expert Systems.", | |
| "links": null | |
| }, | |
| "BIBREF2": { | |
| "ref_id": "b2", | |
| "title": "A System for Discovering Relationships by Feature Extraction from Text Databases", | |
| "authors": [ | |
| { | |
| "first": "J", | |
| "middle": [], | |
| "last": "Conrad", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "M", | |
| "middle": [ | |
| "H" | |
| ], | |
| "last": "Utt", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1994, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Conrad, J., and M. H. Utt (1994). \"A System for Discovering Relationships by Feature Extraction from Text Databases\", SIGIR '94.", | |
| "links": null | |
| }, | |
| "BIBREF3": { | |
| "ref_id": "b3", | |
| "title": "GATE -an environment to support research and development in natural language engineering", | |
| "authors": [ | |
| { | |
| "first": "R", | |
| "middle": [], | |
| "last": "Gaizauskas", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "H", | |
| "middle": [], | |
| "last": "Cunningham", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "Y", | |
| "middle": [], | |
| "last": "Wilks", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "P", | |
| "middle": [], | |
| "last": "Rodgers", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "K", | |
| "middle": [], | |
| "last": "Humphreys", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1996, | |
| "venue": "Proceedings of the 8th IEEE International Conference on Tools with Artificial Intelligence (ICTAI96)", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "58--66", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Gaizauskas, R. Cunningham, H. Wilks, Y. Rodgers, P. and Humphreys, K. GATE -an environment to support research and development in natural language engineering. Proceedings of the 8th IEEE International Conference on Tools with Artificial Intelligence (ICTAI96) , Toulouse, France, pp 58-66, 1996.", | |
| "links": null | |
| }, | |
| "BIBREF4": { | |
| "ref_id": "b4", | |
| "title": "Design Patterns: Elements of Reusable Object-Oriented Software", | |
| "authors": [ | |
| { | |
| "first": "E", | |
| "middle": [], | |
| "last": "Gamma", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "R", | |
| "middle": [], | |
| "last": "Helm", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "R", | |
| "middle": [], | |
| "last": "Johnson", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "J", | |
| "middle": [], | |
| "last": "Vlissides", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1995, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Gamma, E., Helm, R., Johnson, R. and Vlissides, J. (1995). Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley.", | |
| "links": null | |
| }, | |
| "BIBREF5": { | |
| "ref_id": "b5", | |
| "title": "Building an Architecture: A CAWG Saga", | |
| "authors": [ | |
| { | |
| "first": "R", | |
| "middle": [], | |
| "last": "Grishman", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1996, | |
| "venue": "Advances in Text Processing: Tipster Program Phase II", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Grishman, R. (1996). \"Building an Architecture: A CAWG Saga\", in Advances in Text Processing: Tipster Program Phase II, sponsored by DARPA ITC.", | |
| "links": null | |
| }, | |
| "BIBREF6": { | |
| "ref_id": "b6", | |
| "title": "ECLAIR: An extensible Class Library for Information Retrieval", | |
| "authors": [ | |
| { | |
| "first": "D", | |
| "middle": [ | |
| "J" | |
| ], | |
| "last": "Harper", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "A", | |
| "middle": [ | |
| "D M" | |
| ], | |
| "last": "Walker", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1992, | |
| "venue": "Computer Journal", | |
| "volume": "35", | |
| "issue": "3", | |
| "pages": "256--267", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Harper, D.J. and A.D.M. Walker (1992). \"ECLAIR: An extensible Class Library for Information Retrieval\", Computer Journal, 35(3):256-267.", | |
| "links": null | |
| }, | |
| "BIBREF7": { | |
| "ref_id": "b7", | |
| "title": "Automatic acquisition of hyponyms from large text corpora", | |
| "authors": [ | |
| { | |
| "first": "M", | |
| "middle": [], | |
| "last": "Hearst", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": null, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Hearst, M. \"Automatic acquisition of hyponyms from large text corpora.\" COLING '92.", | |
| "links": null | |
| }, | |
| "BIBREF8": { | |
| "ref_id": "b8", | |
| "title": "An architecture for implementing extensible information-seeking environments", | |
| "authors": [ | |
| { | |
| "first": "D", | |
| "middle": [ | |
| "G" | |
| ], | |
| "last": "Hendry", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "D", | |
| "middle": [ | |
| "J" | |
| ], | |
| "last": "Harper", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1996, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Hendry, D. G., and Harper, D. J. (1996). \"An architecture for implementing extensible information-seeking environments\", SIGIR '96.", | |
| "links": null | |
| }, | |
| "BIBREF9": { | |
| "ref_id": "b9", | |
| "title": "Retrieving descriptive phrases from large amounts of free text", | |
| "authors": [ | |
| { | |
| "first": "H", | |
| "middle": [], | |
| "last": "Joho", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "M", | |
| "middle": [], | |
| "last": "Sanderson", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 2000, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Joho, H. and M. Sanderson, \"Retrieving descriptive phrases from large amounts of free text\", CIKM 2000.", | |
| "links": null | |
| }, | |
| "BIBREF10": { | |
| "ref_id": "b10", | |
| "title": "ATTICS: A Software Platform for Online Text Classification", | |
| "authors": [ | |
| { | |
| "first": "D", | |
| "middle": [], | |
| "last": "Lewis", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "D", | |
| "middle": [], | |
| "last": "Stern", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "A", | |
| "middle": [], | |
| "last": "Singhal", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1999, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Lewis, D., D. Stern and A. Singhal (1999). \"ATTICS: A Software Platform for Online Text Classification\", SIGIR '99.", | |
| "links": null | |
| }, | |
| "BIBREF11": { | |
| "ref_id": "b11", | |
| "title": "Language Resources for Determining Authority", | |
| "authors": [ | |
| { | |
| "first": "T", | |
| "middle": [], | |
| "last": "Mitamura", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 2001, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Mitamura, T. (2001). \"Language Resources for Determining Authority\", unpublished manuscript.", | |
| "links": null | |
| }, | |
| "BIBREF12": { | |
| "ref_id": "b12", | |
| "title": "Analyst's Workbench: A CAD-like GUI for Textual Search and Filter Creation", | |
| "authors": [ | |
| { | |
| "first": "T", | |
| "middle": [], | |
| "last": "Neuendorffer", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 2000, | |
| "venue": "HCII Seminar Series", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Neuendorffer, T. (2000). \"Analyst's Workbench: A CAD-like GUI for Textual Search and Filter Creation\", HCII Seminar Series, Carnegie Mellon University, November 29.", | |
| "links": null | |
| }, | |
| "BIBREF13": { | |
| "ref_id": "b13", | |
| "title": "Software Engineering: A Practitioner's Approach", | |
| "authors": [ | |
| { | |
| "first": "R", | |
| "middle": [], | |
| "last": "Pressman", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 2000, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Pressman, R. (2000). Software Engineering: A Practitioner's Approach, 5th edition, McGraw-Hill.", | |
| "links": null | |
| }, | |
| "BIBREF14": { | |
| "ref_id": "b14", | |
| "title": "The Information Grid: A Framework for Information Retrieval and Retrieval-Centred Applications. UIST '92", | |
| "authors": [ | |
| { | |
| "first": "R", | |
| "middle": [], | |
| "last": "Rao", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "S", | |
| "middle": [ | |
| "K" | |
| ], | |
| "last": "Card", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "H", | |
| "middle": [ | |
| "D" | |
| ], | |
| "last": "Jellinek", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "J", | |
| "middle": [ | |
| "D" | |
| ], | |
| "last": "Mackinlay", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "G", | |
| "middle": [], | |
| "last": "Robertson", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": null, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Rao, R., S.K. Card, H.D. Jellinek, J.D. MacKinlay and G. Robertson: The Information Grid: A Framework for Information Retrieval and Retrieval-Centred Applications. UIST '92.", | |
| "links": null | |
| }, | |
| "BIBREF15": { | |
| "ref_id": "b15", | |
| "title": "Software Architecture: Perspectives on an Emerging Discipline", | |
| "authors": [ | |
| { | |
| "first": "M", | |
| "middle": [], | |
| "last": "Shaw", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "D", | |
| "middle": [], | |
| "last": "Garlan", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1996, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Shaw, M. and D. Garlan (1996). Software Architecture: Perspectives on an Emerging Discipline, Prentice-Hall.", | |
| "links": null | |
| }, | |
| "BIBREF16": { | |
| "ref_id": "b16", | |
| "title": "The SMART Retrieval System -Experiments in Automatic Document Processing", | |
| "authors": [ | |
| { | |
| "first": "G", | |
| "middle": [], | |
| "last": "Salton", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1971, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Salton, G. (1971). The SMART Retrieval System - Experiments in Automatic Document Processing, Prentice-Hall.", | |
| "links": null | |
| }, | |
| "BIBREF17": { | |
| "ref_id": "b17", | |
| "title": "Design of a reusable IR framework", | |
| "authors": [ | |
| { | |
| "first": "G", | |
| "middle": [], | |
| "last": "Sonnenberger", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "H", | |
| "middle": [], | |
| "last": "Frei", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1995, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Sonnenberger, G. and H. Frei (1995). \"Design of a reusable IR framework\", SIGIR '95.", | |
| "links": null | |
| }, | |
| "BIBREF18": { | |
| "ref_id": "b18", | |
| "title": "WordNet: An electronic lexical database", | |
| "authors": [ | |
| { | |
| "first": "C", | |
| "middle": [], | |
| "last": "Fellbaum", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1998, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Fellbaum, C. (ed) (1998). WordNet: An electronic lexical database. Cambridge, MA: MIT Press.", | |
| "links": null | |
| }, | |
| "BIBREF19": { | |
| "ref_id": "b19", | |
| "title": "An Open Distributed Architecture for Reuse and Integration of Heterogenous NLP Components", | |
| "authors": [ | |
| { | |
| "first": "R", | |
| "middle": [], | |
| "last": "Zajac", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1997, | |
| "venue": "Proceedings of the 5th conference on Applied Natural Language Processing", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Zajac, R. (1997). \"An Open Distributed Architecture for Reuse and Integration of Heterogenous NLP Components\", In Proceedings of the 5th conference on Applied Natural Language Processing (ANLP-97).", | |
| "links": null | |
| } | |
| }, | |
| "ref_entries": { | |
| "FIGREF0": { | |
| "uris": null, | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Rapid Deployment. Speed up the initial development of new applications. This work is supported by National Science Foundation (KDI) grant number 9873009. \u00a2 For further discussion on how these systems compare with the present work, see Section 7." | |
| }, | |
| "FIGREF1": { | |
| "uris": null, | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Use standardized modules to support plugand-play updates." | |
| }, | |
| "FIGREF2": { | |
| "uris": null, | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Enhance performance by allowing novel combinations of existing components." | |
| }, | |
| "FIGREF3": { | |
| "uris": null, | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "IIM User Interface" | |
| }, | |
| "FIGREF4": { | |
| "uris": null, | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Node Interface and Subtypes." | |
| }, | |
| "FIGREF5": { | |
| "uris": null, | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Exporting A Macro Node." | |
| }, | |
| "FIGREF6": { | |
| "uris": null, | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Statistics for a Node Chain." | |
| } | |
| } | |
| } | |
| } |