DOCSLIB.ORG

XML, XSD, and XSL

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
XML, XSD, and XSL e- business XML, XSD, and XSL Bryan Hogan IBM Terminology e- business World Wide Web Consortium (W3C) develops interoperable technologies (specifications, guidelines, software, and tools) to lead the Web to its full potential as a forum for information, commerce, communication, and collective understanding. (www.w3.org) Document Object Model (DOM) a W3C standard API which describes mechanisms for software developers and Web script authors to access and manipulate parsed XML (and HTML) content. The DOM is both platform-neutral and language-neutral Document Type Definition (DTD) a specification of the elements and attributes that are permitted in an XML document XML Schema a specification of the elements and attributes that are permitted in an XML document along with the datatypes for these artifacts 1 Terminology (continued) e- business Well-formed XML document an XML document that conforms to basic XML rules Valid XML document a well-formed XML document that conforms to the rules specified in a DTD Simple API for XML (SAX) a standard interface for event-based XML parsing Extensible Stylesheet Language Transformations (XSLT) A language for transforming XML documents via the application of stylesheets What is XML? e- business eXtensible Markup Language Markup language for describing data Simpler than predecessor SGML (Standard Generalized Markup Language) More versatile than HTML (HyperText Markup Language) Self-describing: XML documents can describe other XML documents (ie. XML schema) An open standard for defining and sharing data across diverse network topologies Mark Weitzel (IBM) 2 Why use XML? e- business XML data representation is human-readable, application-neutral, and language-neutral enabling universal interchange of data XML documents provide an intuitive mechanism for initializing structured data within an application. XML standard is open; therefore, costs are nominal HTML and XML side by side e- business <table border cellspacing=0 <football_game> cellpadding=5> <home> <tr> <school>NCSU</school> <th>Team name</th> <score>17</score> <th>Score</th> </home> </tr> <tr> <visitor> <td>Clemson</td> <school>Clemson</school> <td>15</td> <score>15</score> </tr> </visitor> <tr> </football_game> <td>NCSU</td> <td>17</td> </tr> </table> 3 XML document syntax e- business Element start/end tags <tag1></tag1> or <tag1/> <tag1></TAG1> <!– syntax error. XML is case sensitive Attributes <tag1 attribute1=“testValue” /> <tag1 enabled /> <!– syntax error. Allowed in HTML not XML Comments <!– This is an XML comment Entity references <tag1 attr1="&Entity1;"> Processing instructions <?xml version="1.0"?> XML document syntax e- business Character data sections (CDATA) <![CDATA [<tag1>test</tag1>] ]> Document type declarations <!DOCTYPE XmlMappingSpec SYSTEM "abtxmap.dtd" > <!DOCTYPE XmlMappingSpec SYSTEM "abtxmap.dtd" [ <!ENTITY entity1 “testValue1" > <!ENTITY entity2 “testValue2" > ]> 4 DTD syntax and terminology e- business Element type declarations <!ELEMENT Street (#PCDATA) > Usage: <Street>29 Oak Street</Street> Attribute list declarations <!ATTLIST name firstName CDATA #REQUIRED > <!ATTLIST car maker (Ford | GM | BMW) > Usage: <name firstName=“George” /> <car maker=“Ford” /> <!-- Not valid. Validating parser will flag error <car maker=“Mercury” /> DTD syntax and terminology e- business Entity declarations <!ENTITY IBM “International Business Machines” > <!ENTITY testDoc SYSTEM “http://mywebsite/testDoc.xml” > Usage: <Company>&IBM;</Company> <!– Inline the contents of the testDoc ENTITY <root>&testDoc;</root> Parameter entity declaration <!ENTITY % code_format “CDATA”> Notations declarations <!NOTATION Find_Help SYSTEM “Help System” > 5 DTD ELEMENT examples e- business An element with multiple required subelements. <!ELEMENT main (sub1, sub2, sub3) > A subelement (sub2) that occurs once or not at all. <!ELEMENT main (sub1, sub2?) > A subelement (sub2) that occurs one or more times. <!ELEMENT main (sub1, sub2+) > A subelement (sub2) that occurs zero or more times. <!ELEMENT main (sub1, sub2*) > An element that contains one of multiple elements. <!ELEMENT main (choice1 | choice2 | choice3) > DTD ATTLIST examples e- business #REQUIRED default indicates that an attribute must be specified in XML document instance. <!ATTLIST main attr1 CDATA #REQUIRED > #IMPLIED default indicates that an attribute is not required by the XML document instance. <!ATTLIST main attr1 CDATA #IMPLIED > #FIXED default indicates an attribute has a fixed value, and no other values are acceptable. Since the attribute value is fixed, it does NOT need to be specified in an instance document. <!ATTLIST main attr1 CDATA #FIXED “FixedValue” > Default value supplied. The default value will be used only if no value is supplied by XML document instance. <!ATTLIST main attr1 CDATA “DefaultValue” > 6 Parsing XML (DOM) e- business DOM parsers read XML into a tree structure of nodes. Node types are shown below: Document DocumentFragment DocumentType EntityReference Element Attr ProcessingInstruction Comment Text CDATASection Entity Notation DOM Element API e- business getAttribute, setAttribute, removeAttribute, getAttributeNode, setAttributeNode, removeAttributeNode, hasAttribute getAttributeNS, setAttributeNS, removeAttributeNS, getAttributeNodeNS, removeAttributeNodeNS, hasAttributeNS getElementsByTagName, getElementsByTagNameNS 7 Parsing XML (SAX) e- business SAX parsers generate parsing events that are processed by handlers in an application program. Parsers allow users to plug in custom implementations of the SAX interfaces. The SAX 2.0 interfaces are: Attributes ContentHandler DTDHandler EntityResolver ErrorHandler Locator XMLFilter XMLReader SAX ContentHandler interface e- business characters endDocument endElement endPrefixMapping ignorableWhitespace processingInstruction setDocumentLocator skippedEntity startDocument startElement startPrefixMapping 8 VAST XML parser e- business XML 1.0 specification http://www.w3.org/TR/1998/REC-xml-19980210 DOM level-2 core interfaces http://www.w3.org/TR/1998/REC-xml-19980210 SAX 2.0 http://www.saxproject.org/ Wedding planner DTD e- <!-- 3/10/2001 WildAndWackyWeddings.com retains information and performs billing for wedding planners. All wedding planners must provide records in the format specified by this DTD. --> business <!ELEMENT WeddingPlanner (Address,PhoneNumber,Weddings)> <!ATTLIST WeddingPlanner Name NMTOKEN #REQUIRED id ID #REQUIRED> <!ELEMENT WeddingPlanners (WeddingPlanner*) > <!ENTITY % AddressMembers 'Street,City,State,Zip' > <!ELEMENT Address (%AddressMembers;)> <!ELEMENT PhoneNumber (#PCDATA) > <!ELEMENT Street (#PCDATA) > <!ELEMENT City (#PCDATA) > <!ELEMENT State (#PCDATA) > <!ELEMENT Zip (#PCDATA) > <!ELEMENT Weddings (Wedding)* > <!ELEMENT Wedding (Bride,Groom,Date,Time,CeremonyLocation,ReceptionLocation,Caterer,NumberOfGuests,TotalFee,BillingAddress)> <!ATTLIST Wedding id ID #REQUIRED > <!ELEMENT Bride (#PCDATA) > <!ELEMENT Groom (#PCDATA) > <!ELEMENT BillingAddress (%AddressMembers;) > <!ELEMENT CeremonyLocation (FacilityName,Address) > <!ELEMENT ReceptionLocation (FacilityName,Address) > <!ELEMENT Date (#PCDATA) > <!ELEMENT Time (#PCDATA) > <!ELEMENT Caterer (#PCDATA) > <!ELEMENT NumberOfGuests (#PCDATA) > <!ELEMENT TotalFee (#PCDATA) > <!ELEMENT FacilityName (#PCDATA) > 9 Valid XML document e- <?xml version="1.0"?> business <!DOCTYPE WeddingPlanner SYSTEM "wedding.dtd" > <WeddingPlanner Name="J-Lo" id="Planner_1" > <Address> <Street>29 Oak St.</Street> <City>Raleigh</City> <State>NC</State> <Zip>99999</Zip> </Address> <PhoneNumber>555-4343</PhoneNumber> <Weddings> <Wedding id="Ghezzo.G"> <!-- Detailed wedding information removed ... --> </Wedding> </Weddings> </WeddingPlanner> VAST XML parser example e- business " Validating parser used to read well-formed XML and verify that the contents conform to the DTD referenced in the XML." | domDocument domElement | domDocument := AbtXmlDOMParser newValidatingParser parseURI: ‘d:\ncsu_2003\wedding1.xml’. domElement := domDocument getElementById: ‘Planner_1’. " Non-validating parser used to read well-formed XML data. " | domDocument domElements | domDocument := AbtXmlDOMParser newNonValidatingParser parseURI: ‘d:\ncsu_2003\wedding1.xml’. domElements := domDocument getElementsByTagName: ‘Address’. 10 XML namespaces e- business An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names. In an XML instance document, items are namespace qualified using a namespace prefix. The reserved word xmlns is used to associate an arbitrary namespace prefix with the actual namespace. Items in the document instance are prefixed to identify the namespace containing their definition. XML namespace example e- <?xml version="1.0"?> business <vastwsd:deployment targetNamespace="urn:SstWSInsurancePolicyInterface" xmlns:vastwsd="urn:VASTWebServiceDeployment600" xmlns:vast="Smalltalk" xmlns:swsipi="urn:Test"> <services> <service name="SstWSInsurancePolicyInterface" namespace="urn:Test"> <serviceInterfaceClass>SstWSService</serviceInterfaceClass> <provider type="swsipi:TestProvider"> <vast:provider className=“TestClass" creationMethod="new"/> </provider> </service> </services> </vastwsd:deployment> 11 XML schema e- business ° XML schema improves on XML DTD ° XML schemas are coded in XML ° XML schema includes type information allowing object models to be represented ° The W3C XML Schema Primer is a great resource for
Load more

Recommended publications
  • <?Xml Version="1.0" Encoding="Iso
    <?xml version="1.0" encoding="iso-8859-1"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <title>BCS Website Services- valid html and css code</title> <meta name="author" content="Administrator" /> <meta name="description" content="Read about the importance of using valid HTML coding in your web site design." /> <meta name="keywords" content="valid,html,css,code,coding,web site design" /> <meta name="robots" content="INDEX,FOLLOW" /> <script type="text/javascript" src="http://www.bcswebsiteservices.com/mambots/system/jceutils/jscripts/jquery.js"></script> <script type="text/javascript" src="http://www.bcswebsiteservices.com/mambots/system/jceutils/jscripts/utils.js"></script> <script type="text/javascript" src="http://www.bcswebsiteservices.com/mambots/system/jceutils/jscripts/embed.js"></script> <link href="http://www.bcswebsiteservices.com/mambots/system/jceutils/css/jcebox.css" rel="stylesheet" type="text/css" media="all"/> <!--[if IE]><link href="http://www.bcswebsiteservices.com/mambots/system/jceutils/css/jcebox_ie.css" rel="stylesheet" type="text/css" media="all"/><![endif]--> <script type="text/javascript"> jQuery.noConflict(); jceUtils.config.convert=1; jceUtils.config.resize=1; jceUtils.config.overlay=1; jceUtils.config.overlay_opacity=0.6; jceUtils.config.fadespeed=500; jceUtils.config.scalespeed=500; jceUtils.config.pngfix=0;
    [Show full text]
  • Information Integration with XML
    Information Integration with XML Chaitan Baru Richard Marciano {baru,marciano}@sdsc.edu Data Intensive Computing Environments (DICE) Group San Diego Supercomputer Center National Partnership for Advanced Computational Infrastructure San Diego Supercomputer Center Members of the DICE Group • Staff • Students • Chaitan Baru • Pratik Mukhopadhyay • Amarnath Gupta • Azra Mulic • Bertram Ludäscher • Kevin Munroe • Richard Marciano • Paul Nguyen • Reagan Moore • Michail Petropolis • Yannis Papakonstantinou • Nicholas Puz • Arcot Rajasekar • Pavel Velikhov • Wayne Schroeder • Michael Wan • Ilya Zaslavsky Tutorial Outline • PART I • Introduction to XML • The MIX Project • PART II • Storing/retrieving XML documents • XML and GIS • Open Issues Information Integration with XML PART I • Introduction to XML • HTML vs. XML • XML Industry Initiatives • DTD, Schema, Namespaces • DOM, SAX • XSL, XSLT • Tools • The MIX Project Introduction to XML • SGML (Standard Generalized Markup Language) • ISO Standard, 1986, for data storage & exchange • Used in U.S. gvt. & contractors, large manufacturing companies, technical info. Publishers. • HTML, a simple application of SGML, 1992 - 1999 • SGML reference is 600 pages long • XML (eXtensible Markup Language) • W3C (World Wide Web Consortium) -- http://www.w3.org/XML/) recommendation in 1998 • Simple subset of SGML: “The ASCII of the Web”. • XML specification is 26 pages long • Canonical XML • equivalence testing of XML documents • SML (Simple Markup Language) • No Attributes / No Processing Instructions (PI) /
    [Show full text]
  • Extensible Markup Language (XML)
    Extensible Markup Language (XML) Pat Morin COMP 2405 Outline · What is XML? · XML versus HTML · Simple XML Documents · XML Document Type Definitions · Example DTDs · XML Schema · XML and CSS · XHTML Examples taken from http://www.w3schools.com/ 2 What is XML? · Stands for Extensible Markup Language · Similar to HTML · Used to describe data · Has no predefined tags · Uses a Document Type Definition (DTD) or XML Schema to describe data ± XML Data is self-describing 3 XML Versus HTML · XML and HTML are both markup languages · HTML is for displaying data · XML is for describing data · XHTML is a version HTML in XML · XML does not DO anything ± Designed to structure and store information only ± Applications that use XML are what do things 4 XML Tags · XML tags are similar to HTML tags but ± They are case-sensitive ± All tags must be closed · Like HTML tags they must be properly nested · All XML documents must have a single root element that contains all other elements ± This root element can have any name · All XML attribute values must be quoted 5 Simple Example · Note: The first line is not an XML tag <?xml version="1.0" encoding="ISO-8859-1"?> <!-- This is my first picture --> <picture title="My First Picture"> <polygon boundary=”r ed” interiorr=”# fefefe”> <point x="0" y="0"/> <point x="0" y="1"/> <point x="1" y="1"/> <point x="1" y="0"/> </polygon> </picture> 6 XML Content · XML elements have different kinds of content ± Element content - tags ± Simple/Text content – plain text (no tags) ± Mixed content – simple and element content ± Empty
    [Show full text]
  • XHTML, Step by Step Move Beyond Tag Soup to Create Sites That Truly Separate Content from Presentation
    XHTML, step by step Move beyond tag soup to create sites that truly separate content from presentation Skill Level: Introductory Uche Ogbuji ([email protected]) Principal Consultant Fourthought Inc. 06 Sep 2005 Get started working with Extensible Hypertext Markup Language. XHTML is a language based on HTML, but expressed in well-formed XML. However, XHTML has more to offer than just regularizing tags and characters -- XHTML can alter the way you approach Web design. This tutorial gives step-by-step instruction for developers familiar with HTML who want to learn how to use XHTML in practical Web sites. Section 1. Tutorial introduction Introducing XHTML This tutorial offers step-by-step instruction for developers familiar with HTML who want to learn how to use XHTML in practical Web sites. XHTML is more than just an XML-compliant variation. It also opens up the first step in advancing from tag soup Web sites to sites that properly separate content from presentation, and thus save time and money in maintenance. The focus of this tutorial will be XHTML 1.1, with the occasional mention of XHTML 2.0. The lessons are built around examples that readers can view and experiment with in their favorite browser. Who should take this tutorial? XHTML, step by step © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 1 of 27 developerWorks® ibm.com/developerWorks XHTML is important in all areas of Web design and management. It is broadly applicable, and yet relatively easy to pick up for those already familiar with HTML and XML. Web designers should take this tutorial to learn how to develop well-formed pages.
    [Show full text]
  • XML Tutorial: Overview
    XML tutorial: Overview Contents 1. HTML and XML - structuring information for the future (21 pp.) 2. Namespaces, XInclude, and XML Base - common extensions to the XML specification (8 pp.) 3. DTD, XML Schema, and DSD - defining language syntax with schemas (27 pp.) 4. XLink, XPointer, and XPath - linking and addressing (24 pp.) 5. XSL and XSLT - stylesheets and document transformation (19 pp.) 6. XQuery - document querying (15 pp.) 7. DOM, SAX, and JDOM - programming for XML (15 pp.) 8. W3C - some background on the World Wide Web Consortium (5 pp.) http://www.brics.dk/~amoeller/XML/overview.html [4/9/2002 4:43:22 PM] XML tutorial: HTML and XML THE XML REVOLUTION - TECHNOLOGIES FOR THE FUTURE WEB Markup Languages: HTML and XML HTML - original motivation, development, and inherent limitations: ● Hyper-Text Markup Language - the Web today ● Original motivation for HTML - some history ● Compact and human readable - alternative document formats ● From logical to physical structure - requirements from users ● Stylesheets - separating logical structure and layout ● Different versions of HTML - a decade of development ● Syntax and validation - HTML as a formal language ● Browsers are forgiving - the real world ● Structuring general information - not everything is hypertext ● Problems with HTML - why HTML is not the solution XML as the universal format for structuring information: ● What is XML? - the universal data format ● HTML vs. XML - the key differences ● A conceptual view of XML - XML documents as labeled trees ● A concrete view of XML - XML documents as text with markup ● Applications of XML - an XML language for every domain ● The recipe example - designing a small XML language ● From SGML to SML - a word on doc-heads and development ● SGML relics - things to avoid ● XML technologies - generic languages and tools for free Selected links: ● Basic XML tools ● Links to more information COPYRIGHT © 2001 ANDERS MØLLER & MICHAEL I.
    [Show full text]
  • XML-Tutorial2017.Pdf
    XML About the Tutorial XML stands for Extensible Markup Language and is a text-based markup language derived from Standard Generalized Markup Language (SGML). This tutorial will teach you the basics of XML. The tutorial is divided into sections such as XML Basics, Advanced XML, and XML tools. Each of these sections contain related topics with simple and useful examples. Audience This reference has been prepared for beginners to help them understand the basic to advanced concepts related to XML. This tutorial will give you enough understanding on XML from where you can take yourself to a higher level of expertise. Prerequisites Before proceeding with this tutorial, you should have basic knowledge of HTML and JavaScript. Copyright & Disclaimer ¬ Copyright 2017 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify us at [email protected] i XML Table of Contents About the Tutorial ............................................................................................................................................ i Audience ........................................................................................................................................................... i Prerequisites ....................................................................................................................................................
    [Show full text]
  • Web Programming Meta-Markup Languages
    Web Programming Lecture 6 – Introduction to XML Meta-markup Languages • A markup language allows the user to identify individual elements of a document, e.g., what is a paragraph, a heading, or an unordered list. • Used in combination with a style sheets, data can be properly presented on a web page, a slide show, or any other method that is appropriate for the data. 1 Meta-markup Languages • A meta-markup language is a little different; it doesn't specify a document – it specifies a language . • SGML ( Standard Generalized Markup Language) and XML (e Xtensible Markup Language) are examples of meta-markup languages. SGML • SGML was based on GML ( Generalized Markup Language), which was developed at IBM in the 1960s. SGML was developed in 1974. • SGML was intended to allow for the sharing of machine-readable documents. • While it was used in the printing and publishing industry, its complexity kept it from wider use. • SGML was used as the basis for HTML. 2 XML • HTML describes the layout of information but conveys no information about its meaning. This limits the ability to retrieve information from an HTML document automatically. • One solution to get around HTML's limitation is for groups of users to define and use their own set of tags and attribute and use a meta-markup language to implement them. • XML is a simpler language than SGML and therefore more useful. Using XML • XML is not a replacement for XHTML. It is intended to provide a way to label data in a way that can be analyzed and manipulated automatically.
    [Show full text]
  • Chapter 1: XML Syntax
    1. XML Syntax 1-1 Chapter 1: XML Syntax References: • Boc DuCharme: XML | The Annotated Specification. Prentice Hall, 1999. • Tim Bray, Jean Paoli, C.M. Sperberg-McQueen: Extensible Markup Language (XML) 1.0, 1998. [http://www.w3.org/TR/REC-xml] See also: [http://www.w3.org/XML]. • Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, Fran¸coisYergeau, John Cowan: Extensible Markup Language (XML) 1.1 (Second Edition), W3C Recommendation 16 August 2006, edited in place 29 September 2006. [http://www.w3.org/TR/xml11]. • Elliotte Rusty Harold, W. Scott Means: XML in a Nutshell, A Desktop Quick Ref., 3rd Ed. O'Reilly, Okt. 2004, ISBN 0-596-00764-7, 689 Seiten, 37 Euro. Stefan Brass: XML und Datenbanken Universit¨atHalle, 2012 1. XML Syntax 1-2 Objectives After completing this chapter, you should be able to: • write syntactically correct XML. • check given XML documents for syntax errors. • explain the tree-structure of XML data. • read XML Document Type Definitions (DTDs). • validate an XML document against a given DTD. Stefan Brass: XML und Datenbanken Universit¨atHalle, 2012 1. XML Syntax 1-3 Overview 1. Introduction 2. XML Documents (Syntax) 3. Document Type Definitions (DTDs) 4. DOCTYPE, XML Declaration 5. Entities, Notations, Marked Sections Stefan Brass: XML und Datenbanken Universit¨atHalle, 2012 1. XML Syntax 1-4 Introduction (1) • XML (\eXtensible Markup Language") is basically a simplification (subset) of SGML (\Standard Ge- neralized Markup Language"). SGML is an ISO-Standard since 1986. XML was developed mainly 1996, and became an W3C Recommendation on February 10, 1998. The current version is XML 1.1 (2nd Ed.) from August 2006.
    [Show full text]
  • Xpath Quick Reference
    3243chAppA.qxd 6/20/05 10:34 AM Page 697 APPENDIX A ■ ■ ■ XPath Quick Reference This appendix gives you a quick guide to XPath, including its syntax and a guide to all the functions that are available to you. Sequences Every XPath expression returns a sequence, which can be empty or hold any number of items. Items can be nodes or atomic values. Nodes Nodes can be of the kinds shown in Table A-1. Table A-1. Node Kinds Node Kind Name String Value Document - Concatenation of all text nodes in the document Element Element name Depends on element type Attribute Attribute name Depends on attribute type Text - Text Comment - Text held within the comment Processing instruction Processing instruction target Text in the processing instruction after the space after the target name Namespace Namespace prefix Namespace URI Node Types Element and attribute nodes can be annotated with a type based on validation against a schema. The types, string values, and typed values of element and attribute nodes are summarized in Table A-2. 697 3243chAppA.qxd 6/20/05 10:34 AM Page 698 698 APPENDIX A ■ XPATH QUICK REFERENCE Table A-2. Node Types Node Kind Validity Type String Value Typed Value Element Unvalidated xdt:untyped Concatenation String value as of all text node xdt:untypedAtomic descendants value Element Invalid or xdt:anyType Concatenation String value as partially validated of all text node xdt:untypedAtomic descendants value Element Valid Simple Text with Sequence of items of whitespace appropriate type normalized based on type Element Valid Mixed Concatenation
    [Show full text]
  • Introduction to XML (Extensible Markup Language)
    Introduction to XML (Extensible Markup Language) 3/31/2008 USC - CSCI585 - Spring 2008 - Farnoush Banaei-Kashani 1 History and References XML is a meta-language, a simplified form of SGML (Standard Generalized Markup Language) XML was initiated in large parts by Jon Bosak of Sun Microsystems, Inc., through a W3C working group References: 1. “XML Pocket Reference,” Robert Eckstein, O’Reilly & Associates, Inc., 1999 2. “Describing and Manipulating XML Data,” Sudarshan S. Chawathe, Bulletin of Data Engineering, v22, n3, Sept. 99 3. “XML Schema Tutorial,” Roger L. Costello http://www.xfront.com/ 4. XML namespaces: http://www.w3.org/TR/1999/REC-xml-names-19990114/ 5. XML specifications: http://www.w3.org/TR/REC-xml/ 6. XML Schema Part 0: Primer http://www.w3.org/TR/xmlschema-0/ 7. XML Schema Part 1: Structures http://www.w3.org/TR/xmlschema-1/ 8. XML Schema Part 2: Datatypes http://www.w3.org/TR/xmlschema-2/ 9. WWW Consortium XML Site: http://www.w3.org/XML/ 10. XML Namespaces Tutorial: http://zvon.org/xxl/NamespaceTutorial/Output/index.html 11. XML Tutorials: http://www.zvon.org/index.php?nav_id=tutorials&mime=html 12. XSL: http://www.w3.org/TR/xsl and http://www.w3.org/TR/xslt 3/31/2008 USC - CSCI585 - Spring 2008 - Farnoush Banaei-Kashani 2 Overview An XML compliant application generally needs three files to display XML content: The XML document • Contains the data tagged with meaningful XML elements A document type definition – DTD or Schema • Specifies the rules how elements and attributes are logically related A stylesheet • Dictates the formatting when the XML document is displayed.
    [Show full text]
  • PDF Documentation
    lxml 2018-03-13 Contents Contents 2 I lxml 13 1 lxml 14 Introduction................................................. 14 Documentation............................................... 14 Download.................................................. 15 Mailing list................................................. 16 Bug tracker................................................. 16 License................................................... 16 Old Versions................................................. 16 2 Why lxml? 17 Motto.................................................... 17 Aims..................................................... 17 3 Installing lxml 19 Where to get it................................................ 19 Requirements................................................ 19 Installation................................................. 20 MS Windows............................................. 20 Linux................................................. 20 MacOS-X............................................... 20 Building lxml from dev sources....................................... 21 Using lxml with python-libxml2...................................... 21 Source builds on MS Windows....................................... 21 Source builds on MacOS-X......................................... 21 4 Benchmarks and Speed 22 General notes................................................ 22 How to read the timings........................................... 23 Parsing and Serialising........................................... 23 The ElementTree
    [Show full text]
  • Answer Any 5 Full Questions. Sub: Programming The
    CMR INSTITUTE OF USN TECHNOLOGY Internal Assessment Test 2 – November 2016 Sub: Programming The WEB Code: 10CS73 Date: 03/ 11/ 16 Duration: 90 Mins Max Marks: 50 Sem: VII A,B Branch: CSE/ISE Note: Answer to the point. Sketch figures wherever necessary. Answer any 5 full questions. Marks CO RBT 1 a) Declare a XML document containing data of 3 Eploees (ep_id, ep_ae, emp_designation, emp_age, emp_phone, emp_address) display this XML using CSS , with following rules :emp_id in font size 28pt and color red, emp_name and emp_designation in 6M CO3 L3 font size 18 pt and color blue ,emp_age , emp_phone and emp_address in font size 15pt and color black b) Explain the following tags with example: i) <div> ii) <span> 4M CO1 L3 2 a) Write an XHTML document that has six short paragraphs of text. Define three different paragraph styles p1, p2, and p3. The p1 style must use left and right margins of 20 pixels, a background color of yellow and a fore ground color of blue. The p2 style must use font size of 5M CO1 L3 18 poits, fot ae Arial ad fot stle i italic for. The p3 stle ust use a tet indent of 1 cm, a background color of green, and foreground color of white. The 1st and 4th paragraph must use p1,the second and 5th must use p2, and 3rd and 6th must use p3? b) What is XML Schema? Explain defining schema with example? 5M CO3 L2 3 Explain the different selector forms provided in CSS. Illustrate the use of each with suitable 10M CO1 L2 example 4 a)What is a query string? How is it transmitted to the server with the GET and POST 5M CO4 L2 methods? b) Explain the string functions in Perl with example 5M CO4 L1 5 What is DTD? What is the difference between External and Internal DTDs? Write the syntax 10M CO3 L2 and example for declaring elements , Attributes and Entities ,CDATA,PCDATA? 6 a)Illustrate with the help of a diagram the XSLT processing? 4M CO3 L1 b) Describe with example various types of variables in Perl.
    [Show full text]