DOCSLIB.ORG

Should S1000D Be Required by the Department of Defense?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Should S1000D Be Required by the Department of Defense? View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Calhoun, Institutional Archive of the Naval Postgraduate School Calhoun: The NPS Institutional Archive Reports and Technical Reports All Technical Reports Collection 2010 Should S1000D be required by the Department of Defense? Blais, Curtis L. Monterey, California. Naval Postgraduate School http://hdl.handle.net/10945/823 NPS-MV-10-002 NAVAL POSTGRADUATE SCHOOL MONTEREY, CALIFORNIA Should S1000D be Required by the Department of Defense? by Curtis L. Blais, John S. Falby and Michael E. McCauley 27 August 2010 Approved for public release; distribution is unlimited Prepared for: Office of the Undersecretary of Defense for Personnel and Readiness 1901 N. Beauregard Street, Suite 600 Alexandria, VA 22311 THIS PAGE INTENTIONALLY LEFT BLANK NAVAL POSTGRADUATE SCHOOL Monterey, California 93943-5000 Daniel T. Oliver Leonard A. Ferrari President Executive Vice President and Provost This report was prepared for, and funded by, the Office of the Undersecretary of Defense for Personnel and Readiness. Reproduction of all or part of this report is authorized. This report was prepared by: _______________________ ______________________ ______________________ Curt L. Blais John S. Falby Michael E. McCauley Research Associate Senior Lecturer Research Professor Modeling, Virtual Department of Department of Environments and Simulation Computer Science Operations Research (MOVES) Institute Naval Postgraduate School Naval Postgraduate School Naval Postgraduate School Reviewed by: _______________________ Joseph A. Sullivan, Director Modeling, Virtual Environments and Simulation (MOVES) Institute Released by: ______________________ Karl A. van Bibber Vice President and Dean of Research THIS PAGE INTENTIONALLY LEFT BLANK Form Approved REPORT DOCUMENTATION PAGE OMB No. 0704-0188 Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing this collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS. 1. REPORT DATE 2. REPORT TYPE 3. DATES COVERED (From - To) 27-08-2010 Technical Report Oct 2009 - May 2010 4. TITLE AND SUBTITLE 5a. CONTRACT NUMBER Should S1000D be Required by the Department of Defense? XJ9H5R9XT376MP 5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER 6. AUTHOR(S) 5d. PROJECT NUMBER Blais, Curt L. Falby, John S. 5e. TASK NUMBER McCauley, Michael E. 5f. WORK UNIT NUMBER 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION Naval Postgraduate School REPORT NUMBER Modeling, Virtual Environments and Simulation (MOVES) NPS-MV-10-002 Institute 700 Dyer Road, Watkins Extension Room 265 Monterey, CA 93943-5001 9. SPONSORING / MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S) Office of the Undersecretary of Defense for OUSD (P&R) Personnel and Readiness 11. SPONSOR/MONITOR’S REPORT 1901 N. Beauregard Street, Suite 600 NUMBER(S) Alexandria, VA 22311 12. DISTRIBUTION / AVAILABILITY STATEMENT Approved for public release; distribution is unlimited 13. SUPPLEMENTARY NOTES 14. ABSTRACT The purpose of this analysis was to determine whether S1000D, an international specification for technical publications, should be required in Department of Defense (DoD) acquisitions. Based on the information and opinions gathered from nearly 200 participants in the study, we conclude that S1000D should be a required standard for technical publications across the DoD. This action should be taken in conjunction with a program to implement, transition, and promote its success. This program would include a set of critical provisions for DoD to: (1) manage/govern the use of the standard; (2) promote the use of the standard; (3) support adoption and evolution of the standard; and (4) establish and enforce use of the standard. 15. SUBJECT TERMS S1000D, technical publication specification, common source database, DoD aquisitions 16. SECURITY CLASSIFICATION OF: 17. LIMITATION 18. NUMBER 19a. NAME OF RESPONSIBLE PERSON OF ABSTRACT OF PAGES Michael McCauley a. REPORT b. ABSTRACT c. THIS PAGE 19b. TELEPHONE NUMBER (include area code) SAR U U U (831) 656-2191 Standard Form 298 (Rev . 8-98) Prescribed by ANSI Std. Z39.18 i THIS PAGE INTENTIONALLY LEFT BLANK ii ABSTRACT The purpose of this analysis was to determine whether S1000D, an international specification for technical publications, should be required in Department of Defense (DoD) acquisitions. Based on the information and opinions gathered from nearly 200 participants in the study, we conclude that S1000D should be a required standard for technical publications across the DoD. This action should be taken in conjunction with a program to implement, transition, and promote its success. This program would include a set of critical provisions for DoD to: (1) manage/govern the use of the standard; (2) promote the use of the standard; (3) support adoption and evolution of the standard; and (4) establish and enforce use of the standard. iii THIS PAGE INTENTIONALLY LEFT BLANK iv TABLE OF CONTENTS I. INTRODUCTION........................................................................................................1 A. PURPOSE.........................................................................................................1 B. BACKGROUND ..............................................................................................1 II. TECHNICAL OVERVIEW OF S1000D...................................................................5 A. STRUCTURED DATA....................................................................................5 B. DATA MODULES...........................................................................................6 C. SOFTWARE TOOLS......................................................................................9 D. BUSINESS RULES..........................................................................................9 E. S1000D GOVERNANCE...............................................................................12 1. S1000D Sponsors................................................................................12 2. S1000D Council ..................................................................................13 3. Working Groups and Task Teams ...................................................14 III. METHODS .................................................................................................................15 A. OVERVIEW...................................................................................................15 B. STRUCTURED INTERVIEWS...................................................................15 C. SURVEY QUESTIONNAIRE ......................................................................17 IV. STRUCTURED INTERVIEW RESULTS..............................................................19 A. SAMPLE SIZE...............................................................................................19 B. RESULTS .......................................................................................................19 1. Benefits................................................................................................19 2. Challenges and Issues ........................................................................24 3. Should S1000D be a DoD Requirement? .........................................27 4. DoD Actions Needed to Promote Successful Implementation of S1000D ................................................................................................30 V. QUESTIONNAIRE SURVEY RESULTS...............................................................35 A. SAMPLE SIZE AND SOURCE ...................................................................35 B. RESULTS .......................................................................................................36 1. Benefits................................................................................................36 2. Key Question: Should S1000D be Required?..................................36 3. Potential Drawbacks..........................................................................38 4. Contributing Activities by DoD ........................................................38 VI. RECOMMENDATIONS...........................................................................................41 REFERENCES .....................................................................................................................43 APPENDIX A - STRUCTURED INTERVIEW .................................................................45 APPENDIX B - QUESTIONNAIRE SURVEY ..................................................................51 APPENDIX C - ADDITIONAL EXCERPTS FROM THE STRUCTURED INTERVIEWS............................................................................................................55
Load more

