DOCSLIB.ORG

Commentary Here's What's Wrong with XML-Defined Standards It Is

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Commentary Here's What's Wrong with XML-Defined Standards It Is COM-18-7987 Research Note R. Knox 30 December 2002 Commentary Here's What's Wrong With XML-Defined Standards It is relatively easy to construct XML standards for vertical domains. This has led to thousands of redundant and conflicting specifications. This chaos is the direct result of how these standards are developed. Extensible Markup Language (XML)-defined standards began with a number of vertically focused standards in 1999 (see Figure 1) but grew to an overwhelming number by 2001 (see Figure 2). Figure 1 All Tied Up With XML: 1999 Schema for OO Chemical Markup Financial Information XML (SOX) Weather Observation Language (CML) eXchange Markup Language XML Linking Markup Format (OMF) (FIXML) Language XML Forms Open MLS (Real Estate) (XLink) Architecture (XFA)Health Level 7 Resource Description Framework (RDF) Vector Markup (HL7) Language (VML) Signed Document Markup Open Trading Protocol (OTP) Language (SDML) Universal Commerce Synchronized Multimedia Language and Protocol Integration Language (SMIL) (UCLP) Commerce XML (cXML) Meta Content Document Commerce Business FrameworkObject Model (DOM) Library (CBL) (MCF) XML Metadata Extensible Forms Interchange (XMI) Description Language Bank Internet Open(XFDL) Software SmartX (Smart Card) Markup XML Data Payment Distribution (OSD) Language (SML) System Web Interface Scalable Vector XML Query Document Type Definition (DTD) Definition Graphics (SVG) Language (XML- Channel Definition Format Language (WIDL) QL) (CDF) Extensible Style XML-Electronic Language (XSL) Precision Graphics Markup Language (PGML) Web Data Interchange (XML-EDI) XML Namespaces Extensible Markup Collections Language (XML) Document Content XSL Transformations (XSLT) Information and Content Description (DCD) Exchange (ICE) Source: Gartner Research Gartner Entire contents © 2002 Gartner, Inc. All rights reserved. Reproduction of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The reader assumes sole responsibility for the selection of these materials to achieve its intended results. The opinions expressed herein are subject to change without notice. Figure 2. All Tied Up With XML: 2001 Geography MarkupOpen Health Care BIOpolymer Markup Language (BIOML) Straight Through Processing Markup Name and AddressHuman Markup Resources Language Markup (NAML) ExtensibleSchema Rights for OOMarkup XML Language (SOX) (XrML) AssociationLanguage (GML) for CooperativeRecords Operations XML Open Philanthropy XML Forms Language (STPML) Language (HRML)Human Markup Language Signed Document Markup Research and Development (ACORD) MusicXML eXchange Information(OPX)(HumanML) TechnologyArchitecture Markup (XFA)Language (SDML) Manufacturing Data Systems Inc XML Metal XML LanguageSociety (ITML)Predictive for Worldwide Model Markup Interbank Language Financial (MDSI-XML)EquationEpicentre of StateMarkup XML Exchange Language Format GeophysicalTelecommunication Markup Language Telecommunications Interchange Well (PMML)Log Markup Extensible CustomerStylesheet Identity Markup(eosML) ML Schools Interoperability(swiftML) Markup (TIM) Language (WellLogML)DirectoryFramework Services Markup (SIF) ExtensibleLanguage User (XSL) InterfaceLanguage (CIML) Research InformationLanguage eXchange (DSML) Markup Architecture, Engineering, Open MLS (real estate)Language (RIXML) LanguageFinancial (XUL) Information eXchange Security Assertion Markup Universal Construction XML (aecXML) XML Linking Language (XLink) MarkupRe-usable Language Data Markup (FIXML) Language (SAML) CommerceSystems Biology Web CollectionsElectronic Catalog Language and Language (RDML) Cell Markup Language Markup Language Bibliographic Markup XML (eCX) Protocol Weather Observation Markup (CellML) Molecular Dynamics(SBML) MarkupLegalXML Language (BiblioML)SoftwareSynchronization Open (UCLP) Format (OMF) Banner MarkupMeta Content Markup CommerceLanguage (MoDL) XML (cXML)XML Query Access Protocol (SOAP) Language (BannerML)Framework Language XMLPIPE for Environmental,(Partner InterfaceLanguage Process for Energy) (XML-QL) Commerce Business (MCF) (SyncML) Safety & OccupationalOpen Trading Protocol Library (CBL)Security Services Markup Vector Markup XML Court Interface (XCI)Language (S2ML) HealthSynchronized (esohXML.org) Multimedia(OTP) Extensible Forms Description Language Bioinformatic SequenceLanguage (VML) Integration Language (SMIL) Open Financial Exchange (OFX) (XFDL) Markup Language (BSML)The WellSchematicML Standard for the Exchange of Product Product Data Markup LanguageMeat (PDML)and Poultry User Interface Markup Project Virtual Model Data XML ( STEPml) Bank Internet Payment SystemVoice MarkupXML Language Language (UIML) Open Software Distribution (OSD) SmartX (smart card) Markup Instruments Markup Language Digital Property XML-Electronic (VoiceXML)DARPA Agent Markup Language (DAML) Language (SML)HealthResource Level 7 (HL7) Description Framework (RDF) Rights Data Interchange XML Metadata Extensible Media Commerce Scalable Vector Graphics (SVG) XML Forms (Xforms) XSL TransformationsJobM Channel Definition Format Language (DPRL) (XML-EDI) Interchange (XMI)Language (XMCL) Standards for TechnologyeXtensible in Business Reporting ExtensibleChemical Markup Language (CML)XML DataBase(XSLT)ExtensibleL Style (CDF) Web Modeling Language UniversalAutomotive Description, Retail Discovery(STAR)/XML and Language (XBRL) Markup Extensible 3D (X3D)(dbXML) Language (XSL)Integration (UDDI)Precision Graphics Markup Language Trading Partner (WebML) Business Rules for E-Commerce (BREC) Electronic Business XML (ebXML) LanguageAgreement MarkupFinancial Planning Markup LanguageDocument Object Model (DOM)XML Namespaces (PGML) (XML) Web InterfaceXML Data DefinitionWeb Services Description Language (WSDL) Multi-Channel AccessXML Language (tpaML)(FpML)Corpus Encoding Standard for XML (XCES)Virtual Instruments Meta Language (VIML) Construction ManufacturingLanguage and (WIDL)Document Content Description (DCD) Agricultural Markup Language(MAXML) Extensible Graph Markup and Distribution Extensible SpacecraftMarkup Markup LanguageGene Expression (SML) Robotic Markup Markup Language ((AgXML) RoboML)Info. and Content Language (cmdXML) Modelling Language (XGMML)Language (GEML)Document Type Definition (DTD) Exchange (ICE) Source: Gartner Research The number of XML-defined standards is still growing and today is in the thousands of often-closely- related, redundant and often-conflicting standards. This problematic situation is the direct result of how these standards are developed and of at least four different problems. There Are No Rules. There are no rules that say what the scope of an XML standard must be, how big or small it can be, or how it should be developed. A single company may develop and publish a standard for public development and use. This was done originally, for example, with TaXML (www.taxml.org) and Value Chain Markup Language (VCML — see www.vcml.net). On the other hand, a group with global companies and organizations as members may be involved, as is the case with electronic business XML — www.ebXML.org, sponsored by Organization for the Advancement of Structured Information Standards (OASIS) and the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT). Certainly the scope of a global tax initiative (for example, TaXML) is extremely complex and must ultimately involve many players if it is to be successful. However, as originally initiated, it was relatively easy for a single company to provide the impetus and direction for the work. Well, why not? There are no requirements that dictate which groups must be involved based on the scope and potential impact of the standard that is ultimately developed. It's Too Easy to Get Into the Standards Game. Because of the interest in the domain a standard covers, the groups convened to create them can be very large (in contrast to the original work on TaXML). For example, Extensible Business Reporting Language (XBRL; www.xbrl.org) is a standard for exchanging and analyzing financial information. As such, it concerns the accounting industry, investors, public and private companies, and regulators. More than 170 companies, associations and government organizations participate. HR-XML (www.hr-xml.org) is developing XML specifications to automate human-resources-related data exchange; it has approximately 120 participating companies and organizations. Although all member organizations don't participate in all aspects of the standards development work, many have some say or contribution to much of it, and they often have voting and COM-18-7987 Copyright 2002 30 December 2002 2 approval rights. The level of agreement required complicates and slows down the development process, and often results in standards meeting the requirements of a lowest common denominator. Some wonder why the World Wide Web Consortium (W3C) or OASIS doesn't supervise the standards work. The W3C's mission is to "lead the World Wide Web to its full potential by developing common protocols that promote its evolution and ensure its interoperability." Hence, its focus is on core standards like XML itself. OASIS is a global consortium that "drives the development, convergence and adoption of e-business standards." It
Load more

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]
  • XML a New Web Site Architecture
    XML A New Web Site Architecture Jim Costello Derek Werthmuller Darshana Apte Center for Technology in Government University at Albany, SUNY 1535 Western Avenue Albany, NY 12203 Phone: (518) 442-3892 Fax: (518) 442-3886 E-mail: [email protected] http://www.ctg.albany.edu September 2002 © 2002 Center for Technology in Government The Center grants permission to reprint this document provided this cover page is included. Table of Contents XML: A New Web Site Architecture .......................................................................................................................... 1 A Better Way? ......................................................................................................................................................... 1 Defining the Problem.............................................................................................................................................. 1 Partial Solutions ...................................................................................................................................................... 2 Addressing the Root Problems .............................................................................................................................. 2 Figure 1. Sample XML file (all code simplified for example) ...................................................................... 4 Figure 2. Sample XSL File (all code simplified for example) ....................................................................... 6 Figure 3. Formatted Page Produced
    [Show full text]
  • Rdfa in XHTML: Syntax and Processing Rdfa in XHTML: Syntax and Processing
    RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing A collection of attributes and processing rules for extending XHTML to support RDF W3C Recommendation 14 October 2008 This version: http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014 Latest version: http://www.w3.org/TR/rdfa-syntax Previous version: http://www.w3.org/TR/2008/PR-rdfa-syntax-20080904 Diff from previous version: rdfa-syntax-diff.html Editors: Ben Adida, Creative Commons [email protected] Mark Birbeck, webBackplane [email protected] Shane McCarron, Applied Testing and Technology, Inc. [email protected] Steven Pemberton, CWI Please refer to the errata for this document, which may include some normative corrections. This document is also available in these non-normative formats: PostScript version, PDF version, ZIP archive, and Gzip’d TAR archive. The English version of this specification is the only normative version. Non-normative translations may also be available. Copyright © 2007-2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract The current Web is primarily made up of an enormous number of documents that have been created using HTML. These documents contain significant amounts of structured data, which is largely unavailable to tools and applications. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites, and allowing browsing applications to improve the user experience: an event on a web page can be directly imported - 1 - How to Read this Document RDFa in XHTML: Syntax and Processing into a user’s desktop calendar; a license on a document can be detected so that users can be informed of their rights automatically; a photo’s creator, camera setting information, resolution, location and topic can be published as easily as the original photo itself, enabling structured search and sharing.
    [Show full text]
  • Semantic Web
    Semantic Web Ing. Federico Chesani Corso di Fondamenti di Intelligenza Artificiale M a.a. 2009/2010 7 Maggio 2010 Outline 1. Introduction a) The map of the Web (accordingly to Tim Berners-Lee) b) The current Web and its limits c) The Semantic Web idea d) Few examples of Semantic Web applications 2. Semantic Information (a bird’s eye view) a) Semantic Models b) Ontologies c) Few examples 3. Semantic Web Tools a) Unique identifiers -URI b) XML c) RDF and SPARQL d) OWL 4. Semantic Web: where are we? a) Problems against the success of SW proposal b) Critics against SW c) Few considerations d) Few links to start with The Web Map (by Berners-Lee) ©Tim Berners-Lee, http://www.w3.org/2007/09/map/main.jpg About the content Knowledge Representation Semantic Web Web The Web 1.0 … • Information represented by means of: – Natural language – Images, multimedia, graphic rendering/aspect • Human Users easily exploit all this means for: – Deducting facts from partial information – Creating mental asociations (between the facts and, e.g., the images) – They use different communication channels at the same time (contemporary use of many primitive senses) The Web 1.0 … • The content is published on the web with the principal aim of being “human-readable” – Standard HTML is focused on how to represent the content – There is no notion of what is represented – Few tags (e.g. <title>) provide an implicit semantics but … • … their content is not structured • … their use is not really standardized The Web 1.0 … We can identify the title by means of its representation (<h1>, <b>) … … what if tomorrow the designer changes the format of the web pages? <h1> <!-- inizio TITOLO --> <B> Finanziaria, il voto slitta a domani<br> Al Senato va in scena l&#039;assurdo </B> <!-- fine TITOLO --> </h1> The Web 1.0 … • Web pages contain also links to other pages, but ..
    [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]
  • Defining Data with DTD Schemas
    06_067232797X_ch03.qxd 10/18/05 9:41 AM Page 43 HOUR 3 Defining Data with DTD Schemas Computers are not intelligent. They only think they are. —Unknown One thing XML aims to solve is human error. Because of XML’s structure and rigidity as a language, there isn’t much room for error on the part of XML developers. If you’ve ever encountered an error at the bank (in their favor!), you can no doubt appreciate the significance of errors in critical computer systems. XML is rapidly being integrated into all kinds of computer systems, including financial systems used by banks. The rigidity of XML as a markup language will no doubt make these systems more robust. The facet of XML that allows errors to be detected is the schema, which is a construct that allows XML developers to define the format and structure of XML data. This hour introduces you to schemas, including the two major types that are used to define data for XML documents. The first of these schema types, DTDs, is examined in detail in this hour, while the latter is saved for a later lesson. This hour explores the inner workings of DTDs and shows you how to create DTDs from scratch. In this hour, you’ll learn . How XML allows you to create custom markup languages . The role of schemas in XML data modeling . The difference between the types of XML schemas . What constitutes valid and well-formed documents . How to declare elements and attributes in a DTD . How to create and use a DTD for a custom markup language Creating Your Own Markup Languages Before you get too far into this hour, I have to make a little confession.
    [Show full text]
  • HTML 4.01 Specification
    HTML 4.01 Specification HTML 4.01 Specification W3C Proposed Recommendation This version: http://www.w3.org/TR/1999/PR-html40-19990824 (plain text [786Kb], gzip’ed tar archive of HTML files [367Kb], a .zip archive of HTML files [400Kb], gzip’ed Postscript file [740Kb, 387 pages], a PDF file [3Mb]) Latest version: http://www.w3.org/TR/html40 Previous version: http://www.w3.org/TR/1998/REC-html40-19980424 Editors: Dave Raggett <[email protected]> Arnaud Le Hors <[email protected]> Ian Jacobs <[email protected]> Copyright © 1997-1999 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This specification defines the HyperText Markup Language (HTML), version 4.0 (subversion 4.01), the publishing language of the World Wide Web. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML, HTML 4.01 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4.01 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide. HTML 4.01 is an SGML application conforming to International Standard ISO 8879 -- Standard Generalized Markup Language [ISO8879] [p.351] . Status of this document This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C. 1 24 Aug 1999 14:47 HTML 4.01 Specification This document is a revised version of the 4.0 Recommendation first released on 18 December 1997 and then revised 24 April 1998 Changes since the 24 April version [p.312] are not just editorial in nature.
    [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]
  • Document Type Definition: Structure
    Introduction to XML: DTD Jaana Holvikivi Document type definition: structure Topics: – Elements – Attributes – Entities – Processing instructions (PI) – DTD design Jaana Holvikivi 2 DTD <!– Document type description (DTD) example (part) --> <!ELEMENT university (department+)> <!ELEMENT department (name, address)> <!ELEMENT name (#PCDATA)> <!ELEMENT address (#PCDATA)> • Document type description, structural description • one rule /element – name – content • a grammar for document instances • ”regular clauses" • (not necessary) Jaana Holvikivi 3 DTD: advantages • validating parsers check that the document conforms to the DTD • enforces logical use of tags • there are existing DTD standards for many application areas – common vocabulary Jaana Holvikivi 4 Well-formed documents • An XML document is well-formed if – its elements are properly nested so that it has a hierarchical tree structure, and all elements have an end tag (or are empty elements) – it has one and only one root element – complies with the basic syntax and structural rules of the XML 1.0 specification: • rules for characters, white space, quotes, etc. – and its every parsed entity is well-formed Jaana Holvikivi 5 Validity • An XML-document is valid if – it is well-formed – it has an attached DTD (or schema) – it conforms to the DTD (or schema) • Validity is checked with a validating parser, either – the whole document at once (”batch") – interactively Jaana Holvikivi 6 Document type declaration Shared <!DOCTYPE catalog PUBLIC ”-//ORG_NAME//DTD CATALOG//EN"> - flag(-/+) indicates
    [Show full text]