DOCSLIB.ORG

Best Practices for XML Internationalization

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Best Practices for XML Internationalization Best Practices for XML Internationalization W3C Working Group Note 13 February 2008 This version: http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/ Latest version: http://www.w3.org/TR/xml-i18n-bp/ Previous version: http://www.w3.org/TR/2007/WD-xml-i18n-bp-20071031/ Editors: Yves Savourel, ENLASO Corporation Jirka Kosek, Invited Expert Richard Ishida, W3C This document is also available in these non-normative formats: PDF version1 and XHTML Diff markup to publication from 31 October 20072. Copyright3 © 2008 W3C4® (MIT5, ERCIM6, Keio7), All Rights Reserved. W3C liability8, trademark9 and document use10 rules apply. Abstract This document provides a set of guidelines for developing XML documents and schemas that are internationalized properly. Following the best practices describes here allow both the de- veloper of XML applications, as well as the author of XML content to create material in different languages. Status of this Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/. 1 ⇢ http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/xml-i18n-bp.pdf 2 ⇢ http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/xml-i18n-bp-diff.html 3 ⇢ http://www.w3.org/Consortium/Legal/ipr-notice#Copyright 4 ⇢ http://www.w3.org/ 5 ⇢ http://www.csail.mit.edu/ 6 ⇢ http://www.ercim.org/ 7 ⇢ http://www.keio.ac.jp/ 8 ⇢ http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer 9 ⇢ http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks 10 ⇢ http://www.w3.org/Consortium/Legal/copyright-documents – 1 – Best Practices for XML Internationalization This is a W3C Working Group Note11 of "Best Practices for XML Internationalization". This document was developed by the Internationalization Tag Set (ITS) Working Group12, part of the W3C Internationalization Activity13. Feedback about this document is encouraged. Send your comments to www-i18n-com- [email protected]. Use "[Comment on xml-i18n-bp WD]" in the subject line of your email, followed by a brief subject. The archives14 for this list are publicly available. Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. This document was produced by a group operating under the 5 February 2004 W3C Patent Policy15. W3C maintains a public list of any patent disclosures16 made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An indi- vidual who has actual knowledge of a patent which the individual believes contains Essential Claim(s)17 must disclose the information in accordance with section 6 of the W3C Patent Policy18. 11 ⇢ http://www.w3.org/2005/10/Process-20051014/tr.html#WGNote 12 ⇢ http://www.w3.org/International/its/ 13 ⇢ http://www.w3.org/International/Activity 14 ⇢ http://lists.w3.org/Archives/Public/www-i18n-comments/ 15 ⇢ http://www.w3.org/Consortium/Patent-Policy-20040205/ 16 ⇢ http://www.w3.org/2004/01/pp-impl/37139/status 17 ⇢ http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential 18 ⇢ http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure – 2 – Best Practices for XML Internationalization Table of Contents 1 Introduction............................................................................................................................5 1.1 Who should use this document.....................................................................................5 1.2 How to use this document.............................................................................................5 1.2.1 Designers and developers of XML applications...................................................5 1.2.2 Users and authors of XML content.......................................................................5 2 When Designing an XML Application....................................................................................6 Best Practice 1: Defining markup for natural language labelling......................................10 Best Practice 2: Defining markup to specify text direction................................................13 Best Practice 3: Avoiding translatable attribute values.....................................................15 Best Practice 4: Indicating which elements and attributes should be translated..............17 Best Practice 5: Defining markup to override translate information..................................19 Best Practice 6: Providing information related to text segmentation.................................21 Best Practice 7: Defining markup for ruby text..................................................................23 Best Practice 8: Defining markup for notes to localizers...................................................25 Best Practice 9: Defining markup for unique identifiers....................................................28 Best Practice 10: Identifying terminology-related elements..............................................29 Best Practice 11: Defining markup for specifying or overriding terminology-related information........................................................................................................................31 Best Practice 12: Working with multilingual documents....................................................32 Best Practice 13: Naming elements and attributes...........................................................34 Best Practice 14: Defining a span-like element................................................................36 Best Practice 15: Documenting internationalization and localization features of your schema..............................................................................................................................37 3 When Authoring XML Content.............................................................................................39 Best Practice 16: Specifying the language of content.......................................................40 Best Practice 17: Specifying text directionality.................................................................43 Best Practice 18: Overriding information about what should be translated......................45 Best Practice 19: Assigning unique identifiers..................................................................48 Best Practice 20: Avoiding CDATA sections.....................................................................49 Best Practice 21: Providing notes for localizers................................................................52 Best Practice 22: Working with inserted text.....................................................................54 Best Practice 23: Identifying terms...................................................................................57 Best Practice 24: Storing markup from another format.....................................................59 4 Generic Techniques.............................................................................................................61 4.1 Writing ITS Rules........................................................................................................61 4.1.1 Precedence and Inheritance...............................................................................61 4.1.2 Dealing with namespaces...................................................................................62 4.1.3 Create your XPath expressions with care..........................................................64 4.2 Example of adding an attribute to an existing schema...............................................65 4.2.1 Including xml:lang in XML Schema....................................................................65 4.2.2 Including xml:lang in RELAX NG........................................................................65 4.2.3 Including xml:lang in an XML DTD.....................................................................66 5 ITS Applied to Existing Formats..........................................................................................67 5.1 ITS and XHTML 1.0....................................................................................................67 5.1.1 Integrating ITS into XHTML................................................................................67 5.1.2 Using XHTML Modularization 1.1 for the Definition of ITS.................................69 5.1.3 Using NVDL to integrate ITS into XHTML..........................................................74 5.1.4 Associating existing XHTML markup with ITS....................................................76 5.2 ITS and TEI.................................................................................................................78 5.2.1 Integrating ITS into TEI.......................................................................................78 – 3 – Best Practices for XML Internationalization 5.3 ITS and XML Spec......................................................................................................80 5.3.1 Integration of ITS into XML Spec........................................................................80 5.3.2 Associating existing XML Spec markup with ITS...............................................83 5.4 ITS
Recommended publications
  • Specification for JSON Abstract Data Notation Version

    Specification for JSON Abstract Data Notation Version

    Standards Track Work Product Specification for JSON Abstract Data Notation (JADN) Version 1.0 Committee Specification 01 17 August 2021 This stage: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.html https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.pdf Previous stage: https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.html https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.pdf Latest stage: https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.md (Authoritative) https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.html https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.pdf Technical Committee: OASIS Open Command and Control (OpenC2) TC Chair: Duncan Sparrell ([email protected]), sFractal Consulting LLC Editor: David Kemp ([email protected]), National Security Agency Additional artifacts: This prose specification is one component of a Work Product that also includes: JSON schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.json JADN schema for JADN documents: https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/schemas/jadn-v1.0.jadn Abstract: JSON Abstract Data Notation (JADN) is a UML-based information modeling language that defines data structure independently of data format.
  • Bibliography of Erik Wilde

    Bibliography of Erik Wilde

    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
  • Darwin Information Typing Architecture (DITA) Version 1.3 Draft 29 May 2015

    Darwin Information Typing Architecture (DITA) Version 1.3 Draft 29 May 2015

    Darwin Information Typing Architecture (DITA) Version 1.3 Draft 29 May 2015 Specification URIs This version: http://docs.oasis-open.org/dita/dita/v1.3/csd01/dita-v1.3-csd01.html (Authoritative version) http://docs.oasis-open.org/dita/dita/v1.3/csd01/dita-v1.3-csd01.pdf http://docs.oasis-open.org/dita/dita/v1.3/csd01/dita-v1.3-csd01-chm.zip http://docs.oasis-open.org/dita/dita/v1.3/csd01/dita-v1.3-csd01-xhtml.zip Previous version: Not applicable Latest version: http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-csd01.html (Authoritative version) http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-csd01.pdf http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-csd01-chm.zip http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-csd01-xhtml.zip Technical committee: OASIS Darwin Information Typing Architecture (DITA) TC Chair: Kristen James Eberlein ([email protected]), Eberlein Consulting LLC Editors: Robert D. Anderson ([email protected]), IBM Kristen James Eberlein ([email protected]), Eberlein Consulting LLC Additional artifacts: This prose specification is one component of a work product that also includes: OASIS DITA Version 1.3 RELAX NG: http://docs.oasis-open.org/dita/dita/v1.3/csd01/schemas/ DITA1.3-rng.zip OASIS DITA Version 1.3 DTDs: http://docs.oasis-open.org/dita/v1.3/os/DITA1.3-dtds.zip OASIS DITA Version 1.3 XML Schemas: http://docs.oasis-open.org/dita/v1.3/os/DITA1.3-xsds.zip DITA source that was used to generate this document: http://docs.oasis-open.org/dita/dita/v1.3/ csd01/source/DITA1.3-source.zip Abstract: The Darwin Information Typing Architecture (DITA) 1.3 specification defines both a) a set of document types for authoring and organizing topic-oriented information; and b) a set of mechanisms for combining, extending, and constraining document types.
  • Ontology Matching • Semantic Social Networks and Peer-To-Peer Systems

    Ontology Matching • Semantic Social Networks and Peer-To-Peer Systems

    The web: from XML to OWL Rough Outline 1. Foundations of XML (Pierre Genevès & Nabil Layaïda) • Core XML • Programming with XML Development of the future web • Foundations of XML types (tree grammars, tree automata) • Tree logics (FO, MSO, µ-calculus) • Expressing information ! Languages • A taste of research: introduction to some grand challenges • Manipulating it ! Algorithms 2. Semantics of knowledge representation on the web (Jérôme Euzenat & • in the most correct, efficient and ! Logic Marie-Christine Rousset) meaningful way ! Semantics • Semantic web languages (URI, RDF, RDFS and OWL) • Querying RDF and RDFS (SPARQL) • Querying data though ontologies (DL-Lite) • Ontology matching • Semantic social networks and peer-to-peer systems 1 / 8 2 / 8 Foundations of XML Semantic web We will talk about languages, algorithms, and semantics for efficiently and meaningfully manipulating formalised knowledge. We will talk about languages, algorithms, and programming techniques for efficiently and safely manipulating XML data. You will learn about: You will learn about: • Expressing formalised knowledge on the semantic web (RDF) • Tree structured data (XML) ! Syntax and semantics ! Tree grammars & validation You will not learn about: • Expressing ontologies on the semantic • XML programming (XPath, XSLT...) You will not learn about: web (RDFS, OWL, DL-Lite) • Tagging pictures ! Queries & transformations ! Syntax and semantics • Hacking CGI scripts ! Reasoning • Sharing MP3 • Foundational theory & tools • HTML • Creating facebook ! Regular expressions
  • An Automated Approach to Grammar Recovery for a Dialect of the C++ Language

    An Automated Approach to Grammar Recovery for a Dialect of the C++ Language

    An Automated Approach to Grammar Recovery for a Dialect of the C++ Language Edward B. Duffy and Brian A. Malloy School of Computing Clemson University Clemson, SC 29634, USA feduffy,[email protected] Abstract plications developed in a new or existing language [12, 15]. Frequently, the only representation of a dialect is the gram- In this paper we present the design and implementa- mar contained in the source code of a compiler; however, a tion of a fully automated technique for reverse engineering compiler grammar is difficult to comprehend since parser or recovering a grammar from existing language artifacts. generation algorithms place restrictions on the form of the The technique that we describe uses only test cases and a compiler grammar [16, page 10]. parse tree, and we apply the technique to a dialect of the Another problem with language dialects is that there C++ language. However, given test cases and a parse tree has been little research, to date, addressing the problem for a language or a dialect of a language, our technique of reverse engineering a grammar or language specifica- can be used to recover a grammar for the language, in- tion for a language dialect from existing language arti- cluding languages such as Java, C, Python or Ruby. facts. Lammel¨ and Verhoef have developed a technique that uses a language reference manual and test cases to recover a grammar for a language or dialect [16]. How- 1. Introduction ever, their technique requires user intervention along most of the stages of recovery and some of the recovery process The role of programming languages in software devel- is manual.
  • XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département D©Informatique Et De Recherche Opérationnelle Université De Montréal

    XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département D©Informatique Et De Recherche Opérationnelle Université De Montréal

    XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/ XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 Abstract This tutorial gives a high-level overview of the main principles underlying some XML technologies: DTD, XML Schema, RELAX NG, Schematron, XPath, XSL stylesheets, Formatting Objects, DOM, SAX and StAX models of processing. They are presented from the point of view of the computer scientist, without the hype too often associated with them. We do not give a detailed description but we focus on the relations between the main ideas of XML and other computer language technologies. A single compact pretty-print example is used throughout the text to illustrate the processing of an XML structure with XML technologies or with Java programs. We also show how to create an XML document by programming in Java, in Ruby, in Python, in PHP, in E4X (Ecmascript for XML) and in Swift. The source code of the example XML ®les and the programs are available either at the companion web site of this document or by clicking on the ®le name within brackets at the start of the caption of each example.
  • Content Processing Framework Guide (PDF)

    Content Processing Framework Guide (PDF)

    MarkLogic Server Content Processing Framework Guide 2 MarkLogic 9 May, 2017 Last Revised: 9.0-7, September 2018 Copyright © 2019 MarkLogic Corporation. All rights reserved. MarkLogic Server Version MarkLogic 9—May, 2017 Page 2—Content Processing Framework Guide MarkLogic Server Table of Contents Table of Contents Content Processing Framework Guide 1.0 Overview of the Content Processing Framework ..........................................7 1.1 Making Content More Useful .................................................................................7 1.1.1 Getting Your Content Into XML Format ....................................................7 1.1.2 Striving For Clean, Well-Structured XML .................................................8 1.1.3 Enriching Content With Semantic Tagging, Metadata, etc. .......................8 1.2 Access Internal and External Web Services ...........................................................8 1.3 Components of the Content Processing Framework ...............................................9 1.3.1 Domains ......................................................................................................9 1.3.2 Pipelines ......................................................................................................9 1.3.3 XQuery Functions and Modules .................................................................9 1.3.4 Pre-Commit and Post-Commit Triggers ...................................................10 1.3.5 Creating Custom Applications With the Content Processing Framework 11 1.4
  • There's a Lot to Know About XML, and It S Constantly Evolving. but You Don't

    There's a Lot to Know About XML, and It S Constantly Evolving. but You Don't

    < Day Day Up > • Table of Contents • Index • Reviews • Reader Reviews • Errata • Academic XML in a Nutshell, 3rd Edition By Elliotte Rusty Harold, W. Scott Means Publisher: O'Reilly Pub Date: September 2004 ISBN: 0-596-00764-7 Pages: 712 There's a lot to know about XML, and it s constantly evolving. But you don't need to commit every syntax, API, or XSLT transformation to memory; you only need to know where to find it. And if it's a detail that has to do with XML or its companion standards, you'll find it--clear, concise, useful, and well-organized--in the updated third edition of XML in a Nutshell. < Day Day Up > < Day Day Up > • Table of Contents • Index • Reviews • Reader Reviews • Errata • Academic XML in a Nutshell, 3rd Edition By Elliotte Rusty Harold, W. Scott Means Publisher: O'Reilly Pub Date: September 2004 ISBN: 0-596-00764-7 Pages: 712 Copyright Preface What This Book Covers What's New in the Third Edition Organization of the Book Conventions Used in This Book Request for Comments Acknowledgments Part I: XML Concepts Chapter 1. Introducing XML Section 1.1. The Benefits of XML Section 1.2. What XML Is Not Section 1.3. Portable Data Section 1.4. How XML Works Section 1.5. The Evolution of XML Chapter 2. XML Fundamentals Section 2.1. XML Documents and XML Files Section 2.2. Elements, Tags, and Character Data Section 2.3. Attributes Section 2.4. XML Names Section 2.5. References Section 2.6. CDATA Sections Section 2.7.
  • File Format Guidelines for Management and Long-Term Retention of Electronic Records

    File Format Guidelines for Management and Long-Term Retention of Electronic Records

    FILE FORMAT GUIDELINES FOR MANAGEMENT AND LONG-TERM RETENTION OF ELECTRONIC RECORDS 9/10/2012 State Archives of North Carolina File Format Guidelines for Management and Long-Term Retention of Electronic records Table of Contents 1. GUIDELINES AND RECOMMENDATIONS .................................................................................. 3 2. DESCRIPTION OF FORMATS RECOMMENDED FOR LONG-TERM RETENTION ......................... 7 2.1 Word Processing Documents ...................................................................................................................... 7 2.1.1 PDF/A-1a (.pdf) (ISO 19005-1 compliant PDF/A) ........................................................................ 7 2.1.2 OpenDocument Text (.odt) ................................................................................................................... 3 2.1.3 Special Note on Google Docs™ .......................................................................................................... 4 2.2 Plain Text Documents ................................................................................................................................... 5 2.2.1 Plain Text (.txt) US-ASCII or UTF-8 encoding ................................................................................... 6 2.2.2 Comma-separated file (.csv) US-ASCII or UTF-8 encoding ........................................................... 7 2.2.3 Tab-delimited file (.txt) US-ASCII or UTF-8 encoding .................................................................... 8 2.3
  • Skyfire: Data-Driven Seed Generation for Fuzzing

    Skyfire: Data-Driven Seed Generation for Fuzzing

    Skyfire: Data-Driven Seed Generation for Fuzzing Junjie Wang, Bihuan Chen†, Lei Wei, and Yang Liu Nanyang Technological University, Singapore {wang1043, bhchen, l.wei, yangliu}@ntu.edu.sg †Corresponding Author Abstract—Programs that take highly-structured files as inputs Syntax Semantic normally process inputs in stages: syntax parsing, semantic check- Features Rules ing, and application execution. Deep bugs are often hidden in the <?xml version="1.0" application execution stage, and it is non-trivial to automatically encoding="utf- pass pass pass 8"?><xsl:stylesheet version="1.0" Syntax Semantic Application xmlns:xsl="http://www.w3 .org/1999/XSL/Transform" generate test inputs to trigger them. Mutation-based fuzzing gen- ><xsl:output xsl:use- √ attribute- Parsing Checking Execution erates test inputs by modifying well-formed seed inputs randomly sets=""/></xsl:stylesheet> Parsing Semantic or heuristically. Most inputs are rejected at the early syntax pars- Inputs Crashes ing stage. Differently, generation-based fuzzing generates inputs Errors Violations from a specification (e.g., grammar). They can quickly carry the ! ! X fuzzing beyond the syntax parsing stage. However, most inputs fail to pass the semantic checking (e.g., violating semantic rules), Fig. 1: Stages of Processing Highly-Structured Inputs which restricts their capability of discovering deep bugs. In this paper, we propose a novel data-driven seed generation approach, named Skyfire, which leverages the knowledge in the analysis [8, 9] that identifies those interesting bytes to mutate, vast amount of existing samples to generate well-distributed seed symbolic execution [10, 11, 12] that relies on constraint solving inputs for fuzzing programs that process highly-structured inputs.
  • Session 7 - Main Theme XML Information Rendering (Part I)

    Session 7 - Main Theme XML Information Rendering (Part I)

    XML for Java Developers G22.3033-002 Session 7 - Main Theme XML Information Rendering (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Summary of Previous Session Extensible Stylesheet Language Transformation (XSL-T) Extensible Stylesheet Language Formatting Object (XSL-FO) XML and Document/Content Management Introduction to XML Application Servers Working with XSLT-T and XSL-FO Processors Assignment 4a+4b (due in two week) 2 1 Summary of Previous Session Summary of Previous Session Document Object Model (DOM) Advanced XML Parser Technology JDOM: Java-Centric API for XML JAXP: Java API for XML Processing Parsers comparison Latest W3C APIs and Standards for Processing XML XML Infoset, DOM Level 3, Canonical XML XML Signatures, XBase, XInclude XML Schema Adjuncts Java-Based XML Data Processing Frameworks Assignment #3 3 XML-Based Rendering Development XML Software Development Methodology Language + Stepwise Process + Tools Rational Unified Process (RUP) vs. “XML Unified Process” XML Application Development Infrastructure Metadata Management (e.g., XMI) XSLT, XPath XSL-FO APIs (JAXP, JAXB, JDOM, SAX, DOM) XML Tools (e.g., XML Editors, Apache’s FOP, Antenna House’s XSL Formatter, HTML/CSS1/2/3, XHTML, XForms, WCAG XML App. Components Involved in the Rendering Phase: Application(s) of XML XML-based applications/services (markup language mediators) MOM, POP, Other Services (e.g., persistence) 4 Application Infrastructure Frameworks
  • SWAD-Europe Deliverable 5.1: Schema Technology Survey

    SWAD-Europe Deliverable 5.1: Schema Technology Survey

    Sat Jun 05 2004 23:47:40 Europe/London SWAD-Europe Deliverable 5.1: Schema Technology Survey Project name: Semantic Web Advanced Development for Europe (SWAD-Europe) Project Number: IST-2001-34732 Workpackage name: 5. Integration with XML Technology Workpackage description: ☞http://www.w3.org/2001/sw/Europe/plan/workpackages/live/esw-wp-5.html Deliverable title: SWAD-Europe: Schema Technology Survey URI: ☞http://www.w3.org/2001/sw/Europe/reports/xml_schema_tools_techniques_report Authors: Stephen Buswell, Dan Brickley, Brian Matthews Abstract: This report surveys the state of schema annotation and mapping technology. It takes a practical approach by targeting the work to the needs of developers, providing background to support our attempts to answer frequently asked questions on this subject. The report first reviews previous work on 'bridging languages', giving an overview of the major approaches and uses that to motivate further technical work to progress the state of the art in this area. Status: Snapshot release for discussion and editorial work. Further revisions are planned during WP4. Comments on this document are welcome and should be sent to the ☞[email protected] list. An archive of this list is available at ☞http://lists.w3.org/Archives/Public/public-esw/ This report is part of ☞SWAD-Europe ☞Work package 5: Integration with XML Technology and addresses the topic of Schema annotation, and the relationship(s) between RDF and XML technologies. The variety of so-called 'schema languages' for the Web has caused some confusion. This document attempts to place them in context, and explore the state of the art in tools for mapping data between the different approaches.