Recommended publications
  • Managing Writers
    Managing Writers Sample Chapter -- Measurement and Metrics Richard L. Hamilton Managing Writers Copyright © 2009 Richard L. Hamilton All rights reserved. No part of this book may be reproduced or transmitted in any form or by any means without the prior written permission of the copyright holder, except for the inclusion of brief quotations in a review. This sample ebook may be distributed freely, but may not be sold in any form. Except for brief quotations in a review, any distribution must include the full copyright and all legal notices. Disclaimer The information in this book is provided on an “as is” basis, without warranty. While every effort has been taken by the author and XML Press in the prepara- tion of this book, the author and XML Press shall have neither liability nor re- sponsibility to any person or entity with respect to any loss or damages arising from the information contained in this book. This book contains links to third-party web sites that are not under the control of the author or XML Press. The author and XML Press are not responsible for the content of any linked site. Inclusion of a link in this book does not imply that the author or XML Press endorses or accepts any responsibility for the content of that third-party site. Trademarks XML Press and the XML Press logo are trademarks of XML Press. All terms mentioned in this book that are known to be trademarks or service marks have been capitalized as appropriate. Use of a term in this book should not be regarded as affecting the validity of any trademark or service mark.
    [Show full text]
  • Alles-Standard-Oder-Was.Pdf
    Alles Standard oder was? Welche technischen Standards Sie für intelligente Informationen brauchen tekom Jahrestagung 2020 © parson AG und Empolis GmbH | 2020 2. November 2020 U. Parson / M. Kreutzer Alles Standard oder was? – Welche technischen Standards Sie für intelligente Informationen brauchen 1 Ulrike Parson Dr. Martin Kreutzer Vorstand Principal Solution Engineer parson AG Empolis Information Management GmbH [email protected] [email protected] www.parson-europe.com www.empolis.com © parson AG und Empolis GmbH | 2020 2. November 2020 U. Parson / M. Kreutzer Alles Standard oder was? – Welche technischen Standards Sie für intelligente Informationen brauchen 2 Intelligente Informationen Eine Frage der Perspektive © parson AG und Empolis GmbH | 2020 2. November 2020 U. Parson / M. Kreutzer Alles Standard oder was? – Welche technischen Standards Sie für intelligente Informationen brauchen 3 Warum machen wir das? • Intelligente Informationen in Dokumentation, Marketing und Service ergänzen smarte Applikationen, Komponenten und Anlagen • Inhalte müssen genauso vernetzbar sein wie Dienste und Komponenten • Inhalte werden modular, kontextabhängig und auf verschiedenen Endgeräten genutzt • Gute und smarte Inhalte können Mehrwerte schaffen © parson AG und Empolis GmbH | 2020 2. November 2020 U. Parson / M. Kreutzer Alles Standard oder was? – Welche technischen Standards Sie für intelligente Informationen brauchen 4 Umstellung auf intelligente Informationen ist aufwändig Authoring • Zusammenführung von Inhalten aus verschiedenen
    [Show full text]
  • What It Is and Why It Matters
    Dynamic Delivery What it is and why it matters - White Paper Series - DYNAMIC DELIVERY Why we need it When you search for information, you are seeking insight. You gain insight when your information is contextual and complete. Contextual because it adapts to you and to the device you’re using. Because it focuses on precisely what you want, and understands what you need Content published as static based on the task you are trying to achieve. documents is incompatible with processes and apps Complete because you can see through formats needed to enhance and across silos—content, structured or not, from productivity. any relevant source in an organization, delivered uniformly, consistently, and immediately. You gain insight when you find precisely what you want, avoid the irrelevant, yet are offered intelligent suggestions of alternate pathways of learning. This is the goal of dynamic content delivery, or Customer Field Self-service 360 dynamic publishing. Support Maintenance Portal Product Info In the following pages we explore the principles It is impossible to make it and benefits of dynamic delivery. It will help you feed next gen interaction understand why you must seriously consider it, and channels. how to choose a solution. In-device, Heads-up Chatbot, Inline Help Display, AR Virtual Agent 2 DYNAMIC DELIVERY What it is Static publishing, what we’re Dynamic publishing delivers Content Maturity Level used to since the dawn of printing, personalized, customized, on-the- is pre-generated, one-size-fits- fly documentation. Content stored in static PDF files, all, always the same. You get one Static only full documents can be viewed It gives results that are more Content manual for a product, regardless or downloaded Findable, more Readable, more of its customizations or the Shareable, and more Interactive.
    [Show full text]
  • Integrated Product Support (IPS) Elements Guidebook Has Now Also Been Extensively Updated to Reflect Current Policy and Guidance
    Product Support Management IPS Elements Guidebook Forward In October 2009, Section 805 of Public Law 111-84 established the key leadership position of Product Support Manager (PSM) and reiterated DoD’s commitment to life cycle product support management. By 2010, the Office of the Assistant Secretary of Defense (ASD) Logistics and Materiel Readiness (L&MR) concluded the seminal work to develop and implement a Product Support Business Model (PSBM) and published a series of Guidebooks to assist the Product Support Manager (PSM) in the execution of his or her duties. These Guidebooks included the “DoD Product Support Manager Guidebook”, the “DoD Product Support Business Case Assessment (BCA) Guidebook” and the “DoD Logistics Assessment (LA) Guidebook”. Since 2010, the existing Product Support Guidebooks have been updated and a few new ones have been developed to fill information gaps. This Integrated Product Support (IPS) Elements Guidebook has now also been extensively updated to reflect current policy and guidance. It picks up where the Product Support Manager Guidebook Appendix A left off in describing the 12 IPS Elements. Program Managers, Product Support Managers and Life Cycle Logisticians should use this Guidebook as a reference source and training aid supporting their responsibilities, tailored to the needs of each program. The term “Integrated” in the term “Integrated Product Support Element” is critical. The Product Support Manager must understand how each element is affected by and linked with the others and should employ all
    [Show full text]
  • Adaptive Fault Diagnosis in Interactive Electronic Technical Manuals (Ietms)
    Graduate Theses, Dissertations, and Problem Reports 2003 Adaptive fault diagnosis in interactive electronic technical manuals (IETMs) Rabih Faysal Kraidli West Virginia University Follow this and additional works at: https://researchrepository.wvu.edu/etd Recommended Citation Kraidli, Rabih Faysal, "Adaptive fault diagnosis in interactive electronic technical manuals (IETMs)" (2003). Graduate Theses, Dissertations, and Problem Reports. 1325. https://researchrepository.wvu.edu/etd/1325 This Thesis is protected by copyright and/or related rights. It has been brought to you by the The Research Repository @ WVU with permission from the rights-holder(s). You are free to use this Thesis in any way that is permitted by the copyright and related rights legislation that applies to your use. For other uses you must obtain permission from the rights-holder(s) directly, unless additional rights are indicated by a Creative Commons license in the record and/ or on the work itself. This Thesis has been accepted for inclusion in WVU Graduate Theses, Dissertations, and Problem Reports collection by an authorized administrator of The Research Repository @ WVU. For more information, please contact [email protected]. Adaptive Fault Diagnosis in Interactive Electronic Technical Manuals (IETMs) Rabih F. Kraidli Thesis Submitted to the College of Engineering and Mineral Resources at West Virginia University in partial fulfillment of the requirements for the degree of Master of Science In Computer Science Hany H. Ammar, Ph.D., Chair Katerina Goseva-Popstojanova, Ph.D. Don Reynolds, Technical Director, ManTech Enterprise Integration Center Lane Department of Computer Science and Electrical Engineering Morgantown, West Virginia University 2003 Keywords: IETM, Web Services, Adaptive Fault Diagnosis, User Modeling Copyright 2003 Rabih Kraidli ABSTRACT Adaptive Fault Diagnosis in Interactive Electronic Technical Manuals (IETMs) Rabih F.
    [Show full text]
  • Qué Son Los Formatos De Archivo Implicados En La Localización?
    I. Fundamentos 1. ¿Qué son los formatos de archivo implicados en la localización? En general, un formato de archivo implicado en la localización se puede definir como el diseño y la organización de los datos de un archivo usado para la localización de componentes de software. Al usar herramientas de TAO y de software en un proyecto de localización, los formatos de archivo implicados en la localización se importan como achivos de origen al principio del proyecto. Con el fin de trabajar con los formatos de archivo de localización para localizar componentes de software, primero es necesario distinguir entre texto traducible y no traducible contenido en los archivos. Para ello, es importante considerar que según qué componentes del software se deban localizar (interfaz de usuario, sitios web, archivo de ayuda o documentación impresa), los formatos de archivo implicados en la localización pueden variar. 2. Tipos de formato de archivo implicados en la localización 2.1 Según los componentes de software Los componentes de software (el software y la documentación) se crean usando distintas aplicaciones informáticas basadas en distintos lenguajes de programación. Como resultado, tienen formatos de archivo distintos. Por ejemplo, con las interfaces de usuario de software, los datos pueden comprender no sólo texto (datos localizables), sino también código de programa, código fuente o código de recursos, una secuencia de instrucciones escritas en un lenguaje de programación legible por el ser humano. En el caso de la documentación, como los sitios web y los archivos de ayuda, el texto traducibles puede estar enmarcado entre etiquetas de diseño. Algunos de los formatos posibles para los distintos componentes de software son: Software: Archivos de programa: Archivos RC files y .exe procedentes de distintos entornos de programación, como Borland Delphi, Java, XML, .NET, Visual Basic o archivos en formatos de metalocalización como .po, XLIFF, etc.
    [Show full text]
  • Database Publishing in Adobe Framemaker 11
    Adobe® FrameMaker® 11 White Paper Database Publishing in Adobe FrameMaker 11 Introduction Contents Database publishing is important for businesses of all sizes in all industries. Every enterprise needs to 1 Introduction distribute information internally and externally. From company phone directories to online product catalogs 2 Applications of server- to 3D media content, database publishing enables timely, effective communication. A well-implemented based publishing database publishing system can help companies reduce the time and expenses associated with publishing 5 Document types and improve information quality. 8 Data sources 9 The FrameMaker What is database publishing? database publishing solution Database publishing is a form of automated media production in which source data resides in traditional databases 11 Implementing a (in the form of text, pictures, and metadata related to formatting and special rules regarding document generation). FrameMaker solution The data is then aggregated and converted into multiple formats for publication and distribution. Such formats 16 Next steps include Adobe Portable Document Format (PDF) and Hypertext Markup Language (HTML), including HTML5, for 18 Conclusion the Internet, ePub, and Kindle formats, help outputs for online help systems, Extensible Markup Language (XML), which can be delivered to VoiceXML browsers and mobile devices, and formats for native apps that can be viewed on mobile devices without an Internet connection. The goal for many organizations is to create content once and publish it across multiple formats. Through Adobe Technical Communication Suite 4, FrameMaker can also publish to multiscreen HTML5 for delivery on mobile devices such as tablet computers and smartphones. Database publishing occurs in two broad categories: automated, tagged publishing or data-driven, dynamic publishing.
    [Show full text]
  • Smart Content in the Enterprise
    Research Report Smart Content in the Enterprise How Next Generation XML Applications Deliver New Value to Multiple Stakeholders August 2010 by Geoffrey Bock, Dale Waldt, and Mary Laplante Smart Content in the Enterprise The Gilbane Group gratefully acknowledges the support of the sponsors of the research informing this report. This work would not have been possible without them. Please see the Sponsor Acknowledgement section for descriptions of providers. 2010 Gilbane Group, a Division of Outsell, Inc. 83 Gilbane Group A Division of Outsell, Inc. 763 Massachusetts Avenue Cambridge, MA 02139 USA Tel: 617.497.9443 Fax: 617.497.5256 [email protected] http://gilbane.com 2010 Gilbane Group, a Division of Outsell, Inc. ii Table of Contents Executive Summary .......................................................................................... iv Study Highlights................................................................................................. 2 Why “Smart” Content? ....................................................................................... 3 Using This Report .............................................................................................. 4 New Value Propositions for Content .................................................................. 6 Connecting Content with Business Levers ......................................................... 6 Characterizing Smart Content ........................................................................... 8 The Business Value of “Smart” .........................................................................
    [Show full text]
  • Tekom-Jahrestagung 2017 Tagungsablauf Highlights Inhaltsverzeichnis
    Der internationale Branchen- Programmtreffpunkt rund um die Technische Kommunikation 2017The world‘s largest international Der internationaleconference inBranchen- technical treffpunktcommunication rund um die Technische Kommunikation ICS ICS Stuttgart Stuttgart 24. 24. – 26. – 26. Oktober Oktober 2017 2017 #tekom #tekom#tcworld Tagung Conference Liebe Konferenzteilnehmer, Montag, 23.10. Mittwoch, 25.10. seit vielen Jahren trifft sich die Branche im Einlass ab 7:30 Herbst auf der tekom-Jahrestagung, um ihre Rahmenprogramm Vorträge, Tutorials gemeinsamen Interessen in den Mittelpunkt Besichtigung der 14:15 – 18:15 und Workshops 8:45 – 18:00 zu stellen, die Professiona lisierung voranzu- Festo Technologiefabrik Branchenforum 10:00 – 17:00 Serviceinformation Halle C1 treiben sowie die Aus- und Weiterbildung in Messe 9:00 – 18:00 der Technischen Kommunikation internatio- Hallen C1 und C2, Foyer nal zu stärken. Dienstag, 24.10. Tool-Präsentationen 9:45 – 18:00 In diesem Jahr gibt es eine Rekordzahl an Einlass ab 7:30 Raum C10.1–C10.5, Zugang über Halle C2 Vortragseinreichungen. Dies zeigt, welchen Begrüßung der 8:30 – 8:45 Tagungsteilnehmer Mitgliederversammlung wichtigen Stellenwert die Tagung als Plenum 1 (nur für tekom-Mitglieder) 14:00 – 15:30 Branchentreffpunkt hat. Die Bandbreite an Vorträge, Tutorials 8:45 – 18:00 Raum C5.2 OG Themen spiegelt die Vielfalt unseres Arbeits- und Workshops DokuSlam 17:00 – 18:00 VIP Lounge feldes. Ein Schwerpunkt ist dabei der Branchenforum Lernmedien 10:00 – 17:00 Halle C1 Standard iiRDS, an dem die tekom im Sinne Messe 9:00 – 18:00 Rahmenprogramm einer Vernetzung über Systemgrenzen Hallen C1 und C2, Foyer International hinweg arbeitet und über dessen Stand in Tool-Präsentationen 9:45 – 18:00 Networking Event ab 18:00 den verschiedensten Facetten hier berichtet Raum C10.1–C10.5, mit der tekom Allstar Band Zugang über Halle C2 Plenum 2 wird.
    [Show full text]
  • Documenting and Implementing Guidelines with Schematron
    Documenting and Implementing Guidelines with Schematron Joshua Lubell <[email protected]> Abstract Data exchange specifications must be broad and general in order to achieve acceptance, yet they must also be customizable in a controlled and interoperable manner in order to be useful. This paper describes an approach employing the Schematron language and literate programming ideas for developing the guidelines needed to effectively use data exchange specifications. Table of Contents Why Guidelines? ................................................................................................................ 1 Implementing Guidelines with Schematron ............................................................................. 3 A Literate Programming Approach ........................................................................................ 4 The NDRProfile Experience ................................................................................................. 7 Discussion ......................................................................................................................... 8 References ....................................................................................................................... 10 Why Guidelines? Data exchange specifications for electronic business (e-business) applications describe in a computer- interpretable fashion the information to be transferred between systems. Thanks to the ubiquity and success of the Extensible Markup Language [XML] as an implementation technology, these
    [Show full text]
  • Analysis of Standards for Lifecycle Management of Systems for US Army --- a Preliminary Investigation
    NISTIR 7339 Analysis of Standards for Lifecycle Management of Systems for US Army --- a preliminary investigation Sudarsan Rachuri Sebti Foufou Sharon Kemmerer NISTIR 7339 Analysis of Standards for Lifecycle Management of Systems for US Army --- a preliminary investigation Sudarsan Rachuri Sebti Foufou Sharon Kemmerer August 2006 U.S. DEPARTMENT OF COMMERCE Carlos M. Gutierrez, Secretary TECHNOLOGY ADMINISTRATION Michelle O'Neill, Acting Under Secretary of Commerce for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY William Jeffrey, Director Analysis of Standards for Lifecycle Management of Systems for US Army --- a preliminary investigation Executive summary The need to exchange data among multiple business partners, developers, suppliers, users, and maintainers is the normal day-to-day complex business environment for the U.S. Army and other Department of Defense (DoD) Services. Product lifecycle management (PLM) is a function or a business strategy for creating, sharing, validating, and managing information about product, process, people, and services within and across the extended and networked enterprise covering the entire product lifecycle spectrum. A number of institutions including the National Institute of Standards and Technology (NIST), Department of Defense (DoD), the European Ministries of Defense and, more recently, by the vendor and end-user communities have recognized the importance of interoperability across the phases and functions in PLM. A 1999 study commissioned by NIST estimated that imperfect interoperability of engineering data costs at least $1 billion per year to the members of the U.S. automotive supply chain. By far, the greatest component of these costs is the resources devoted to repairing or reentering data files that are not usable for downstream applications.
    [Show full text]
  • Diseño Metodológico De Una Ontología En Geografía a Partir De
    Universidad de La Salle Ciencia Unisalle Sistemas de Información, Bibliotecología y Archivística Escuela de Humanidades y Estudios Sociales 5-2016 Diseño metodológico de una ontología en geografía a partir de términos de representación del conocimiento del diccionario geográfico de Colombia sobre el municipio de La Calera Cristhian Camilo Torres Galindo Universidad de La Salle, Bogotá Follow this and additional works at: https://ciencia.lasalle.edu.co/sistemas_informacion_documentacion Part of the Library and Information Science Commons Citación recomendada Torres Galindo, C. C. (2016). Diseño metodológico de una ontología en geografía a partir de términos de representación del conocimiento del diccionario geográfico de Colombia sobre el municipio de La Calera. Retrieved from https://ciencia.lasalle.edu.co/sistemas_informacion_documentacion/127 This Trabajo de grado - Pregrado is brought to you for free and open access by the Escuela de Humanidades y Estudios Sociales at Ciencia Unisalle. It has been accepted for inclusion in Sistemas de Información, Bibliotecología y Archivística by an authorized administrator of Ciencia Unisalle. For more information, please contact [email protected]. DISEÑO METODOLÓGICO DE UNA ONTOLOGÍA EN GEOGRAFÍA A PARTIR DE TÉRMINOS DE REPRESENTACIÓN DEL CONOCIMIENTO DEL DICCIONARIO GEOGRÁFICO DE COLOMBIA SOBRE EL MUNICIPIO DE LA CALERA. CRISTHIAN CAMILO TORRES GALINDO UNIVERSIDAD DE LA SALLE FACULTAD DE CIENCIAS ECONÓMICAS Y SOCIALES PROGRAMA DE SISTEMAS DE INFORMACIÓN Y DOCUMENTACIÓN BOGOTÁ 2016 1 DISEÑO METODOLÓGICO DE UNA ONTOLOGÍA EN GEOGRAFÍA A PARTIR DE TÉRMINOS DE REPRESENTACIÓN DEL CONOCIMIENTO DEL DICCIONARIO GEOGRÁFICO DE COLOMBIA SOBRE EL MUNICIPIO DE LA CALERA. CRISTHIAN CAMILO TORRES GALINDO Tesis de grado para optar por el título: Profesional en Sistemas de Información, Bibliotecología y Archivística DIRECTOR EDWIN SOSSA UNIVERSIDAD DE LA SALLE FACULTAD DE CIENCIAS ECONÓMICAS Y SOCIALES PROGRAMA DE SISTEMAS DE INFORMACIÓN Y DOCUMENTACIÓN BOGOTÁ D.C.
    [Show full text]