A Flexible XML-Based Glossary Approach for the Federal Government

Slides:



Advertisements
Similar presentations
DOCUMENT TYPES. Digital Documents Converting documents to an electronic format will preserve those documents, but how would such a process be organized?
Advertisements

Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Thesaurus Design and Development
Integrating data sources on the World-Wide Web Ramon Lawrence and Ken Barker U. of Manitoba, U. of Calgary
RDF Kitty Turner. Current Situation there is hardly any metadata on the Web search engine sites do the equivalent of going through a library, reading.
Software Requirements
Methodology Conceptual Database Design
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Requirements engineering l The process of establishing the services that the.
BIS310: Week 7 BIS310: Structured Analysis and Design Data Modeling and Database Design.
ECA 228 Internet/Intranet Design I Intro to XML. ECA 228 Internet/Intranet Design I HTML markup language very loose standards browsers adjust for non-standard.
INTRODUCTION TO DATABASE USING MS ACCESS 2013 PART 2 NOVEMBER 4, 2014.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Towards Translating between XML and WSML based on mappings between.
Concepts and Terminology Introduction to Database.
Lecture Four: Steps 3 and 4 INST 250/4.  Does one look for facts, or opinions, or both when conducting a literature search?  What is the difference.
A GENERIC PROCESS FOR REQUIREMENTS ENGINEERING Chapter 2 1 These slides are prepared by Enas Naffar to be used in Software requirements course - Philadelphia.
Nancy Lawler U.S. Department of Defense ISO/IEC Part 2: Classification Schemes Metadata Registries — Part 2: Classification Schemes The revision.
Metadata Models in Survey Computing Some Results of MetaNet – WG 2 METIS 2004, Geneva W. Grossmann University of Vienna.
Tommie Curtis SAIC January 17, 2000 Open Forum on Metadata Registries Santa Fe, NM SDC JE-2023.
Terminology and documentation*  Object of the study of terminology:  analysis and description of the units representing specialized knowledge in specialized.
Tutorial 13 Validating Documents with Schemas
Advanced Technical Writing 2006 Session #4. Today in Class… ► Meet with your editorial team, refine/post deliverables ► Send URL for deliverables to Bill.
Of 33 lecture 1: introduction. of 33 the semantic web vision today’s web (1) web content – for human consumption (no structural information) people search.
Dictionary based interchanges for iSURF -An Interoperability Service Utility for Collaborative Supply Chain Planning across Multiple Domains David Webber.
Web Technologies for Bioinformatics Ken Baclawski.
COMMON COMMUNICATION FORMAT (CCF). Dr.S. Surdarshan Rao Professor Dept. of Library & Information Science Osmania University Hyderbad
The FDES revision process: progress so far, state of the art, the way forward United Nations Statistics Division.
Rendering XML Documents ©NIITeXtensible Markup Language/Lesson 5/Slide 1 of 46 Objectives In this session, you will learn to: * Define rendering * Identify.
Online Information and Education Conference 2004, Bangkok Dr. Britta Woldering, German National Library Metadata development in The European Library.
IT 5433 LM3 Relational Data Model. Learning Objectives: List the 5 properties of relations List the properties of a candidate key, primary key and foreign.
4/13/2015 Most terms were extracted from TermTerm.org, the freely accessible multilingual terminology database containing the terms of terminology and.
Some basic concepts Week 1 Lecture notes INF 384C: Organizing Information Spring 2016 Karen Wickett UT School of Information.
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Wolfram Höpken IFITT RMSIG.
Knowledge Representation Part I Ontology Jan Pettersen Nytun Knowledge Representation Part I, JPN, UiA1.
General Notes on Stylistics
Human Computer Interaction Lecture 21 User Support
Ricardo EIto Brun Strasbourg, 5 Nov 2015
Logical Database Design and the Rational Model
Business System Development
Searching the research literature
UNIFIED MEDICAL LANGUAGE SYSTEMS (UMLS)
The Semantic Web By: Maulik Parikh.
The Object-Oriented Thought Process Chapter 11
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Object Management Group Information Management Metamodel
Software Requirements
Chapter 5 – Requirements Engineering
Databases Chapter 16.
Knowledge Representation Part I Ontology
IB Assessments CRITERION!!!.
ece 627 intelligent web: ontology and beyond
XML QUESTIONS AND ANSWERS
Improving Braille accessibility and personalization on Internet
Web Engineering.
Lecture on Data Modeling and Analysis
Chapter III: Terminology and Arabization: Problems of Multiplicity and Methodology Part 1.
Template library tool and Kestrel training
Networking and Health Information Exchange
Database Vocabulary Terms.
Survey of Knowledge Base Content
Part of the Multilingual Web-LT Program
TERMINOLOGY AND TRANSLATION
Transportation Research Thesaurus:
MIS2502: Data Analytics Relational Data Modeling
Chapter 13 Quality Management
Module P4 Identify Data Products and Views So Their Requirements and Attributes Can Be Controlled Learning Objectives: Understand the value of data. Understand.
Chapter 11 Describing Process Specifications and Structured Decisions
Requirement Engineer Terms and Conditions
Designing a Search Strategy
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Unit 6 - XML Transformations
Presentation transcript:

