|
{ |
|
"paper_id": "1998", |
|
"header": { |
|
"generated_with": "S2ORC 1.0.0", |
|
"date_generated": "2023-01-19T10:26:17.276863Z" |
|
}, |
|
"title": "MULTIDOC -Controlling Language in multilingual Documentation J\u00f6rg Sch\u00fctz", |
|
"authors": [], |
|
"year": "", |
|
"venue": null, |
|
"identifiers": {}, |
|
"abstract": "", |
|
"pdf_parse": { |
|
"paper_id": "1998", |
|
"_pdf_hash": "", |
|
"abstract": [], |
|
"body_text": [ |
|
{ |
|
"text": "MULTIDOC is a European project of the Fourth Framework Programme within the Language Engineering Sector. It is founded on the specific needs and requirements of product documentation expressed by several representatives of the European automotive industry, among them are Bertone, BMW, Jaguar, Renault, Rolls-Royce Motor Cars, Rover, Volvo and others. The focus of the project is particularly on the multilingual aspects of product documentation. Therefore, the general goal is to define and specify methods, tools and workflows supporting stronger demands on quality, consistency and clarity in the technical information, and shorter lead times and reduced costs in the whole production value cycle of documentation including the translation into multiple languages.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Introduction", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "The results of the project are applicable to any other component or system manufacturing business; thus, they are not restricted to the automotive industry. The project is divided into two phases: an inception and elaboration phase, the so-called MULTIDOC Concerted Action (LE3-4230), and a construction or development phase, the so-called MULTIDOC Project (LE4-8323). The first phase has been finished by the end of last year, and the second phase has started in January 1998.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Introduction", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "The aim of the MULTIDOC Concerted Action was to identify the problem areas and to specify solutions for the European automotive industry when it comes to multilingual product documentation and also set a roadmap for the future. In software engineering, this phase is usually called the inception phase of an iterative software development process. During inception we establish the business rationale for the project and decide on the scope of the project. This is also the phase where we get the commitment from the project sponsor(s) to go further; in our case this was the successful evaluation of our MULTIDOC Project proposal.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "The Concerted Action also included parts of the elaboration phase of a software development project. In elaboration, we collect more detailed requirements, do high-level analysis and design to establish a baseline architecture, and create the plan for construction which is the actual software production phase consisting of many iterations. In our domain, the most crucial bottlenecks comprise the following business areas that needed further elaboration:", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "\u2022 More and more languages in which product documentation has to be published;", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "there is a drastically increased focus on Asian and East-European markets. \u2022 Increasing costs for translations.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "\u2022 Lead times in the document production process and in the translation process.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "\u2022 Poor or no possibility to measure and control the translation process.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "\u2022 Inconsistent use of information structure and information content.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "All project partners agree that besides the quality of the product the services associated with the product and the accompanying documentation of the product must be seen as an integral part of the product. To satisfy the demand for high-quality technical documentation, the documentation has not only to be comprehensible and up to date, it has to be produced and delivered (including the accessibility to new or up-dated information) with modern technologies. The following scenario shall exemplify the intended direction:", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "Mr M is the proud owner of a new, environmentally clean car which was assembled according to his wish list from a huge variety of car components of the automotive manufacturer. The first contact with his new car was well before the actual delivery in a virtual reality animation, where Mr M was able to check his colour selection, the harmonisation of the chosen colour with the selected materials of the car interior, as well as first virtual driving tests.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "Mr M is also very satisfied with the delivered car documentation; he got the personalised documentation right after the deal was contracted. This documentation is not only personalised but also customised to his specific car: this includes the appropriate colouring of all graphics in the documentation and the text itself, where we do not find any generalised references such as \"... applies to specific countries.\", \"... according to the model variant.\" and so forth.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "With the CD-ROM edition of the documentation Mr M can directly search for information on his PC at home, and he is also provided with multimedia enhanced information about his car. This documentation is also available in his car via the on-board computer. This computer maintains each service work and possible repair work in its storage, and therefore permits customised service and repair measures and fault tracing at dealer's workshops. Not to mention, that these data are also available via the world-wide computer network of the car manufacturer.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "Mr M gets new information about his car and about new products and services of the car manufacturer via his Internet access at home; for this he has subscribed to the free information service which in addition is parametrisable according to his information demands. Now, on a business trip to the south of Spain Mr M has to stop with a defect late at night. The workshop that is alarmed due to the 24-hours assistance service is somehow lost: this kind of defect is not listed in the technical service documentation and therefore not a standard service and repair routine. However, the immediate access to the hotline information service via the computer network identifies the same defect two days ago in Oregon/USA. The problem solution that the Spanish mechanic gets on his workshop screen is in English. So he activates the translation-on-demand button and receives a Spanish translation within a few seconds. This translation is not perfect, but the necessary repair steps and the terminology of the needed tools and parts is correct due to a multilingual terminology knowledge base which is maintained by the car manufacturer; therefore the mechanic does not care about the 'ser/estar' errors of the delivered Spanish text.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "Not every service information is available in all languages that are supported by the car manufacturer; the translation of service information is a matter of information need, but every available information is accessible through \"pull\" technology (for example, the hotline information service). Information of common interest is distributed in all languages through \"push\" technology; this ensures a fast and efficient update of all product documentation. The defect of Mr M's car is now available in English and Spanish (after a correction of the computer translation); after an in-depth analysis of the defect this information might become available in all supported languages.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "This scenario, which of course is partly a vision, shows the necessity of integrating services, documentation and networked information technology (IT) solutions with the support of modern, multilingual language technology (LT). The identified documentation bottlenecks and parts of this scenario then form the basis of the MULTIDOC vision of an Abstract Documentation Factory (ADF).", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Basic Requirements and Vision", |
|
"sec_num": "2." |
|
}, |
|
{ |
|
"text": "Within the Concerted Action a so-called virtual application was defined. It constitutes a compromise between the present situation of product documentation in the different automotive companies and the MULTIDOC vision of an ADF that is based on the concept of Translation Engineering. We talk about a virtual application because this application is based on the generalisation of the different processes and workflows maintained in the automotive product documentation environments of the MULTIDOC partners. For this we analysed the existing documentation processing chain and we identified the stages for initial improvements taking into account the historical evolution of product documentation. The sequential stages of today's documentation value cycle is profiled in Figure 1 below.", |
|
"cite_spans": [], |
|
"ref_spans": [ |
|
{ |
|
"start": 772, |
|
"end": 780, |
|
"text": "Figure 1", |
|
"ref_id": null |
|
} |
|
], |
|
"eq_spans": [], |
|
"section": "Translation Engineering", |
|
"sec_num": "3.1" |
|
}, |
|
{ |
|
"text": "This analysis led to the definition of a strategy for an efficient and effective employment of language technology to bridge the gap between the present situation in product documentation and the MULTIDOC vision. This strategy is based on the present situation and has to be maintained with various restrictions for the different automotive companies but with the common interest to work toward the ADF vision that is shared by all companies, however, with different ways to reach the vision.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 1: Today's Documentation Workflow", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "The virtual application is the result of the elaboration phase, and it allows for a smooth and cost effective transition of the business, because we have first and foremost concentrated on the existing process stages, where several control capabilities for the source language, such as spell, grammar and style checking functionality in the authoring stage, as well as the control of terminology consistency in the product data stage, the knowledge acquisition stage and the authoring stage, support the technical writer and other knowledge workers in identifying and defining information objects in an SGML authoring environment.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 1: Today's Documentation Workflow", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "In broad terms, an information object is either a meaningful, non decomposable SGML marked-up text unit or a composition of such text units. The virtual application shall already include steps toward Translation Engineering that is the operational foundation of the MULTIDOC vision. Translation Engineering (TE) as a business strategy is concerned with:", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 1: Today's Documentation Workflow", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "\u2022 Fostering the use of information objects preferably linked with product data to ensure the consistent use of information structure and information content. to shorten lead times and to further improve the quality of technical documentation. In addition, the core business and the component or system manufacturing industry benefits in terms of:", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 1: Today's Documentation Workflow", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "\u2022 accelerating the building of enterprise-wide and industry sector wide knowledge systems (repositories and knowledge bases) based on Web technology (intranets and extranets) including multimedia (text, graphics, video and animation, virtual reality) and multimodal (language and speech navigation) capabilities,", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 1: Today's Documentation Workflow", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "\u2022 improving the semantic content of information objects (accuracy and quality),", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 1: Today's Documentation Workflow", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "\u2022 speeding up of the translation processes (today, in limited cases the translation process could be substituted by multilingual generation and symbolic authoring, which in particular has to be seen in combination with controlled languages),", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 1: Today's Documentation Workflow", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "\u2022 reorganising of the overall production process (lean multilingual documentation).", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 1: Today's Documentation Workflow", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "A snapshot of this information distribution scenario is shown in Figure 2 below.", |
|
"cite_spans": [], |
|
"ref_spans": [ |
|
{ |
|
"start": 65, |
|
"end": 73, |
|
"text": "Figure 2", |
|
"ref_id": null |
|
} |
|
], |
|
"eq_spans": [], |
|
"section": "Figure 1: Today's Documentation Workflow", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "TE as such will revolutionise the current way of thinking in technical documentation because the whole documentation process is oriented toward multilingualism. This new business scenario includes a push/pull policy for technical information delivery and retrieval in an automotive dealer's workshop in combination with a translation-ondemand policy (see the scenario above). TE is responsive to the new business demands, and it will harmonise and unify the most crucial documentation requirements in areas such as the consistent use of technical information in structure and content, the efficient and effective reuse of information objects based on standardised information structures (increased retrieval hit-rates), and the terminological and multilingual orientation of the whole information production process.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 2: Information Distribution", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "Abstract Representation", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Product Definition Product Definition Representation", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "Multilingual SGML Representation", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Geometric Representation SGML Representation", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "The vision of the ADF comprises the complete re-organisation of the documentation processes. This means that LT in general, and specifically multilingual LT including translation technology, will make the move from a supporting technology to an enabling technology. The most important areas for this development are:", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Abstract Documentation Factory", |
|
"sec_num": "3.2" |
|
}, |
|
{ |
|
"text": "\u2022 Graphics and other multimedia incarnations, such as video, animation and virtual reality applications, may enrich or even replace text in certain information objects and facilitate new approaches to information production such as symbolic authoring.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Abstract Documentation Factory", |
|
"sec_num": "3.2" |
|
}, |
|
{ |
|
"text": "\u2022 Translation-on-demand policy to allow for an efficient and effective control of the actual translation needs, because not all information objects need to be stored in every language that is supported by the business (translation management).", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Abstract Documentation Factory", |
|
"sec_num": "3.2" |
|
}, |
|
{ |
|
"text": "\u2022 Compilation of documents from multilingual information objects, either already stored in a foreign language, translated on demand, or generated from an abstract representation; this allows for the simultaneous delivery (publishing) of multilingual documentation.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Abstract Documentation Factory", |
|
"sec_num": "3.2" |
|
}, |
|
{ |
|
"text": "The focus of the ADF is on the following three main components:", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Abstract Documentation Factory", |
|
"sec_num": "3.2" |
|
}, |
|
{ |
|
"text": "\u2022 Multilingual terminological ontology as a means for representing domain knowledge (the subject of technical documentation) linked with natural language semantics. Figure 3 below shows the different views on the ontology organisation at the upper level.", |
|
"cite_spans": [], |
|
"ref_spans": [ |
|
{ |
|
"start": 165, |
|
"end": 173, |
|
"text": "Figure 3", |
|
"ref_id": "FIGREF1" |
|
} |
|
], |
|
"eq_spans": [], |
|
"section": "Abstract Documentation Factory", |
|
"sec_num": "3.2" |
|
}, |
|
{ |
|
"text": "\u2022 Object Modelling Technique (OMT) as a theoretical foundation for analysis and design, and as an implementation platform based on distributed object environments such as, for example, CORBA.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Abstract Documentation Factory", |
|
"sec_num": "3.2" |
|
}, |
|
{ |
|
"text": "\u2022 Agent technology as the overall umbrella for construction, and as an alternative implementation platform, especially for networked applications.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Abstract Documentation Factory", |
|
"sec_num": "3.2" |
|
}, |
|
{ |
|
"text": "In the ADF, knowledge producer and knowledge consumer will operate in virtual environments brokered by software agents. A software agent acts autonomously on behalf of a person to fulfil the person's goal or task. Agents are also key enabler for push technology which is used in information update tasks and information retrieval tasks. ", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Abstract Documentation Factory", |
|
"sec_num": "3.2" |
|
}, |
|
{ |
|
"text": "All development strategies have been validated with a cost/benefit appraisal based on a hypothetical business calculation of a virtual automotive enterprise. We have taken this way to further maintain the generalisation direction which we already followed in the other phases of the Concerted Action. However, our profitability assessment is based on actual calculations made by the MULTIDOC partners for their specific enterprise situation. The validation stage also included a risk analysis consisting of:", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Validation", |
|
"sec_num": "3.3" |
|
}, |
|
{ |
|
"text": "\u2022 Critical analysis of our approach.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Validation", |
|
"sec_num": "3.3" |
|
}, |
|
{ |
|
"text": "\u2022 Analysis of changes to the human resources, the technical infrastructure and the organisational environment.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Validation", |
|
"sec_num": "3.3" |
|
}, |
|
{ |
|
"text": "\u2022 Identification of any restrictions, constraints, risks and problems hitherto not taken into account.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Validation", |
|
"sec_num": "3.3" |
|
}, |
|
{ |
|
"text": "In the following, we will demonstrate that the effective control of terminology helps to reduce costs at a very early stage of the documentation workflow. This is motivated by the costs that are needed to detect and repair a terminology error.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Validation", |
|
"sec_num": "3.3" |
|
}, |
|
{ |
|
"text": "Let us assume that a unit cost of one is assigned to the effort required to detect and repair an error during the authoring stage, then the cost to detect and repair an error during the data gathering, harmonisation (synchronisation between product data and product documentation) and documentation design stages (which are similar to the requirements stages in software engineering) is between five to ten times less. Furthermore, the cost to detect and repair an error during the maintenance stage is twenty times more. The reasons for this large difference is that many of these errors are not detected until well after they have been made. This delay in error discovery means that the cost to repair includes the ", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Validation", |
|
"sec_num": "3.3" |
|
}, |
|
{ |
|
"text": "cost to correct the offending error and to correct subsequent investments in the error. These investments include rework (perhaps redesign) of documentation, rewrite of related documentation, and the cost to rework or replace documentation in the field. Figure 44 below shows the cost pyramid of the different stages of error detection and correction.", |
|
"cite_spans": [], |
|
"ref_spans": [ |
|
{ |
|
"start": 254, |
|
"end": 263, |
|
"text": "Figure 44", |
|
"ref_id": null |
|
} |
|
], |
|
"eq_spans": [], |
|
"section": "Support_Object", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "This shows that errors made at early stages in the documentation workflow are extremely expensive to repair. If such error occurred infrequently, then the contribution to the overall documentation cost would not be significant. However, terminology errors are indeed a large class of errors typically found in complex technical documentation. These errors could be between 30 % and 70 % of the errors discovered in technical documentation.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 4: Cost Pyramid for Detecting and Correcting Terminology Errors", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "It seems reasonable to assume that a 20 % or more reduction in terminology errors can be accomplished at various levels of organisational maturity. Because of the multiplying effect, any such reduction can have a dramatic overall effect to our project's bottom line.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 4: Cost Pyramid for Detecting and Correcting Terminology Errors", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "The user groups who are in the focus of our work are, on the one hand, the knowledge producers of documentation departments and translation departments (technical writers and translators, designers and engineers, and so forth) and the knowledge consumers in the automotive workshops (mechanics and technicians).", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Figure 4: Cost Pyramid for Detecting and Correcting Terminology Errors", |
|
"sec_num": null |
|
}, |
|
{ |
|
"text": "Both approaches, \"bridging the gap\" and ADF, are centred around the MULTIDOC terminological ontology as the primary information source. The parallel development allows for an optimal use of resources, and permits a straight forward implementation of the ADF based on already existing LT modules and components. It should be noted that the ontology centric approach has several benefits which have an direct impact on the most important business demands in multilingual documentation. Among them the most significant ones are that it \u2022 supports harmonisation and standardisation between product data environments and \u2022 ensures better control of information object production, translation and deployment because of clearly defined responsibilities and quality assurance measures, including a transparent workflow control;", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Conclusions and Perspectives", |
|
"sec_num": "4" |
|
}, |
|
{ |
|
"text": "\u2022 fosters a better integration of supplier information and subsidiary information (core business as well as associated businesses);", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Conclusions and Perspectives", |
|
"sec_num": "4" |
|
}, |
|
{ |
|
"text": "\u2022 abandons the need of an end-control within the information object production value cycle because of the distributed responsibilities with an integrated control functionality;", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Conclusions and Perspectives", |
|
"sec_num": "4" |
|
}, |
|
{ |
|
"text": "\u2022 fits with existing and emerging networked computing environments, including advanced agent technology.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Conclusions and Perspectives", |
|
"sec_num": "4" |
|
}, |
|
{ |
|
"text": "More details on the project can be obtained from our web pages at URL:", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Conclusions and Perspectives", |
|
"sec_num": "4" |
|
}, |
|
{ |
|
"text": "http://www.iai.uni-sb.de/MULTIDOC.", |
|
"cite_spans": [], |
|
"ref_spans": [], |
|
"eq_spans": [], |
|
"section": "Conclusions and Perspectives", |
|
"sec_num": "4" |
|
} |
|
], |
|
"back_matter": [], |
|
"bib_entries": { |
|
"BIBREF0": { |
|
"ref_id": "b0", |
|
"title": "User-centred Design", |
|
"authors": [ |
|
{ |
|
"first": "Nigel", |
|
"middle": [], |
|
"last": "Bevan", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1996, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Bevan, Nigel (1996): User-centred Design. Deliverable D3.1.2 v1.2 of IE 2016 project INUSE.", |
|
"links": null |
|
}, |
|
"BIBREF1": { |
|
"ref_id": "b1", |
|
"title": "Software Agents", |
|
"authors": [ |
|
{ |
|
"first": "Jeffrey", |
|
"middle": [ |
|
"M" |
|
], |
|
"last": "Bradshaw", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Bradshaw, Jeffrey M. ed. (1997): Software Agents. AAAI Press/MIT Press, Cambridge, Massachusetts, USA.", |
|
"links": null |
|
}, |
|
"BIBREF2": { |
|
"ref_id": "b2", |
|
"title": "Good applications for crummy machine translation", |
|
"authors": [ |
|
{ |
|
"first": "Ken", |
|
"middle": [], |
|
"last": "Church", |
|
"suffix": "" |
|
}, |
|
{ |
|
"first": "Eduard", |
|
"middle": [], |
|
"last": "Hovy", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1993, |
|
"venue": "Machine Translation", |
|
"volume": "8", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Church, Ken and Hovy, Eduard (1993): Good applications for crummy machine translation. Machine Translation 8,", |
|
"links": null |
|
}, |
|
"BIBREF3": { |
|
"ref_id": "b3", |
|
"title": "Structuring Use Cases with Goals", |
|
"authors": [ |
|
{ |
|
"first": "Alistair", |
|
"middle": [], |
|
"last": "Cockburn", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Cockburn, Alistair (1997a): Structuring Use Cases with Goals. Web document at URL http://members.aol.com/cockburn/papers/usecases.htm.", |
|
"links": null |
|
}, |
|
"BIBREF4": { |
|
"ref_id": "b4", |
|
"title": "Using \"V-W\" Staging to Clarify Spiral Development", |
|
"authors": [ |
|
{ |
|
"first": "Alistair", |
|
"middle": [], |
|
"last": "Cockburn", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Cockburn, Alistair (1997b): Using \"V-W\" Staging to Clarify Spiral Development. Web document at URL http://members.aol.com/cockburn/papers/ vwstage.htm", |
|
"links": null |
|
}, |
|
"BIBREF5": { |
|
"ref_id": "b5", |
|
"title": "Developing Java Beans", |
|
"authors": [ |
|
{ |
|
"first": "Robert", |
|
"middle": [], |
|
"last": "Englander", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Englander, Robert (1997): Developing Java Beans. O'Reilly & Associates, Inc., Sepastopol, CA, USA.", |
|
"links": null |
|
}, |
|
"BIBREF6": { |
|
"ref_id": "b6", |
|
"title": "Java in a Nutshell", |
|
"authors": [ |
|
{ |
|
"first": "David", |
|
"middle": [], |
|
"last": "Flanagan", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1996, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Flanagan, David (1996): Java in a Nutshell. O'Reilly & Associates, Inc., Sepastopol, CA, USA.", |
|
"links": null |
|
}, |
|
"BIBREF7": { |
|
"ref_id": "b7", |
|
"title": "Java in a Nutshell", |
|
"authors": [ |
|
{ |
|
"first": "David", |
|
"middle": [], |
|
"last": "Flanagan", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Flanagan, David (1997): Java in a Nutshell. Second Edition covering Java 1.1, O'Reilly & Associates, Inc., Sepastopol, CA, USA.", |
|
"links": null |
|
}, |
|
"BIBREF8": { |
|
"ref_id": "b8", |
|
"title": "UML Distilled", |
|
"authors": [ |
|
{ |
|
"first": "Martin", |
|
"middle": [], |
|
"last": "Foyler", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Foyler, Martin (1997): UML Distilled. Addision Wesley Publishing Company, Reading, MA, USA.", |
|
"links": null |
|
}, |
|
"BIBREF9": { |
|
"ref_id": "b9", |
|
"title": "No mirrors and magic here -You can write common code for Unix and NT. Sunworld On-line", |
|
"authors": [ |
|
{ |
|
"first": "David", |
|
"middle": [], |
|
"last": "Herdman", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Herdman, David (1997): No mirrors and magic here -You can write common code for Unix and NT. Sunworld On-line, April issue and May issue.", |
|
"links": null |
|
}, |
|
"BIBREF10": { |
|
"ref_id": "b10", |
|
"title": "Document Management Beyond 2000: More of the Same, a Strategic Tool or Spider in the Web", |
|
"authors": [ |
|
{ |
|
"first": "Ian", |
|
"middle": [], |
|
"last": "Howells", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "Document World, Issue 1, IMC and AIIM publication", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Howells, Ian (1997): Document Management Beyond 2000: More of the Same, a Strategic Tool or Spider in the Web?. In: Document World, Issue 1, IMC and AIIM publication, Powerhouse Solutions Ltd., Surrey, England.", |
|
"links": null |
|
}, |
|
"BIBREF11": { |
|
"ref_id": "b11", |
|
"title": "The Clash of Civilizations", |
|
"authors": [ |
|
{ |
|
"first": "Samuel", |
|
"middle": [ |
|
"P" |
|
], |
|
"last": "Huntington", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1996, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Huntington, Samuel P. (1996): The Clash of Civilizations. Simon and Schuster, New York, USA.", |
|
"links": null |
|
}, |
|
"BIBREF12": { |
|
"ref_id": "b12", |
|
"title": "RESPECT User Requirements Framework Handbook. Deliverable D5.1 of Information Engineering (IE) 2010 project RESPECT", |
|
"authors": [ |
|
{ |
|
"first": "Martin", |
|
"middle": [], |
|
"last": "Maguire", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Maguire, Martin (1997): RESPECT User Requirements Framework Handbook. Deliverable D5.1 of Information Engineering (IE) 2010 project RESPECT. HUSAT Research Institute, Loughborough, UK.", |
|
"links": null |
|
}, |
|
"BIBREF13": { |
|
"ref_id": "b13", |
|
"title": "The Common Object Request Broker: Architecture and Specification Version", |
|
"authors": [], |
|
"year": 1995, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Object Management Group (1995): The Common Object Request Broker: Architecture and Specification Version 2.0", |
|
"links": null |
|
}, |
|
"BIBREF14": { |
|
"ref_id": "b14", |
|
"title": "The Essential Distributed Objects Survival Guide", |
|
"authors": [ |
|
{ |
|
"first": "Robert", |
|
"middle": [], |
|
"last": "Orfali", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1996, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Orfali, Robert et al. (1996): The Essential Distributed Objects Survival Guide. John Wiley & Sons, Inc., New York, NY, USA.", |
|
"links": null |
|
}, |
|
"BIBREF15": { |
|
"ref_id": "b15", |
|
"title": "Client/Server Programming with Java and CORBA", |
|
"authors": [ |
|
{ |
|
"first": "Robert", |
|
"middle": [], |
|
"last": "Orfali", |
|
"suffix": "" |
|
}, |
|
{ |
|
"first": "Dan", |
|
"middle": [], |
|
"last": "Harkey", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Orfali, Robert and Harkey, Dan (1997): Client/Server Programming with Java and CORBA. John Wiley & Sons, Inc., New York, NY, USA.", |
|
"links": null |
|
}, |
|
"BIBREF16": { |
|
"ref_id": "b16", |
|
"title": "Ovum Evaluates: Document Management. Ovum Ltd", |
|
"authors": [ |
|
{ |
|
"first": "Heather", |
|
"middle": [], |
|
"last": "Stark", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1996, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Stark, Heather, et al. (1996): Ovum Evaluates: Document Management. Ovum Ltd, London, England.", |
|
"links": null |
|
}, |
|
"BIBREF17": { |
|
"ref_id": "b17", |
|
"title": "Database Programming with JDBC and Java", |
|
"authors": [ |
|
{ |
|
"first": "George", |
|
"middle": [], |
|
"last": "Reese", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Reese, George (1997): Database Programming with JDBC and Java. O'Reilly & Associates, Inc., Sepastopol, CA, USA.", |
|
"links": null |
|
}, |
|
"BIBREF18": { |
|
"ref_id": "b18", |
|
"title": "Combining Language Technology and Web Technology to Streamline an Automotive Hotline Support Service", |
|
"authors": [ |
|
{ |
|
"first": "J\u00f6rg", |
|
"middle": [], |
|
"last": "Sch\u00fctz", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1996, |
|
"venue": "Proceedings of AMTA-96", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Sch\u00fctz, J\u00f6rg (1996a): Combining Language Technology and Web Technology to Streamline an Automotive Hotline Support Service. In Proceedings of AMTA-96, Montreal, Canada.", |
|
"links": null |
|
}, |
|
"BIBREF19": { |
|
"ref_id": "b19", |
|
"title": "Network-based Machine Translation Service", |
|
"authors": [ |
|
{ |
|
"first": "J\u00f6rg", |
|
"middle": [], |
|
"last": "Sch\u00fctz", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1996, |
|
"venue": "Proceedings of the EAMT Machine Translation Workshop", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Sch\u00fctz, J\u00f6rg (1996b):. Network-based Machine Translation Service. In: Proceedings of the EAMT Machine Translation Workshop, Vienna, Austria.", |
|
"links": null |
|
}, |
|
"BIBREF20": { |
|
"ref_id": "b20", |
|
"title": "Utilizing Evaluation in Networked Machine Translation", |
|
"authors": [ |
|
{ |
|
"first": "J\u00f6rg", |
|
"middle": [], |
|
"last": "Sch\u00fctz", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1997, |
|
"venue": "Proceedings of TMI 97", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Sch\u00fctz, J\u00f6rg (1997): Utilizing Evaluation in Networked Machine Translation. In Proceedings of TMI 97, Santa Fe, New Mexico, USA.", |
|
"links": null |
|
}, |
|
"BIBREF21": { |
|
"ref_id": "b21", |
|
"title": "Conceptual Structures: Information Processing in Mind and Machine", |
|
"authors": [ |
|
{ |
|
"first": "John", |
|
"middle": [ |
|
"F" |
|
], |
|
"last": "Sowa", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1984, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Sowa, John F. (1984): Conceptual Structures: Information Processing in Mind and Machine. Addision Wesley Publishing Company, Reading, MA, USA.", |
|
"links": null |
|
}, |
|
"BIBREF22": { |
|
"ref_id": "b22", |
|
"title": "Knowledge Representation: Logical, Philosophical and Computational Foundation", |
|
"authors": [ |
|
{ |
|
"first": "John", |
|
"middle": [ |
|
"F" |
|
], |
|
"last": "Sowa", |
|
"suffix": "" |
|
} |
|
], |
|
"year": null, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Sowa, John F. (to appear): Knowledge Representation: Logical, Philosophical and Computational Foundation. To be published by PWS Publishing Company.", |
|
"links": null |
|
}, |
|
"BIBREF23": { |
|
"ref_id": "b23", |
|
"title": "Harmonization of SGML and STEP. ISO (TC 184/SC4/WG3/T14 Product Documentation) STEP/SGML Tutorial", |
|
"authors": [ |
|
{ |
|
"first": "Hugh", |
|
"middle": [ |
|
"A" |
|
], |
|
"last": "Tucker", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1996, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Tucker, Hugh A. (1996): Harmonization of SGML and STEP. ISO (TC 184/SC4/WG3/T14 Product Documentation) STEP/SGML Tutorial.", |
|
"links": null |
|
}, |
|
"BIBREF24": { |
|
"ref_id": "b24", |
|
"title": "Unified Modelling Language (UML) Documentation, Version 1.0. Rational Software Corporation", |
|
"authors": [], |
|
"year": 1997, |
|
"venue": "UML", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "UML (1997): Unified Modelling Language (UML) Documentation, Version 1.0. Rational Software Corporation, Santa Clara, California, USA. Available on the Web at URL http://www.rational.com.", |
|
"links": null |
|
}, |
|
"BIBREF25": { |
|
"ref_id": "b25", |
|
"title": "The Unicode Standard: World-wide Character Encoding", |
|
"authors": [ |
|
{ |
|
"first": "", |
|
"middle": [], |
|
"last": "Unicode", |
|
"suffix": "" |
|
} |
|
], |
|
"year": 1996, |
|
"venue": "", |
|
"volume": "", |
|
"issue": "", |
|
"pages": "", |
|
"other_ids": {}, |
|
"num": null, |
|
"urls": [], |
|
"raw_text": "Unicode (1996): The Unicode Standard: World-wide Character Encoding. Addison-Wesley Publishing Company, Reading, MA, USA.", |
|
"links": null |
|
} |
|
}, |
|
"ref_entries": { |
|
"FIGREF0": { |
|
"uris": null, |
|
"text": "Optimising the translation production chain through the employment of different multilingual language technologies, including multilingual generation.\u2022 Linking of source language information and target language information to facilitate better maintenance, quality assurance and quality control. TE as a methodology for multilingual documentation will help to drastically reduce cost,", |
|
"num": null, |
|
"type_str": "figure" |
|
}, |
|
"FIGREF1": { |
|
"uris": null, |
|
"text": "Different Views on the Ontology", |
|
"num": null, |
|
"type_str": "figure" |
|
} |
|
} |
|
} |
|
} |