A Framework for Processing and Presenting Parallel Text Corpora

Total Page:16

File Type:pdf, Size:1020Kb

A Framework for Processing and Presenting Parallel Text Corpora A framework for processing and presenting parallel text corpora Dissertation der Fakultat¨ fur¨ Informations- und Kognitionswissenschaften der Eberhard-Karls-Universitat¨ Tubingen¨ zur Erlangung des Grades eines Doktors der Naturwissenschaften (Dr. rer. nat.) vorgelegt von Dipl.-Inform. Volker Simonis aus Mediasch T ¨ubingen 2004 Tag der m ¨undlichenQualifikation: 21. Juli 2004 Dekan: Prof. Dr. Ulrich Guntzer¨ 1. Berichterstatter: Prof. Dr. Rudiger¨ Loos 2. Berichterstatter: Prof. Dr. Wolfram Luther (Univ. Duisburg-Essen) Meinen Eltern Abstract This thesis describes an extensible framework for the processing and pre- sentation of multi-modal, parallel text corpora. It can be used to load digital documents in many formats like for example pure text, XML or bit-mapped graphics, to structure these documents with a uniform markup and link them together. The structuring or tagging can be done with respect to formal, lingui- stic, semantic, historical and many other aspects. Different, parallel taggings are possible for a document and the documents marked up this way can be linked together with respect to any of these structures. Depending on the nature of the tagging and the scope of the linking, they can be performed automatically, semi-automatically or manually. As a foundation of this work, XTE, a simple but powerful XML standoff annotation scheme has been developed and realized as a DTD and as an XML Schema. XTE is especially well suited for the encoding of multiple, overlapping hierarchies in multi-modal documents and for the cross linking of the elements of these encodings across several documents. Together with XTE, elaborate editor and browser applications have been de- veloped which allow the comfortable creation and presentation of XTE encoded documents. These applications have been realized as a configurable and exten- sible framework that makes it easy for others to extend, customize and adopt the system for their special needs. The combination of a classical textual synop- sis with the supplementary options of dictionaries, encyclopedias, multi-media extensions and powerful tools opens a wide area of applicability for the system ranging from text analysis and language learning to the creation of critical edi- tions and electronic publishing. As a side effect of the main topic, different tools for program and software documentation have been developed and a new and innovative, multilingual user interface has been created. The documentation tools have been used to do- cument the components of the framework while the new user interface has been built into the created applications. Zusammenfassung Diese Arbeit stellt ein erweiterbares System fur¨ die Bearbeitung und Prasen-¨ tation von multi-modalen, parallelen Textkorpora vor. Es kann dazu verwendet werden um digitale Dokumente in vielerlei Formaten wie zum Beispiel einfa- che Textdateien, XML-Dateien oder Graphiken zu bearbeiten wobei bearbeiten in diesem Zusammenhang vor allem strukturieren und verlinken bedeutet. Die- se Strukturierung nach einem neu entwickelten Kodierungschema kann zum Beispiel auf formalen, linguistischen, semantischen, historischen oder auch vie- len anderen Gesichtspunkten beruhen. Die Dokumente konnen¨ gleichzeitig mit beliebig vielen parallelen und sich moglicherweise¨ auch uberlappenden¨ Struk- turen versehen werden und bezuglich¨ jeder dieser Strukturen auch miteinander verknupft¨ werden. Die unterschiedlichen Strukturen konnen¨ je nach Art ent- weder automatisch oder halbautomatisch erzeugt werden oder sie konnen¨ vom Benutzer manuell spezifiziert werden. Als Grundlage des vorgestellten Systems dient XTE, ein einfaches aber zu- gleich machtiges,¨ externe Kodierungsschema das sowohl als eine XML DTD als auch als ein XML Schema verwirklicht wurde. XTE ist besonders zum Kodie- ren von vielen, sich gegenseitig uberlappenden¨ Hierarchien in multi-modalen Dokumenten und zum Verknupfen¨ dieser Strukturen uber¨ mehrere Dokumente hinweg, geeignet. Zusammen mit XTE wurden zwei ausgereifte Anwendungen zum Betrach- ten und Bearbeiten von XTE-kodierten Dokumenten sowie zum komfortablen Arbeiten mit den so erstellten Ergebnisdokumenten geschaffen. Diese Anwen- dungen wurden als anpassbares und erweiterbares System konzipiert, das mog-¨ lichst einfach fur¨ andere Einsatzgebiete und an neue Benutzerwunsche¨ ange- passt werden konnen¨ soll. Die Kombination einer klassischen Synopse zusam- men mit den vorhandenen Erweiterungsmoglichkeiten¨ mittels Worterb¨ uchern,¨ Lexika und Multi-Media Elementen die das System bietet, machen es zu einem Werkzeug das auf vielen Gebieten, angefangen von der Text-Analyse und dem Sprachenlernen uber¨ die Erstellung textkritischer Editionen bis hin zum elektro- nischen Publizieren, einsetzbar ist. Neben diesem System sind als weitere Ergebnisse dieser Arbeit verschiedene Werkzeuge fur¨ die Softwaredokumentation entstanden und zur Dokumentation des Systems eingesetzt worden. Weiterhin wurde eine neuartige, mehrsprachi- ge, graphische Benutzeroberflache¨ entwickelt, die unter anderem in dem hier beschriebenen System eingesetz wurde. Contents 1 Introduction 1 1.1 Text encoding ................................... 1 1.1.1 History of text encoding ......................... 2 1.1.2 Electronic character encodings .................... 4 1.2 Text markup .................................... 5 1.2.1 Text processing .............................. 5 1.2.2 General Markup Languages ...................... 6 1.2.3 Specialized Markup Languages for Text ............... 8 1.3 Scope and contribution ............................. 9 1.4 Structure of this work ............................... 10 2 A new markup scheme for text 11 2.1 A short introduction to XML ........................... 11 2.1.1 XML namespaces ............................ 13 2.1.2 XML schema languages ......................... 14 2.1.3 XPath, XPointer and XLink ........................ 15 2.1.4 XSL - The Extensible Stylesheet Language .............. 17 2.1.5 The future of XML ............................. 17 2.2 The problem of overlapping hierarchies ................... 17 2.3 Workarounds for the problem of overlapping hierarchies ......... 18 2.3.1 The SGML CONCUR feature ......................... 18 2.3.2 Milestone elements ............................ 19 2.3.3 Fragmentation .............................. 20 2.3.4 Virtual joins ................................. 20 2.3.5 Multiple encodings ............................ 21 2.3.6 Bottom up virtual hierarchies ...................... 21 2.3.7 Just in time trees ............................. 21 2.3.8 Standoff markup ............................. 21 2.4 XTE - A new standoff markup scheme ..................... 22 2.4.1 The XTE DTD ................................ 23 2.4.2 XTE - Expressed as an XML Schema .................. 30 2.4.3 Using the XTE DTD together with the XTE XML Schema ....... 38 2.4.4 Encoding facsimile texts with XTE ................... 41 3 The software architecture of LanguageExplorer and LanguageAnalyzer 43 3.1 The Java programming language ....................... 43 3.1.1 The Java APIs ............................... 44 3.2 The LanguageExplorer text classes ...................... 49 3.2.1 The document class ........................... 50 3.2.2 The editor kit ................................ 52 Dissertation der Fak. f. Informations- u. Kognitionswissenschaften, Univ. Tubingen¨ - 2004 ii CONTENTS 3.2.3 The view classes ............................. 54 3.3 The LanguageExplorer file formats ....................... 55 3.3.1 The LanguageExplorer book format .................. 55 3.3.2 Encryption of LanguageExplorer books ............... 57 3.3.3 LanguageExplorer configuration files ................. 58 3.4 The design of LanguageAnalyzer ....................... 59 3.5 The design of LanguageExplorer ........................ 60 3.6 The plugin concept ............................... 62 3.6.1 Handling new XTE elements ...................... 62 3.6.2 Support for new media types ...................... 63 3.6.3 Adding new tools ............................. 63 4 Implementation techniques and libraries 65 4.1 Program documentation with ProgDOC .................... 65 4.1.1 Introduction ................................ 66 4.1.2 Some words on Literate Programming ................ 66 4.1.3 Software documentation in the age of IDEs ............. 70 4.1.4 Software documentation and XML .................. 71 4.1.5 Overview of the ProgDOC system ................... 72 4.1.6 The \sourceinput command ...................... 75 4.1.7 Using ProgDOC in two-column mode ................. 77 4.1.8 Using the alternative highlighter pdlsthighlight ........... 77 4.1.9 The \sourcebegin and \sourceend commands ............ 78 4.1.10 The \sourceinputbase command .................... 79 4.1.11 The source file format .......................... 79 4.1.12 LATEX customization of ProgDOC ..................... 81 4.1.13 An example Makefile .......................... 83 4.2 Program documentation with XDoc ..................... 85 4.2.1 Introduction ................................ 85 4.2.2 The new XDoc approach ........................ 85 4.2.3 A prototype implementation ...................... 88 4.2.4 Conclusion ................................. 94 4.3 A Locale-Sensitive User Interface ....................... 97 4.3.1 Introduction ................................ 97 4.3.2 The Java Swing architecture ...................... 98 4.3.3 The solution - idea and implementation ............... 99 4.3.4 Conclusion ................................. 107 4.4 Scrolling on demand ..............................
Recommended publications
  • Recommended Formats Statement 2019-2020
    Library of Congress Recommended Formats Statement 2019-2020 For online version, see https://www.loc.gov/preservation/resources/rfs/index.html Introduction to the 2019-2020 revision ....................................................................... 2 I. Textual Works and Musical Compositions ............................................................ 4 i. Textual Works – Print .................................................................................................... 4 ii. Textual Works – Digital ................................................................................................ 6 iii. Textual Works – Electronic serials .............................................................................. 8 iv. Digital Musical Compositions (score-based representations) .................................. 11 II. Still Image Works ............................................................................................... 13 i. Photographs – Print .................................................................................................... 13 ii. Photographs – Digital ................................................................................................. 14 iii. Other Graphic Images – Print .................................................................................... 15 iv. Other Graphic Images – Digital ................................................................................. 16 v. Microforms ................................................................................................................
    [Show full text]
  • The Music Encoding Initiative As a Document-Encoding Framework
    12th International Society for Music Information Retrieval Conference (ISMIR 2011) THE MUSIC ENCODING INITIATIVE AS A DOCUMENT-ENCODING FRAMEWORK Andrew Hankinson1 Perry Roland2 Ichiro Fujinaga1 1CIRMMT / Schulich School of Music, McGill University 2University of Virginia [email protected], [email protected], [email protected] ABSTRACT duplication of effort that comes with building entire encoding schemes from the ground up. Recent changes in the Music Encoding Initiative (MEI) In this paper we introduce the new tools and techniques have transformed it into an extensible platform from which available in MEI 2011. We start with a look at the current new notation encoding schemes can be produced. This state of music document encoding techniques. Then, we paper introduces MEI as a document-encoding framework, discuss the theory and practice behind the customization and illustrates how it can be extended to encode new types techniques developed by the TEI community and how their of notation, eliminating the need for creating specialized application to MEI allows the development of new and potentially incompatible notation encoding standards. extensions that leverage the existing music document- 1. INTRODUCTION encoding platform developed by the MEI community. We also introduce a new initiative for sharing these The Music Encoding Initiative (MEI)1 is a community- customizations, the MEI Incubator. Following this, we driven effort to define guidelines for encoding musical present a sample customization to illustrate how MEI can documents in a machine-readable structure. The MEI be extended to more accurately capture new and unique closely mirrors work done by text scholars in the Text music notation sources.
    [Show full text]
  • Dynamic Generation of Musical Notation from Musicxml Input on an Android Tablet
    Dynamic Generation of Musical Notation from MusicXML Input on an Android Tablet THESIS Presented in Partial Fulfillment of the Requirements for the Degree Master of Science in the Graduate School of The Ohio State University By Laura Lynn Housley Graduate Program in Computer Science and Engineering The Ohio State University 2012 Master's Examination Committee: Rajiv Ramnath, Advisor Jayashree Ramanathan Copyright by Laura Lynn Housley 2012 Abstract For the purpose of increasing accessibility and customizability of sheet music, an application on an Android tablet was designed that generates and displays sheet music from a MusicXML input file. Generating sheet music on a tablet device from a MusicXML file poses many interesting challenges. When a user is allowed to set the size and colors of an image, the image must be redrawn with every change. Instead of zooming in and out on an already existing image, the positions of the various musical symbols must be recalculated to fit the new dimensions. These changes must preserve the relationships between the various musical symbols. Other topics include the laying out and measuring of notes, accidentals, beams, slurs, and staffs. In addition to drawing a large bitmap, an application that effectively presents sheet music must provide a way to scroll this music across a small tablet screen at a specified tempo. A method for using animation on Android is discussed that accomplishes this scrolling requirement. Also a generalized method for writing text-based documents to describe notations similar to musical notation is discussed. This method is based off of the knowledge gained from using MusicXML.
    [Show full text]
  • Scanscore 2 Manual
    ScanScore 2 Manual Copyright © 2020 by Lugert Verlag. All Rights Reserved. ScanScore 2 Manual Inhaltsverzeichnis Welcome to ScanScore 2 ..................................................................................... 3 Overview ...................................................................................................... 4 Quickstart ..................................................................................................... 4 What ScanScore is not .................................................................................... 6 Scanning and importing scores ............................................................................ 6 Importing files ............................................................................................... 7 Using a scanner ............................................................................................. 7 Using a smartphone ....................................................................................... 7 Open ScanScore project .................................................................................. 8 Multipage import ............................................................................................ 8 Working with ScanScore ..................................................................................... 8 The menu bar ................................................................................................ 8 The File Menu ............................................................................................ 9 The
    [Show full text]
  • Methodology and Technical Methods
    Recordare MusicXML: Methodology and Technical Methods Michael Good Recordare LLC Los Altos, California, USA [email protected] 17 November 2006 Copyright © 2006 Recordare LLC 1 Outline Personal introduction What is MusicXML? Design methodology Technical methods MusicXML use today Suitability for digital music editions Recommendations Future directions 17 November 2006 Copyright © 2006 Recordare LLC 2 My Background B.S. and M.S. in computer science from Massachusetts Institute of Technology B.S. thesis on representing scores in Music11 Trumpet on MIT Symphony Orchestra recordings available on Vox/Turnabout Opera and symphony chorus tenor; have performed for Alsop, Nagano, Ozawa Worked in software usability at SAP and DEC before founding Recordare in 2000 17 November 2006 Copyright © 2006 Recordare LLC 3 What is MusicXML? The first standard computer format for common Western music notation Covers 17th century onwards Available via a royalty-free license Supported by over 60 applications, including Finale, Sibelius, capella, and music scanners Useful for music display, performance, retrieval, and analysis applications Based on industry standard XML technology 17 November 2006 Copyright © 2006 Recordare LLC 4 The Importance of XML XML is a language for developing specialized formats like MusicXML, MathML, and ODF XML files can be read in any computer text editor Fully internationalized via Unicode The files are human readable as well as machine readable Each specialized format can use standard XML tools Allows musicians to leverage the large
    [Show full text]
  • Proposals for Musicxml 3.2 and MNX Implementation from the DAISY Music Braille Project
    Proposals for MusicXML 3.2 and MNX Implementation from the DAISY Music Braille Project 11 March 2019 Author: Haipeng Hu, Matthias Leopold With contributions from: Jostein Austvik Jacobsen, Lori Kernohan, Sarah Morley Wilkins. This document provides general suggestions on the implementation of MusicXML 3.2 and MNX formats, hoping they can be more braille-transcription-friendly. But it doesn't limit to the requirement of music braille transcription. Some of the points may also benefit the common transformation of musical data to be more accurately and clearly. Note: The word “text” in this document specifically means all non-lyrics texts, such as titles, composers, credit page information, as well as expression / technique / instructional texts applied to a staff or the whole system. A. MusicXML 3.2 Suggestions 1. If possible, implement a flow to include all system-wide texts (such as tempo texts, stage indications), lines (such as a line with text “poco a poco rit.”) and symbols (such as a big fermata or breath mark above the whole system), like the "global" section of MNX, so that all things in it can affect the whole score instead of the topmost staff or (in orchestra) piccolo and first violin staves. This can also ease part extraction. The position of the elements can be placed using the forward command. (e.g. in SATB choir pieces: sometimes breathing marks, dynamics and wedges are only written once in Soprano but are meant to apply to all voices; and in orchestral scores, tempo texts and overall indications are written above piccolo and first violin; and some big fermata or breath marks appear above every instrument category).
    [Show full text]
  • Access Control Models for XML
    Access Control Models for XML Abdessamad Imine Lorraine University & INRIA-LORIA Grand-Est Nancy, France [email protected] Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 2 Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 3 What is XML? • eXtensible Markup Language [W3C 1998] <files> "<record>! ""<name>Robert</name>! ""<diagnosis>Pneumonia</diagnosis>! "</record>! "<record>! ""<name>Franck</name>! ""<diagnosis>Ulcer</diagnosis>! "</record>! </files>" 4 What is XML? • eXtensible Markup Language [W3C 1998] <files>! <record>! /files" <name>Robert</name>! <diagnosis>! /record" /record" Pneumonia! </diagnosis> ! </record>! /name" /diagnosis" <record …>! …! </record>! Robert" Pneumonia" </files>! 5 XML for Documents • SGML • HTML - hypertext markup language • TEI - Text markup, language technology • DocBook - documents -> html, pdf, ... • SMIL - Multimedia • SVG - Vector graphics • MathML - Mathematical formulas 6 XML for Semi-Structered Data • MusicXML • NewsML • iTunes • DBLP http://dblp.uni-trier.de • CIA World Factbook • IMDB http://www.imdb.com/ • XBEL - bookmark files (in your browser) • KML - geographical annotation (Google Maps) • XACML - XML Access Control Markup Language 7 XML as Description Language • Java servlet config (web.xml) • Apache Tomcat, Google App Engine, ... • Web Services - WSDL, SOAP, XML-RPC • XUL - XML User Interface Language (Mozilla/Firefox) • BPEL - Business process execution language
    [Show full text]
  • Beyond PDF – Exchange and Publish Scores with Musicxml
    Beyond PDF – Exchange and Publish Scores with MusicXML MICHAEL GOOD! DIRECTOR OF DIGITAL SHEET MUSIC! ! APRIL 12, 2013! Agenda • Introduction to MusicXML • MusicXML status and progress in the past year • Possible future directions for MusicXML • Interactive discussions throughout What is MusicXML? • The standard open format for exchanging digital sheet music between applications • Invented by Michael Good at Recordare in 2000 • Developed collaboratively by a community of hundreds of musicians and software developers over the past 13 years • Available under an open, royalty-free license that is friendly for both open-source and proprietary software • Supported by over 160 applications worldwide What’s Wrong With Using PDF? • PDF: Portable Document Format • The standard format for exchanging and distributing final form documents • High graphical fidelity • But it has no musical knowledge – No playback – No alternative layouts – Limited editing and interactivity • PDF duplicates paper – it does not take advantage of the interactive potential for digital sheet music MusicXML Is a Notation Format • Music is represented using the semantic concepts behind common Western music notation • Includes both how a score looks and how it plays back • Includes low-level details of the appearance of a particular engraving, or the nuances of a particular performance – Allows transfer of music between applications with high visual fidelity – Also allows the visual details to be ignored when appropriate – The best display for paper is often not the best for
    [Show full text]
  • Recordare Case Study
    Recordare Case Study Recordare Case Study An Altova customer uses XMLSpy and DiffDog to develop MusicXML-based “universal translator” plugins for popular music notation programs. Overview Recordare® is a technology company focused on and Sibelius®. The list of MusicXML adopters also providing software and services to the musical includes optical scanning utilities like SharpEye or community. Their flagship products, the Dolet® capella-scan, music sequencers like Cubase, and plugin family, are platform-independent plugins beyond. Dolet increases the MusicXML support in for popular music notation programs, facilitating all of these programs and promotes interoperability the seamless exchange and interaction of sheet and the sharing of musical scores. music data files by leveraging MusicXML. In creating the Dolet plugins, Recordare used Dolet acts as a high quality translator between Altova's XML editor, XMLSpy, for editing and the MusicXML data format and other applications, testing the necessary MusicXML XML Schemas enabling users to work with these files on any con- and DTDs, and its diff/merge tool, DiffDog, for ceivable system, including industry leading notation regression testing. and musical composition applications Finale® The Challenge Music interchange between applications had Since its original release by Recordare in January traditionally been executed using the MIDI of 2004 (version 2.0 was released in June 2007), (Musical Instrument Digital Interface) file format, MusicXML has gained acceptance in the music a message transfer protocol that has its roots in notation industry with support in over 100 leading electronic music. MIDI is not an ideal transfer products, and is recognized as the de facto XML format for printed music, because it does not take standard for music notation interchange.
    [Show full text]
  • Deliverable 5.2 Score Edition Component V2
    Ref. Ares(2021)2031810 - 22/03/2021 TROMPA: Towards Richer Online Music Public-domain Archives Deliverable 5.2 Score Edition Component v2 Grant Agreement nr 770376 Project runtime May 2018 - April 2021 Document Reference TR-D5.2-Score Edition Component v2 Work Package WP5 - TROMPA Contributor Environment Deliverable Type Report Dissemination Level PU Document due date 28 February 2021 Date of submission 28 February 2021 Leader GOLD Contact Person Tim Crawford (GOLD) Authors Tim Crawford (GOLD), David Weigl, Werner Goebl (MDW) Reviewers David Linssen (VD), Emilia Gomez, Aggelos Gkiokas (UPF) TR-D5.2-Score Edition Component v2 1 Executive Summary This document describes tooling developed as part of the TROMPA Digital Score Edition deliverable, including an extension for the Atom text editor desktop application to aid in the finalisation of digital score encodings, a Javascript module supporting selection of elements upon a rendered digital score, and the Music Scholars Annotation Tool, a web app integrating this component, in which users can select, view and interact with musical scores which have been encoded using the MEI (Music Encoding Initiative) XML format. The most important feature of the Annotation Tool is the facility for users to make annotations to the scores in a number of ways (textual comments or cued links to media such as audio or video, which can then be displayed in a dedicated area of the interface, or to external resources such as html pages) which they ‘own’, in the sense that they may be kept private or ‘published’ to other TROMPA users of the same scores. These were the main requirements of Task 5.2 of the TROMPA project.
    [Show full text]
  • 2021-2022 Recommended Formats Statement
    Library of Congress Recommended Formats Statement 2021-2022 For online version, see Recommended Formats Statement - 2021-2022 (link) Introduction to the 2021-2022 revision ....................................................................... 3 I. Textual Works ...................................................................................................... 5 i. Textual Works – Print (books, etc.) ........................................................................................................... 5 ii. Textual Works – Digital ............................................................................................................................ 7 iii. Textual Works – Electronic serials .......................................................................................................... 9 II. Still Image Works ............................................................................................... 12 i. Photographs – Print ................................................................................................................................ 12 ii. Photographs – Digital............................................................................................................................. 13 iii. Other Graphic Images – Print (posters, postcards, fine prints) ............................................................ 14 iv. Other Graphic Images – Digital ............................................................................................................. 15 v. Microforms ...........................................................................................................................................
    [Show full text]
  • Framework for a Music Markup Language Jacques Steyn Consultant PO Box 14097 Hatfield 0028 South Africa +27 72 129 4740 [email protected]
    Framework for a music markup language Jacques Steyn Consultant PO Box 14097 Hatfield 0028 South Africa +27 72 129 4740 [email protected] ABSTRACT Montgomery), FlowML (Bert Schiettecatte), MusicML (Jeroen van Rotterdam), MusiXML (Gerd Castan), and Objects and processes of music that would be marked with MusicXML (Michael Good), all of which focus on subsets a markup language need to be demarcated before a markup of CWN. ChordML (Gustavo Frederico) focuses on simple language can be designed. This paper investigates issues to lyrics and chords of music. MML (Jacques Steyn) is the be considered for the design of an XML-based general only known attempt to address music objects and events in music markup language. Most present efforts focus on general. CWN (Common Western Notation), yet that system addresses only a fraction of the domain of music. It is In this paper I will investigate the possible scope of music argued that a general music markup language should objects and processes that need to be considered for a consider more than just CWN. A framework for such a comprehensive or general music markup language that is comprehensive general music markup language is XML-based. To begin with, I propose the following basic proposed. Such a general markup language should consist requirements for such a general music markup language. of modules that could be appended to core modules on a 2 REQUIREMENTS FOR A MUSIC MARKUP needs basis. LANGUAGE Keywords A general music markup language should Music Markup Language, music modules, music processes, S music objects, XML conform to XML requirements as published by the W3C 1 INTRODUCTION S use common English music terminology for The use of markup languages exploded after the element and attribute names introduction of the World Wide Web, particularly HTML, S which is a very simple application of SGML (Standard address intrinsic as well as extrinsic music objects General Markup Language).
    [Show full text]