A Flexible XML-Based Glossary Approach for the Federal Government By Ken Sall for the US Federal XML Community of Practice January 19, 2005

Flexible XML-Based Glossary Approach for the Federal Government Problem Statement After examining standard glossary terminology (ISO 1087 and others), define an XML Schema or DTD that models “all useful” aspects of a term and its definition. Should be applicable to any government agency. Consider flexibility and collaborative development as key design criteria. Many different agencies may use the model and many individuals may author specific term definitions. Create an XSLT stylesheet that knows about the model and displays an XML glossary instance document as HTML in any modern browser. Eventually consider XSL-FO for PDF rendering of the glossary. 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government Design Goals Standards-Based - XML element names are loosely based on an international standard, ISO 1087. Flexible - The Glossary DTD, although initially a strawman to stimulate discussion, is fairly flexible with few required elements, many optional elements, and several repeatable elements. Provides a Framework - Since so few elements are required, terms can be added even before definitions are known. These terms act as placeholders that are fully supported by the DTD and XSLT. (For example, see the stub terms "DTD" and "XSLT" in the example instance.) 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government Design Goals Specialized - Any term may have multiple definitions so that different agencies may use the same term with their own specialized meaning, where necessary. Collaborative - Since an XSLT stylesheet is used to sort the terms alphabetically, many individuals can work on their own glossary fragments (XML instances of the Glossary DTD). At any time, the various contributions can be easily merged without manual editing. Leverages Links - Search links are automatically generated for each term by means of the XSLT, both to help kick-start and to augment the definition. 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government ISO 1087 Terminology (etc.) Key: ISO 1087 Used ISO 1087 & Used Unused Characteristic: Abstraction of a property of an object or of a set of objects. Note - Characteristics are used for describing concepts. [ISO 1087-1:2000, 3.2.4] Concept: A unit of thought constituted through abstraction on the basis of properties common to a set of objects. Note - Concepts are not bound to particular languages. They are, however, influenced by the social or cultural background. (ISO 1087:1990) Unit of knowledge created by a unique combination of characteristics. [ISO 1087-1:2000, 3.2.1] Definition: Statement which describes a concept and permits its differentiation from other concepts within a system of concepts. (ISO 1087:1990) Representation of a concept by a descriptive statement which serves to differentiate it from related concepts. [ISO 1087-1:2000, 3.3.1] 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government ISO 1087 Terminology (etc.) Designation: Representation of a concept by a sign which denotes it. [ISO 1087-1:2000, 3.4.1] Dictionary [see terminology and vocabulary]: Structured collection of lexical units with linguistic information about each of them. (ISO 1087:1990) Key: ISO 1087 Used ISO 1087 & Used Unused 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government ISO 1087 Terminology (etc.) Entry, Headword: The term headword appears in two different meanings. In lexicography, a headword is the word used as the heading in a dictionary entry or encyclopedia. In a descriptive terminology entry where no preference is given to any one term, there is no head term, but if preference is given to a term, head term is sometimes used in analogy to lexicography, as is main entry term. (Wright & Budin, 1997) Key: ISO 1087 Used ISO 1087 & Used Unused 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government ISO 1087 Terminology (etc.) Glossary [see dictionary, terminology, vocabulary]: Alphabetical list of terms or words found in or relating to a specific topic or text. It may or may not include explanations. Note - The distinguishing criterion is that glossaries are considered to reside in backmatter attached to books and other publications rather than being independent works in their own right. Glossaries are sometimes perceived as being less scientific in intent and methodology than terminologies, terminology standards, and even vocabularies, although a certain degree of synonymy exists. (Wright & Budin, 1997) 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government ISO 1087 Terminology (etc.) Nomenclature: System of terms which is elaborated according to pre-established naming rules. (ISO 1087:1990) Object: Anything perceivable or conceivable. Note - Objects may also be material (e.g. an engine, a sheet of paper, a diamond), immaterial (e.g. a conversion ratio, a project plan) or imagined (e.g. a unicorn). [Adapted from ISO 1087-1:2000, 3.1.1] Key: ISO 1087 Used ISO 1087 & Used Unused 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government ISO 1087 Terminology (etc.) Synonym: A word with the same meaning or nearly the same meaning as another word in the same language. (Longman Dictionary of English Language and Culture: Longman Group UK Limited 1992) Note: Terminologists distinguish between real synonyms, i.e. terms which can be substituted with each other whatever the context, and the more common quasi-synonyms, which can differ from one another by context and sometimes by subject field (Sager, 1990) Term: Designation of a defined concept in a special language by a linguistic expression. Note - A term may consist of one or more words or even contain symbols. (ISO 1087:1990) 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government ISO 1087 Terminology (etc.) Terminological Dictionary [see dictionary and vocabulary]: Dictionary containing terminological data from one or more specific subject fields. Note - admitted term: technical dictionary (ISO 1087:1990) Terminological Record: Structured collection of terminological data relevant to one concept. (ISO 1087:1990) Terminological Database: Structured sets of terminological records in an information processing system. (ISO 1087:1990) Key: ISO 1087 Used ISO 1087 & Used Unused 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government ISO 1087 Terminology (etc.) Terminology Work: Any activity concerned with the systematization and representation of concepts or with the presentation of terminologies on the basis of established principles and methods. (ISO 1087:1990) Vocabulary [see terminology, dictionary, glossary]: Terminological dictionary containing the terminology of a specific subject field or of related subject fields and based on terminology work. (ISO 1087:1990) Key: ISO 1087 Used ISO 1087 & Used Unused 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Summary: ISO 1087 Terminology Unused ISO 1087 Terms Characteristic Designation Dictionary Nomenclature Object PreferredTerm – TBD? Terminological Dictionary / technical dictionary Terminological Record Terminological Database Terminological Dictionary Terminology Work Vocabulary ISO 1087 Terms Used: Concept Definition Term Used but not ISO 1087: Glossary Synonym RelatedTerm Additional Terms by Sall (next slide): Name Acronym ExpandedAcronym DefinitionSection Source Usage 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Additional (Non-Standard) Terminology Glossary – change to Dictionary, Vocabulary, Technical Dictionary or Terminology? Name – added only to allow Term to be a container; could change Term to Entry and Name to Term? Acronym – necessary option for technical terms ExpandedAcronym – ditto DefinitionSection - added simply as a repeatable container to encompass all aspects pertaining to a specific definition of a term Source - useful for traceability and credibility Usage – useful to have an optional example sentence for a given definition (use in context) 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

