DOCSLIB.ORG

CS490W XML Data and Retrieval XML and Retrieval

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
CS490W XML Data and Retrieval XML and Retrieval CS490W XML data and Retrieval Luo Si Department of Computer Science Purdue University XML and Retrieval: Outline Outline: z Semi-Structure Data ¾ XML, Examples, Application z XML Search ¾ XQuery ¾ XIRQL z Text-Based XML Retrieval ¾ Vector-space model ¾ INEX Semi-Structured Data XML has been used as the standard representation of Semi- Structured Data z eXtensible Markup Language is a W3C-recommended general-purpose markup language that supports a wide variety of applications. z A framework for defining markup languages z Open vocabulary for tags z Each set of XML corresponds to different applications z facilitate the sharing of data across different information systems, particularly systems connected via the Internet z Examples: RSS, XHTML, MathML Semi-Structured Data Structure of XML z XML data is organized by documents like unstructured data z There are structures (nodes/tags) within the documents z Each XML document is an ordered, labeled tree z Element Nodes are labeled with ¾ Node name (e.g., chapter) ¾ Node attributes and the values (e.g., size=1000; time=01/01/2007) ¾ May have child nodes or data z Data exist (e.g., text strings) within leaf nodes XML Example <book id=“ML_Tom”> <title>Machine Learning</title> <author> <firstname>Tom</firstname> <surname>Mitchell</surname> </author> ... <p>Machine Learning Applications...</p> ... </book> Elements, Attributes/Values, Data(Text String) XML Example <book id=“ML_Tom”> <title>Machine Learning</title> <author> <firstname>Tom</firstname> <surname>Michael</surname> </author> book ... <p>Machine Learning Applications...</p> title ... </book> author firstname surname Elements, Attributes/Values, Data(Text String) chapter chapter title para para para Elements z Elements are defined by markup tags z Elements: <TagName attr_a=“value”…>text</TagName> z ID of the element is TagName z Attribute: attr_a; Values=“value” z Data/text: “text” z End tag </TagName> XML, HTML, SGML 1986: SGML ISO 8879-1986 Nov 1995: HTML 2.0 Nov 1996: Simplified and stripped down SGML draft (dubbed XML) Jan 1997: HTML 3.2 Aug 1997: XML working draft Dec 1997: XML 1.0 proposed recommendation Jan 1998: XML Feb 1999: XHTML XML and HTML z Both of them are derivations of SGML z HTML is a markup language mainly for display in browsers z XML is a framework for markup languages z HTML defines display z XML defines the data structure, the display factor is separated from the content z HTML can be formalized as XML (XHTML) Why XML? z Unlike relational database, XML data does not require relational schemata, etc., because the data itself contains this information. z Unlike widely used Web format, HTML, which only ensures the correct presentation of the formatted data, XML also guarantees total usability of data. XML Applications z CML – chemical markup language: z WML – wireless markup language z ThML – theological markup language XML Applications z CML – chemical markup language: CML (Chemical Markup Language) is a new approach to managing molecular information using tools such as XML and Java. It was the first domain specific implementation based strictly on XML, <molecule convention="MDLMol" id="baclofen" title="BACLOFEN"> XML Applications z WML – wireless markup language Wireless Markup Language, is a content format for devices that implement the Wireless Application Protocol (WAP) specification, such as mobile phones. <?xml version="1.0"?> <!DOCTYPE wml PUBLIC "-//PHONE.COM//DTD WML 1.1//EN" "http://www.phone.com/dtd/wml11.dtd" > <wml> <card id="main" title="First Card"> <p mode="wrap">This is a sample WML page.</p> </card> </wml> XML Applications z ThML – theological markup language <ThML> <ThML.body> – <div1> <div2 title="Genesis" id="Gen"> – <div3 title="Chapter 1"> •<p> • <scripture/> • In the beginning God created the heaven and the earth. • <scripture/> • And the earth was without form, and void; and darkness was upon the face of the deep. And the Spirit of God moved upon the face of the waters. •</p> – </div3> </div2> – </div1> </ThML.body> </ThML> XML Files z Schema/DTD: syntax definition of XML Language; Document Type Definition (DTD file) XML provides an application independent way of sharing data. With a DTD, independent groups of people can agree to use a common DTD for interchanging data. However, this is often NOT the case <?xml version="1.0"?> <!DOCTYPE note [ <!ELEMENT note (to,from,heading,body)> <!ELEMENT to (#PCDATA)> DTD Example <!ELEMENT from (#PCDATA)> <!ELEMENT heading (#PCDATA)> <!ELEMENT body (#PCDATA)> ]> XML Files z <?xml version="1.0"?> <!DOCTYPE note [ <!ELEMENT note (to,from,heading,body)> <!ELEMENT to (#PCDATA)> DTD Example <!ELEMENT from (#PCDATA)> <!ELEMENT heading (#PCDATA)> <!ELEMENT body (#PCDATA)> ]> <note> <to>Tove</to> XML Document <from>Jani</from> <heading>Reminder</heading> <body>Don't forget me this weekend!</body> </note> XML Files z XML Schema: Recommended by the W3C as the successor of DTDs, more informally referred to by the initialism for XML Schema instances, XSD (XML Schema Definition). XSDs are far more powerful than DTDs in describing XML languages. <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="country" type="Country"/> <xs:complexType name="Country"> <xs:sequence> <xs:element name="name" type="xs:string"/> <xs:element name="population" type="xs:decimal"/> </xs:sequence> </xs:complexType> </xs:schema> XML Search z Most XML Search protocols use a database-based approach ¾ Non-text data match ¾ Exact keyword (text) match ¾ Evaluate XML path expression ¾ No concept of relevant XML Search z Traditional XML Search from Database-based approach ¾ XQuery ¾ Search multiple types of data: value-based (e.g., price of a book); ids (ISBN of book); keyword match (text) z XML text search from information retrieval approach ¾ XIRQL ¾ Vector-space based ¾ Search text data: estimate relevance of xml elements with respect of query ¾ Query may contain path expressions XML Search z XQuery ¾ SQL for XML ¾ Used for text-rich documents; data-oriented documents (non-text); mixed documents ¾ Consider: path expression (XPath); XML Schema datatypes ¾ It is still a working draft; details are being improved XML Search z XQuery considers some principal forms ¾ Path expression ¾ Conditional expressions ¾ Datatype expressions ¾ List expression ¾ etc z Programming Language: Flowers (FLWOR) expression z Principle forms can be evaluated with respect to context Principal Forms z Path Query /book//title contains “Information Retrieval” title of the book contains keywords “Information Retrieval” z Conditional expressions $h/title, IF $h/@type = "Journal" THEN …. if the type of an article is journal Flowers (FLWR) z Programming Language: Flowers (FLWR) expression The programming language XQuery defines FLWOR or FLWR (often pronounced as 'flower') as expression that supports iteration and binding of variables to intermediate results. ¾ For and let create a sequence of tuples ¾ where filters the tuples on a boolean expression ¾ order by sorts the tuples, using any comparable data ¾ return gets evaluated once for every tuple Flowers (FLWR) for $d in document("depts.xml")//deptno let $e := document("emps.xml")//employee[deptno = $d] where count($e) >= 10 order by avg($e/salary) descending return <big-dept> { $d, <headcount>{count($e)}</headcount>, <avgsal>{avg($e/salary)}</avgsal> } </big-dept> XML Search z XQuery considers some principal forms and combine them with Flowers (FLWR) It is quite similar to SQL for relational database z However, it does not have the concept of relevance, which is important for both text data (text-based information retrieval) and non-text data (fuzzy search). Find a book about information retrieval Find a book which is about $30. XML IR Challenges 1: Term Statistics z There are multiple types of elements: books/titles/abstracts; how to construct the corpus-statistics (idf) for different elements? z How do we handle the term frequency information? Example: /book//title “information retrieval” do we consider the book abstract? Hierarchical smoothing XML IR Challenges 2: Schemas z Ideal Case ¾ There is a universal schema ¾ User can associate data type with the universal schema without ambiguity ¾ Too ideal to be true… z Real Word ¾ There are many schemas; different spellings; different concepts; different granularities; (e.g., “auth” & “authors”; “abstract” & “description”; “abstract” & “keywords”) XML IR Challenges 3: User interface z How to guide user to find relevant elements ¾ Granularity control: Book->Abstract->Full Text z What type of querying language ¾ Natural language query (IR approach): most usable ¾ With structure information: more powerful but less usable z How to do query expansion ¾ How to automatically add structure information e.g., find a book written by J. K. Rowling, -> find a book written by /../author (J. K. Rowling,) open research problem XIRQL Prof. Norbert Furth University of Dortmund: Open source XML search engine XIRQL: a query language for information retrieval in XML documents ¾ Structured Document Retrieval Principle ¾ Users may not know the schema Allow users to search even if they do not know the schema of the data Units z Only atomic units can be returned traditional IR treats documents as atomic units; XML treat tree-like view of documents. z XIRQL only indexes and returns atom-units ¾ Atom-units can be leaf nodes that contain text information ¾ Atom-units can be other internal nodes ¾ Atom-units can be defined in DTD ¾ TF-IDF values are calculated based-on atom-units XIRQL Atom-Units Structured Document Retrieval
Load more

Recommended publications
  • Designing Universal Chemical Markup (UCM) Through the Reusable Methodology Based on Analyzing Existing Related Formats
    Designing Universal Chemical Markup (UCM) through the reusable methodology based on analyzing existing related formats Background: In order to design concepts for a new general-purpose chemical format we analyzed the strengths and weaknesses of current formats for common chemical data. While the new format is discussed more in the next article, here we describe our software s t tools and two stage analysis procedure that supplied the necessary information for the n i r development. The chemical formats analyzed in both stages were: CDX, CDXML, CML, P CTfile and XDfile. In addition the following formats were included in the first stage only: e r P CIF, InChI, NCBI ASN.1, NCBI XML, PDB, PDBx/mmCIF, PDBML, SMILES, SLN and Mol2. Results: A two stage analysis process devised for both XML (Extensible Markup Language) and non-XML formats enabled us to verify if and how potential advantages of XML are utilized in the widely used general-purpose chemical formats. In the first stage we accumulated information about analyzed formats and selected the formats with the most general-purpose chemical functionality for the second stage. During the second stage our set of software quality requirements was used to assess the benefits and issues of selected formats. Additionally, the detailed analysis of XML formats structure in the second stage helped us to identify concepts in those formats. Using these concepts we came up with the concise structure for a new chemical format, which is designed to provide precise built-in validation capabilities and aims to avoid the potential issues of analyzed formats.
    [Show full text]
  • Linking Nwchem and Avogadro with the Syntax and Semantics of Chemical Markup Language Wibe a De Jong1*†, Andrew M Walker2† and Marcus D Hanwell3†
    de Jong et al. Journal of Cheminformatics 2013, 5:25 http://www.jcheminf.com/content/5/1/25 RESEARCH ARTICLE Open Access From data to analysis: linking NWChem and Avogadro with the syntax and semantics of Chemical Markup Language Wibe A de Jong1*†, Andrew M Walker2† and Marcus D Hanwell3† Abstract Background: Multidisciplinary integrated research requires the ability to couple the diverse sets of data obtained from a range of complex experiments and computer simulations. Integrating data requires semantically rich information. In this paper an end-to-end use of semantically rich data in computational chemistry is demonstrated utilizing the Chemical Markup Language (CML) framework. Semantically rich data is generated by the NWChem computational chemistry software with the FoX library and utilized by the Avogadro molecular editor for analysis and visualization. Results: The NWChem computational chemistry software has been modified and coupled to the FoX library to write CML compliant XML data files. The FoX library was expanded to represent the lexical input files and molecular orbitals used by the computational chemistry software. Draft dictionary entries and a format for molecular orbitals within CML CompChem were developed. The Avogadro application was extended to read in CML data, and display molecular geometry and electronic structure in the GUI allowing for an end-to-end solution where Avogadro can create input structures, generate input files, NWChem can run the calculation and Avogadro can then read in and analyse the CML output produced. The developments outlined in this paper will be made available in future releases of NWChem, FoX, and Avogadro. Conclusions: The production of CML compliant XML files for computational chemistry software such as NWChem can be accomplished relatively easily using the FoX library.
    [Show full text]
  • XML for Java Developers G22.3033-002 Course Roadmap
    XML for Java Developers G22.3033-002 Session 1 - Main Theme Markup Language Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Course Roadmap Consider the Spectrum of Applications Architectures Distributed vs. Decentralized Apps + Thick vs. Thin Clients J2EE for eCommerce vs. J2EE/Web Services, JXTA, etc. Learn Specific XML/Java “Patterns” Used for Data/Content Presentation, Data Exchange, and Application Configuration Cover XML/Java Technologies According to their Use in the Various Phases of the Application Development Lifecycle (i.e., Discovery, Design, Development, Deployment, Administration) e.g., Modeling, Configuration Management, Processing, Rendering, Querying, Secure Messaging, etc. Develop XML Applications as Assemblies of Reusable XML- Based Services (Applications of XML + Java Applications) 2 1 Agenda XML Generics Course Logistics, Structure and Objectives History of Meta-Markup Languages XML Applications: Markup Languages XML Information Modeling Applications XML-Based Architectures XML and Java XML Development Tools Summary Class Project Readings Assignment #1a 3 Part I Introduction 4 2 XML Generics XML means eXtensible Markup Language XML expresses the structure of information (i.e., document content) separately from its presentation XSL style sheets are used to convert documents to a presentation format that can be processed by a target presentation device (e.g., HTML in the case of legacy browsers) Need a
    [Show full text]
  • Matml: XML for Information Exchange with Materials Property Data
    MatML: XML for Information Exchange with Materials Property Data Aparna S. Varde1,2 Edwin F. Begley Sally Fahrenholz-Mann 1. Department of Computer Science Computer Integrated Building Electronic Publishing and Content 2. Materials Science Program Processes Group Management Worcester Polytechnic Institute (WPI) National Institute of Standards and ASM International Worcester, MA, USA Technology (NIST) Materials Park, OH, USA [email protected] Gaithersburg, MD, USA sally.fahrenholz- [email protected] [email protected] ABSTRACT 1. INTRODUCTION This paper describes the development and use of MatML, the XML, the eXtensible Markup Language is today a widely Materials Markup Language. MatML is an emerging XML accepted standard for storage and exchange of information. It standard intended primarily for the exchange of materials serves a twofold purpose of providing a data model for storing property information. It provides a medium of communication for information and a medium of communication for exchanging users in materials science and related fields such as manufacturing information over the worldwide web [29]. and aerospace. It sets the stage for the development of semantic Domain-specific markup languages are often defined within the web standards to enhance knowledge discovery in materials context of XML to serve as the means for storing and exchanging science and related areas. MatML has been used in applications information in the respective domains. Some examples of such such as the development of materials digital libraries and analysis markup languages include [14, 9]: of contaminant emissions data. Data mining applications of MatML include statistical process control and failure analysis. • AniML: Analytical Information Markup Language Challenges in promoting MatML involve satisfying a broad range • ChemML: Chemical Markup Language of constituencies in the international engineering and materials science community and also adhering to other related standards in • femML: Finite Element Modeling Markup Language web data exchange.
    [Show full text]
  • The Semantics of Chemical Markup Language (CML
    Murray-Rust et al. Journal of Cheminformatics 2011, 3:43 http://www.jcheminf.com/content/3/1/43 RESEARCH ARTICLE Open Access The semantics of Chemical Markup Language (CML): dictionaries and conventions Peter Murray-Rust1*, Joe A Townsend1, Sam E Adams1, Weerapong Phadungsukanan2 and Jens Thomas3 Abstract The semantic architecture of CML consists of conventions, dictionaries and units. The conventions conform to a top-level specification and each convention can constrain compliant documents through machine-processing (validation). Dictionaries conform to a dictionary specification which also imposes machine validation on the dictionaries. Each dictionary can also be used to validate data in a CML document, and provide human-readable descriptions. An additional set of conventions and dictionaries are used to support scientific units. All conventions, dictionaries and dictionary elements are identifiable and addressable through unique URIs. Introduction semantics through dictionaries. These have ranged from From an early stage, Chemical Markup Language (CML) a formally controlled ontology (ChemAxiom [2]) which was designed so that it could accommodate an indefi- is consistent with OWL2.0 [3] and the biosciences’ nitely large amount of chemical and related concepts. Open Biological and Biomedical Ontologies (OBO)[4] This objective has been achieved by developing a dic- framework, to uncontrolled folksonomy-like tagging. tionary mechanism where many of the semantics are Although we have implemented ChemAxiom and it is added not through hard-coded elements and attributes part of the bioscientists’ description of chemistry, we but by linking to semantic dictionaries. CML has a regard it as too challenging for the current practice of number of objects and object containers which are chemistry and unnecessary for its communication.
    [Show full text]
  • Archive and Compressed [Edit]
    Archive and compressed [edit] Main article: List of archive formats • .?Q? – files compressed by the SQ program • 7z – 7-Zip compressed file • AAC – Advanced Audio Coding • ace – ACE compressed file • ALZ – ALZip compressed file • APK – Applications installable on Android • AT3 – Sony's UMD Data compression • .bke – BackupEarth.com Data compression • ARC • ARJ – ARJ compressed file • BA – Scifer Archive (.ba), Scifer External Archive Type • big – Special file compression format used by Electronic Arts for compressing the data for many of EA's games • BIK (.bik) – Bink Video file. A video compression system developed by RAD Game Tools • BKF (.bkf) – Microsoft backup created by NTBACKUP.EXE • bzip2 – (.bz2) • bld - Skyscraper Simulator Building • c4 – JEDMICS image files, a DOD system • cab – Microsoft Cabinet • cals – JEDMICS image files, a DOD system • cpt/sea – Compact Pro (Macintosh) • DAA – Closed-format, Windows-only compressed disk image • deb – Debian Linux install package • DMG – an Apple compressed/encrypted format • DDZ – a file which can only be used by the "daydreamer engine" created by "fever-dreamer", a program similar to RAGS, it's mainly used to make somewhat short games. • DPE – Package of AVE documents made with Aquafadas digital publishing tools. • EEA – An encrypted CAB, ostensibly for protecting email attachments • .egg – Alzip Egg Edition compressed file • EGT (.egt) – EGT Universal Document also used to create compressed cabinet files replaces .ecab • ECAB (.ECAB, .ezip) – EGT Compressed Folder used in advanced systems to compress entire system folders, replaced by EGT Universal Document • ESS (.ess) – EGT SmartSense File, detects files compressed using the EGT compression system. • GHO (.gho, .ghs) – Norton Ghost • gzip (.gz) – Compressed file • IPG (.ipg) – Format in which Apple Inc.
    [Show full text]
  • Understanding
    Implementing UBL Mark Crawford UBL Vice Chair XML 2003 9 December 2003 Why Are We Talking About UBL • UBL fulfils the promise of XML for business by defining a standard cross-industry vocabulary • UBL is the ebXML missing link • UBL plus ebXML enables the next generation of eBusiness exchanges – Cheaper, easier, Internet-ready – Extends benefits of EDI to small businesses – Fits existing legal and trade concepts – Allows re-use of data • UBL can provide the XML payload for a wide variety of other web-based business frameworks Overview 1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability 4 Making UBL Happen 5 UBL Phase 2 6 Summary The promise of XML for e-business • Plug ‘n’ play electronic commerce – Spontaneous trade – No custom programming • Ubiquity on the Internet – Dirt-cheap tools – Complete platform independence – Enable true global market availability • Enable universal interoperability – Abandon existing EDI systems – Handle both "publication" document types and "transactional" documents Goals for Successful eBusiness Services • Web-enable existing fax- and paper-based business practices • Allow businesses to upgrade at their own pace • Preserve the existing investment in electronic business exchanges • Integrate small and medium-size businesses into existing electronic data exchange-based supply chains The standardization of XML business documents is the easiest way to accomplish
    [Show full text]
  • An XML Format for Proteomics Database to Accelerate Collaboration Among Researchers
    AO HUPO workshop in Tsukuba (Dec. 19, 2002) An XML Format For Proteomics Database to Accelerate Collaboration Among Researchers HUP-ML: Human Proteome Markup Language K. Kamijo, H. Mizuguchi, A. Kenmochi, M. Sato, Y. Takaki and A. Tsugita Proteomics Res. Center, NEC Corp. 1 Overview (HUP-ML) z Introduction z XML features z XMLs in life science z HUP-ML concept z Example of HUP-ML z Details of HUP-ML z Demonstration of “HUP-ML Editor” 2 Introduction z Download entries from public DBs as a flat-file z easy for a person to read z different formats for every DB z sometimes needs special access methods and special applications for each format z Needs machine-readable formats for software tools z To boost studies by exchanging data among researchers Activates standardization 3 XML format z XML (eXtensible Markup Language) W3C: World Wide Web Consortium (inception in 1996) Attribute Key Value Example Element Start Tag <tag_element_source attribute_growth=“8 weeks”> rice leaf </tag_element_source> End Tag z Highly readable for machine and person z Can represent information hierarchy and relationships z Details can be added right away z Convenient for exchanging data z Easy to translate to other formats 4 z Logical-check by a Document Type Definition (DTD) Overview (HUP-ML) z Introduction z XML features z XMLs in life science z HUP-ML concept z Example of HUP-ML z Details of HUP-ML z Demonstration of “HUP-ML Editor” 5 XML features z Exchangeable z Inter-operability: z OS (Operating System): Windows, Linux, etc. z Software Development Languages
    [Show full text]
  • For Computational Chemistry : Compchem
    The Semantics of Chemical Markup Language (CML) for Computational Chemistry : CompChem Preprint Cambridge Centre for Computational Chemical Engineering ISSN 1473 { 4273 The Semantics of Chemical Markup Language (CML) for Computational Chemistry : CompChem Weerapong Phadungsukanan 1, Markus Kraft 1, Joe Townsend 2, Peter Murray-Rust 2 released: May 22, 2012 1 Department of Chemical Engineering and 2 Department of Chemistry Biotechnology University of Cambridge University of Cambridge Lensfield Road New Museums Site Cambridge, CB2 1EW Pembroke Street UK Cambridge, CB2 3RA UK E-mail: [email protected] Preprint No. 117 Keywords: CML, CompChem, RDF, computational chemistry, thermochemistry, control vocab- ulary, rule-based validation Edited by Computational Modelling Group Department of Chemical Engineering and Biotechnology University of Cambridge New Museums Site Pembroke Street Cambridge CB2 3RA CoMo United Kingdom GROUP Fax: + 44 (0)1223 334796 E-Mail: [email protected] World Wide Web: http://como.cheng.cam.ac.uk/ Abstract This paper introduces a subdomain chemistry format for storing computa- tional chemistry data called CompChem. It has been developed based on the design, concepts and methodologies of Chemical Markup Language (CML) by adding computational chemistry semantics on top of the CML Schema. The format allows a wide range of ab initio quantum chemistry calculations of individual molecules to be stored. These calculations include, for exam- ple, single point energy calculation, molecular geometry optimization, and vibrational frequency analysis. The paper also describes the supporting in- frastructure, such as processing software, dictionaries, validation tools and database repositories. In addition, some of the challenges and difficulties in developing common computational chemistry dictionaries are discussed.
    [Show full text]
  • Chemical Markup, XML, and the Worldwide Web. 1. Basic Principles
    Chemical Markup, XML, and the Worldwide Web. 1. Basic Principles Peter Murray-Rust*,† and Henry S. Rzepa‡ Virtual School of Molecular Sciences, School of Pharmaceutical Sciences, University of Nottingham, U.K., and Department of Chemistry, Imperial College of Science, Technology and Medicine, London SW72AY, U.K. Received May 26, 1999 Chemical markup language (CML) is an application of XML, the extensible markup language, developed for containing chemical information components within documents. Its design supports interoperability with the XML family of tools and protocols. It provides a base functionality for atomic, molecular, and crystallographic information and allows extensibility for other chemical applications. Legacy files can be imported into CML without information loss and can carry any desired chemical ontology. Some applications of CML (Markush structures, chemical searching) will be discussed in later articles. An XML document type declaration (DTD) for CML is included as a Chart. INTRODUCTION TO XML TERMINOLOGY AND (9) Name spaces can be nested and the youngest ancestor SYNOPSIS OF TERMS with a name space declaration determines the current scope Prior to introducing XML (extensible markup language) (10) A DTD may, but need not, be provided for a and CML (chemical markup language),1 we feel it important document instance. If it is, a validating parser can check to define some key XML terminology (Table 1).2 We assume whether the document is valid (i.e. it conforms). the reader is familiar with the basis of HTML (hypertext A number of related applications are under active develop- 2 markup language) and its application in chemistry.3 XML ment, all expressed in XML itself.
    [Show full text]
  • Three SGML Metadata Formats: TEI, EAD, and CIMI
    Three SGML metadata formats: TEI, EAD, and CIMI A Study for BIBLINK Work Package 1.1 December 1996 Lou Burnard and Richard Light BIBLINK study of SGML metadata formats Page 1 Prefatory Note BIBLINK Work Package 1 (Study of Metadata) is intended to identify, describe, and compare current approaches to the encoding of metadata, with a view to making recommendations. Amongst the many different approaches currently in use, those based on the Standard Generalized Markup Lamguage (SGML: ISO 8879) appear to offer the widest range of features and the broadest potential for cross-sector applicability. This additional detailed study on three SGML-based formats was therefore commissioned to supplement the survey reported on in Work Package 1. This report consists of a brief overview of each of the three schemes studied, some general discussion of the technical aspects of using SGML in a production environment, and a detailed feature by feature comparison of the three schemes with respect to a number of key attributes identified by the Biblink project. A bibliography with pointers to further reading on each of the three schemes is also provided. Richard Light was responsible for the original draft of the report, and for the information on CIMI and EAD. Lou Burnard was responsible for final editing of the report and for the information on TEI and SGML. Thanks are due to John Perkins, Daniel Pitti, and Rachel Heery for helpful suggestions during the preparation of the report. 1 Introduction 2 2 Overview of the schemes studied 2 2.1 The Text Encoding
    [Show full text]
  • Markup Languages—How to Structure Chemistry-Related Documents by Peter Murray-Rust and Henry S
    Markup Languages—How to Structure Chemistry-Related Documents by Peter Murray-Rust and Henry S. Rzepa G Creation of an infrastructure for underpinning the Although the use of markup languages in publishing emerging areas of e-business goes back to the 1960s when IBM introduced GML (Generalized Markup Language), which subsequently The extension to chemistry included, therefore, the evolved into the standard SGML, most authors are creation of a new generation of ontologically rich, pri- nowadays more familiar with the more recent imple- mary publication and a clear division of the respective mentation, referred to as HTML (HyperText Markup roles of humans and software agents (robots). Thus, Language). The rapid rise in the use of HTML in con- humans should be able to: junction with the growth of the World Wide Web was in G Publish all their data automatically large measure due to its ease of use for achieving pre- G Eliminate errorsfrom publications sentational and visual effect. However, its limitations as a mechanism for expressing precisely defined data and G Use the published literature as a database meanings were not always adequately recognized. G Understandinformation from other domains These limitations meant that in areas such as molecular sciences where precise meanings are essential, a variety Robots should be able to: of often proprietary solutions continued to be used to G Analyze publications (on whatever scale) define and manipulate molecular “data” and informa- G Create secondary publications tion. The publishing processes were seen as quite sepa- rate and the process of translating data, information, and G Purchase chemicals knowledge into a published entity remained an activity G Synthesize chemicals from literature requiring much human perception.
    [Show full text]