File Information
File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/metho/79/p79-1023_metho.xml
Size: 11,107 bytes
Last Modified: 2025-10-06 14:11:19
<?xml version="1.0" standalone="yes"?> <Paper uid="P79-1023"> <Title>W~ IL: RETRIEVE \[JOB.EMPLOYEE,JOB.ADDRESS\] WHERE (DIV.DNAME - &quot;R&D&quot;) AND (DIV.DIV JOB CH - JOB.DIV_JOBCH) AND (JOB.JNAME - &quot;SECRETARY&quot;) AND (JOB.CLASS - &quot;EXECUTIVE&quot;) WW'DMS QUERY: INVOKE 'WWDMS/PERSONNEL/ADF' REPORT EUFID-1 ON FILE 'USER/PASSWD/EUFID' FOR TTY QI. LINE &quot;EMPLOYEE NAME =&quot;,EMPLOYEE Q2. LINE &quot;ADDRESS &quot;&quot;,ADDRESS</Title> <Section position="4" start_page="0" end_page="92" type="metho"> <SectionTitle> 3. TABLES </SectionTitle> <Paragraph position="0"> EUFID is application and data base independent. Thls independence is achieved by having three sets of tables-the semantic dictionary tables, the data base tables, and the mapping tables which map from the semantic view to the data base. Conceivably, a single semantic view could map to two data bases that contain the same data but are accessed by different data management systems.</Paragraph> <Section position="1" start_page="91" end_page="91" type="sub_section"> <SectionTitle> 3.1 SEMANTIC TABLES </SectionTitle> <Paragraph position="0"> The semantic view is defined by an application expert working with a EUFID expert. Together the 7 determine the ways chat a user mlghc want to talk about the data. From this, a llsC of words is developed and the basic sentence structures are defined. Words are classed as: entitles (e.g., company) events (e.g., send) funcClons (after 1975) parrs of a phrase or idiom (map coordlnaCes) connectors (co) system words (the) anaphores (ic) two or more of the above (ship an enClCy plus ship an event) An entity corresponds approximately co a noun and an event co a verb. Connectors are preposlClons which are dropped after the sentence is parsed. System words are conjunctions, auxiliaries, and decermlners whloh participate in determining meaning buc do noC relate co data base fields. Anaphores are words chac refer Co previous words and are replaced by them while parsln 8. Basically then, the only words chat relate co the items in the data base are entities, events, and funcclons.</Paragraph> <Paragraph position="1"> Entities and events are defined using a case structure representation which combines synCacclc and sm---clc information. Lexlcal items which may co-occur with an entity to form noun phrases, or wlch a verb co form verb phrases, fill cases on the enClCy or event. Cases are disclngulshed by the sac of possible fillers, the possible connectors, and the syncactlc position of the case relaclve co the antic 7 or event. A case may be specified as opclonal or obllgacory.</Paragraph> <Paragraph position="2"> A sense of an entlCy or event is defined by the sac of cases which form a dlsCincC noun phrase or verb phrase type. Three senses of the word &quot;ship&quot; are illustrated in Figure i.</Paragraph> <Paragraph position="4"> The flrsc sense of &quot;ship&quot; accounts for acClve voice verb phrases wlch the pattern &quot;Companies ship goods CO companies in year.*' Examples are: ..</Paragraph> <Paragraph position="5"> Whac companies ship to Ajax? In 1976, who shipped light freight co Colonial? This sense of &quot;ship&quot; has ~wo obligatory cases, A and C, and ~ao optional cases B and H. The face chac the &quot;year&quot; case can be moved opclonally wichln the phrase is noC represented within the case structure, buc is recoEnlzed by the Analyzer, which assigns a structure Co the phrase.</Paragraph> <Paragraph position="6"> The second sense of &quot;ship&quot; accounts for the passive con8CrucClon of the type &quot;Goods are shipped Co company by company.&quot; Examples are: Was llghc frelghc shipped Co Ajax in 19787 What goods were shipped Co Ajax by Colonial? By whaC companies in 1975 was hesw/ freight shipped Co Colonial? Case O has the same filler as case B, but precedes &quot;ship&quot; and is obligatory. Case g has the same filler as case A, buc follows &quot;ship&quot;, has a dlfferenc connector, and is optional. That is, sense i of &quot;ship&quot; is daflned as the associaclon of &quot;ship&quot; with cases A,B,C. Sense 2 is the associ&clon of &quot;ship&quot; with cases C,D,E. Sense 3 of &quot;ship&quot; describes the nominallzed form &quot;shlpmenc&quot; and expliclCly captures the informaclon Chac shlpmencs involve goods and reflect transacClons between companies.</Paragraph> <Paragraph position="7"> An *~-mple is: '~taC is the cransacclon number for the shlpmanc of bolts from Colonial co Ajax?&quot;</Paragraph> </Section> <Section position="2" start_page="91" end_page="91" type="sub_section"> <SectionTitle> 3.2 DATA BASE TABLES </SectionTitle> <Paragraph position="0"> The data base cables describe the data base as viewed by the data management system. Since all dace mamagsmenC syscemn deal with dace iCmma organized into groups chac are related through links, ic is possible co have a co~n cable format for any dace management system.</Paragraph> <Paragraph position="1"> The dace bus cables actually consist of two cables.</Paragraph> <Paragraph position="2"> The CAN table contains information about groups and dace iC ~a. A group (also called entity or record in ocher systems) is Idenclfled by the group name. A dare Icam in che CAN cable consists of Che data ices &quot;mine, che grOUp CO which IC belongs, a uniC code, an output Idenclflar, and some field type informaClon.</Paragraph> <Paragraph position="3"> Notably missing is anything about the byte wichln the record or the number of bytes. ~UFID accesses the dace base through s data management sysCom. Therefore, the dace can be reorganized ~rLChouC/ changing the EUFID cables aa long as the dace iCeml retain their names and chair groupings.</Paragraph> <Paragraph position="4"> The second data beam cable is the P~L cable which contains an encz 7 for each group with its links co ocher groups.</Paragraph> <Paragraph position="5"> For nscwork dace bases, cha link is the chain name for the primary chain chac connects master and derail records. For relational dace bases, every dace item pair in the two groups chac can have the same value is a potential link.</Paragraph> </Section> <Section position="3" start_page="91" end_page="92" type="sub_section"> <SectionTitle> 3.3 MAPPING TABLES </SectionTitle> <Paragraph position="0"> The mapping cablu cell the program how to gec from the semantic nods, as found in the semantic dictionary, co the dace base field names. Each entry in the mapping table has a node name followed by two parts. The first parr describes the pacCsrn of cases and their fillers for chac node name. The second parr is called a production and ic gives the mapping for each case filler. A node may map co a node higher in the sentence tree before iC maps co a dace bus item. For exalpls, &quot;company name&quot; in the question '~at companies are locacnd in Los Angeles?&quot; may map to a group containing ge~sral company ~n~ormacion. However, &quot;company name&quot; in the question &quot;W~'mt companies ship Co Los Angeles?&quot; may map to a group concain~ng shipping company information.</Paragraph> <Paragraph position="1"> Therefore, it is necessary to first map &quot;company name&quot; up to a higher node that determines the meaning. At the point where a unique node is determined, the mapping is made to a data item name via the CAN table. This data item name is used in the generatlon of the query to the data management system.</Paragraph> </Section> </Section> <Section position="5" start_page="92" end_page="92" type="metho"> <SectionTitle> 4. INTERMEDIATE LANGUAGE </SectionTitle> <Paragraph position="0"> EUFID is adaptable to most data management systems without changes to the central modules. This is accomplished by using an intermediate language (IL). The main parts of EUFID analyze the question, map it to data items, and then express the query in a standard language (IL). A translator is written for each data management system in order to rephrase the IL query into the language of the data management system. This is an extra step, but it greatly enhances EUFID's flexibility and portability.</Paragraph> <Paragraph position="1"> The intermediate language looks like a relational retrieval language. Translating it into QUEL is straightforward, but translating It to a procedural language such as WWDMS is very difficult. The example below shows a question with its QUEL and WWDMS equivalent.</Paragraph> </Section> <Section position="6" start_page="92" end_page="92" type="metho"> <SectionTitle> QUESTION: WHAT ARE THE NAMES AND ADDRESSES OF THE EXECUTIVE SECRETARIES IN R&D? INGRES IL: RETRIEVE \[JOB.EHFLOYEE,JOB.ADDRESS\] </SectionTitle> <Paragraph position="0"> WHERE (DIV.NAHE = &quot;R&D&quot;) AND (DIV.JOB = JOB.NAHE) AND (JOB.NAME = &quot;SECRETARY&quot;) AND (JOB.CLASS = &quot;EXECUTIVE&quot;) QUEL: range of div is dlv range of Job is Job retrieve (Job.employee,Job.address) where dlv.name = &quot;R&D&quot;) and dlv. Job= Job.name and Job.name = &quot;secretary&quot; and Job.class = &quot;executive&quot;</Paragraph> </Section> <Section position="7" start_page="92" end_page="93" type="metho"> <SectionTitle> 5. SECURITY </SectionTitle> <Paragraph position="0"> EUFID protects the data base by removin B the user from direct access to the data management system and data base. At the most general level, EUFID will only allow users to ask questions within the semantics that are defined and stored in the dictionary. Some data items or views of the data could be omitted from the dlctlonazy.</Paragraph> <Paragraph position="1"> At a more specific level, EUFID controls access through a user profile table. Before a user can use EUFID, a system person must define the user profile. This cable states which applications or subsets of applications are available to the user. One user may be allowed Co query everything that is covered by the semantic dictionary.</Paragraph> <Paragraph position="2"> Another user may be restricted in his access.</Paragraph> <Paragraph position="3"> The profile table is built by a concept graph editor.</Paragraph> <Paragraph position="4"> When a new login id is established for EUFID, the system person gives the application name of each application that the user may access. Associated with an applicatlon name is a set of file names of the tables for the application. If access is to be restricted, a copy of the CAN and mapping function tables is made. The copies are chanEed to delete the data items which the user is not to know about. The names of the restricted tables are then stored in the user's profile record. EUFID will still be able to find the words that are used co talk about the data item, but when EUFID maps the word to a removed data item it responds to the user as though the sentence could not be understood.</Paragraph> </Section> class="xml-element"></Paper>