XML Glossary Model Strawman 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government XML Example of One Term <Term id="ontology"> <Name>ontology</Name> <DefinitionSection> <Concept>semantic web</Concept> <Concept>knowledge management</Concept> <Definition>Defines the common words and concepts used to describe and represent an area of knowledge, and so standardizes the meanings. An ontology includes classes in the domains of interest, instances, relationships, properties and their values, functions of and processes involving the objects, and relevant constraints and rules.</Definition> <Source>Daconta, Obrst, Smith</Source> <Usage>An onotology can range from the simple notion of a taxonomy to a thesaurus, to a conceptual model, to a logical theory. [Daconta, Obrst, Smith]</Usage> <Synonym>classification system</Synonym> <RelatedTerm>taxonomy</RelatedTerm> <RelatedTerm>OWL</RelatedTerm> </DefinitionSection> <Concept>philosophy</Concept> <Definition>[sometimes "Ontology"] the metaphysical study of the nature of being and existence</Definition> <Source>WordNet</Source> <Usage>Both the ontology and manner of human existence are of concern to Existentialism.</Usage> <Synonym>metaphysics</Synonym> </Term> 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

XML Ex: Client-Side XSLT (Firefox) 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

XML Ex: Client-Side XSLT (IExplorer) 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

XML Example: XSLT Details CSS Styling DefinitionSection based on Concept Optional and Repeatable Elements New DefinitionSection based on 2nd Concept Auto-generated Search Links 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Collaboration – Merging Instances Since a Glossary consists of one or more Terms, a relatively simple XSLT can be created to merge the Term elements for two or more XML instances. This means different authors (from the same or different agencies) can work independently. Issue: What if same Term is defined by different authors? Automatically add each definition, even though they may overlap/conflict, or manually edit collisions (could generate a conflict message)? Issue: Should agency name be a Source or another element (e.g., AgencySource)? Advantage is that custom XSLT could extract or render terms on per agency basis, if desired. Should there be an optional, repeatable SourceLink element for a URL? 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Alternative: GlossXML 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Alternative: XML Acronym Desmystifier 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government

Flexible XML-Based Glossary Approach for the Federal Government Next Steps Determine interested agencies. Establish funding. Resolve terminology issues for the Glossary model. Consider merge or replacement by GlossXML and/or XML Acronym Demystifier. Need to finalize DTD or XML Schema before agencies start authoring. Revise initial XSLT to match final Glossary model. Determine repository and submission mechanisms. Could be a good use for CORE.gov? Coordinate with Plans for Derived XML Registry Prototype? Write additional XSLT stylesheets for merging and pulling agency-specific terms, etc. Develop XSL-FO stylesheets for PDF rendering of Glossary. 1/19/2005 Flexible XML-Based Glossary Approach for the Federal Government