DOCSLIB.ORG

Moving Toward Xhtml 2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Moving Toward Xhtml 2 Copyright • Copyright © 2003 John Cowan MOVING TOWARD • Licensed under the GNU General Public License • ABSOLUTELY NO WARRANTIES; USE AT YOUR OWN RISK XHTML 2 • Black and white for readability • The Gentium font available at http://www.sil.org/~gaultney/gentium John Cowan Associated Press 1 2 Roadmap Roadmap • Introduction (10 slides) • The Common Attributes (19 slides) • Goals and Principles (8 slides) • XML Events (11 slides) • New and Nifty (8 slides) • XForms (19 slides) • What's History (7 slides) • To Be Continued... (1 slide) • The Elements (27 slides) 3 4 Versions of HTML • HTML 1.0 – simple hypertext INTRODUCTION • HTML 2.0 – images and forms • HTML 3.2 – the union of the browsers • HTML 4.01 – the kitchen sink • XHTML 1.0 – it's XML time • XHTML 1.1 – modularization • XHTML 2 – simple and powerful hypertext 5 6 What is XHTML 2? XHTML 2 Abstract • An evolving standard currently being XHTML 2 is a general purpose markup worked on by the HTML Working Group of language designed for representing the W3C. documents for a wide range of purposes • The first major change to the semantics of across the World Wide Web. To this end it HTML since HTML 4.0. does not attempt to be all things to all people, supplying every possible markup idiom, but to – Obsolete syntax has been discarded supply a generally useful set of elements. – Separation of content and presentation essentially complete – Genuinely new features being introduced 7 8 Why design XHTML 2? Why plan for XHTML 2? • More usable • Predicting the degree of market uptake not • More accessible to different kinds of users yet possible and display devices • Support for legacy HTML will probably be • Easier to write by hand or with tools provided forever for practical reasons • Less reliant on embedded scripting • Avoiding most deprecated and obsolete languages for commonly used functionality features is already possible • The planner's rule of thumb: “Plan or be planned for” 9 10 Making early adoption easy Who supports XHTML 2? • Much HTML is already generated using • Too soon for formal commitments XSLT from one of many XML formats • Server-side support is straightforward • XHTML 2 can be generated just as easily • Cross-platform open-source browsers will • Early-adopting clients can get a better almost certainly support XHTML 2 fairly browsing experience quickly and easily • The WG contains several major browser companies 11 12 Constructing document types Everything is subject to change • XHTML 2 has a fully modular definition • This presentation is based on the July 2006 • Defining subsets for use within other public working draft of XHTML 2 document types will be easy, for: • Disclaimer: not every slide is 100% updated – rich textual annotations to the very latest draft – embedded presentation-ready material • There are still open issues, which are rather poorly documented at present 13 14 Working Group(s) • XHTML 2 has been developed by the W3C's HTML WG GOALS AND PRINCIPLES • I am not on the WG, so I have limited inside information • XHTML 2 is being handed off to a new WG soon, according to the latest reports 15 16 Goals: ease of use Goals: universal access • Generic XML when possible • Better internationalization for the World • Less presentation, more structure Wide Web • Make the language easy to write • Device independence: – Author once, not once per device • Make the resulting documents easy to use – Render differently on different devices • Be as inclusive as possible (“design for our future selves”) 17 18 Goal: reduced use of scripting Breaking backward compatibility • Writing scripts is programming, not • Earlier versions of HTML were special- document authoring purpose languages • Only high-powered user agents (lots of • Backward compatibility required so that memory and CPU speed) can process scripts new documents would still be usable in • XHTML 2 tries to make declarative, not older browsers procedural, pages straightforward • Modern browsers can render arbitrary XML with stylesheets 19 20 Breaking backward compatibility Modular design • Much of XHTML 2 already works in existing • XHTML 2 is divided into modules which browsers together define the elements, attributes, • XML Events and XForms still require user and content models of the language agents that understand that functionality • Modules are meant to be reusable • Clever use of Javascript under the table can independently help here • If your XML design needs a bit of rich text, recycle some XHTML 2! 21 22 Namespaces Schema language independence • XHTML 2 introduces a new namespace • The working drafts define XHTML 2 syntax name: http://www.w3.org/2002/06/xhtml2/ normatively in RELAX NG (www.relaxng.org) . • Ruby, XForms, and XML Events have their • DTD and W3C XML Schema normative own namespace names definitions will be added in later drafts 23 24 Ubiquitous hyperlinks • Any element can be the target of a NEW AND NIFTY hyperlink (through the id attribute) • Any element can be the source of a hyperlink (through the href attribute) • The a element is kept for backward compatibility 25 26 Hyperlinking example Generalized transclusion • Any element can have a src attribute <p href=”#security”>Security providing external content to be rendered Considerations</p> instead of the element ... • This means rich text can be embedded as <p id=”security”>This system well as images and objects is just inherently insecure. • The img element is likewise kept for Deal with it.</p> backward compatibility 27 28 Transclusion example How to do images <img src=”...” alt=”text”> becomes <p src=”http://www.example.com/intro”> Hmm, transclusion isn't working. <span src=”...”>text</span> Sorry. <a or href=”http://www.example.com/intro”> Click</a> here and then use the Back <object data=”...”>text</object> button.</p> 29 30 External modules XForms • Ruby provides support for Japanese-style • Widgets can appear anywhere in a XHTML annotation document • XML Events is a greatly extended events • Arbitrary XML is embedded in the module based on DOM Level 2 Events document as a template • XForms is a completely new forms language • Widgets are bound using XPaths to • Other languages (MathML, SVG) aren't part appropriate parts of the template of XHTML 2 but can be used with it • The filled-out template is submitted 31 32 Streamlined language • HTML 4.0: 91 elements, 188 attributes (counting shared attributes only once) WHAT'S HISTORY • XHTML 2: 59 elements (plus 1 for XEvents and 29 for XForms), 59 attributes • Almost any attribute can be attached to almost any element • XHTML 2 is the true (refactored) second version of HTML 33 34 Presentational markup is It's XML, you know dead, dead, dead • Make sure all start-tags have end-tags and • Originally, HTML was designed to represent empty-tags end in /> the structure of a document, not its • Lower-case elements and attributes presentation • Quote attribute values • Presentation-oriented elements were later added to the language by browser • Wrap script and style content in CDATA manufacturers sections • XHTML 2 takes HTML back to its roots • HTML Tidy (tidy.sf.net) is your friend 35 36 Presentational markup is Presentational markup is dead, dead, dead dead, dead, dead • All presentational elements and attributes • Presentation handled solely by stylesheets are gone • Standardizing on stylesheets means • Even old warhorses like b, i, and br bite enhanced flexibility of presentation the dust • CSS can do more than presentational HTML • HTML Tidy is still your friend ever did • XSLT is also your friend • A standard stylesheet will be provided to give the default (traditional) presentation 37 38 The img and applet elements No more frames • Superseded by the new and generalized • Everything to do with frames is gone object element, which is now used to • The target attribute of hyperlinks embed any non-XHTML content remains, but its use is not defined • XSLT is your friend once again 39 40 New forms and event sublanguages • The new XForms language completely supersedes HTML Forms THE ELEMENTS • It's still possible for forms to return attribute-value pairs, but full XML documents are the recommended method • Event handling now uses XML Events 41 42 The Document Module The Structural Module • Elements: html , head , title , body • Elements: p, div , separator , address , • Attributes specific to the html element: blockquote , pre , blockcode , section , h, h1 -h6 – version replaces DOCTYPE declaration as an effective version signature • blockcode is a hybrid of blockquote – xsi:schemaLocation points to W3C and pre , intended to set off code XML Schemas for namespaces • separator replaces hr • p can now contain lists and tables, but not nested paragraphs 43 44 The section and h elements The Inline Text Module • section elements • Elements: abbr , cite , code , dfn , em , – contain major divisions of text kbd , l, q, samp , span , strong , sub , – can be nested to convey subdivisions, sub- sup , var subdivisions, etc. • No presentation elements: not even b and i • The h element works like h1 within a main survive document, like h2 within a top-level • q is for quotations, but no longer tries to section, like h3 within a sub-section, etc. supply quotation marks automatically (the • h1 -h6 are no longer necessary rules depend on language and country) 45 46 What are those elements for, The l element anyhow? • Container for a single line (of verse, • abbr : an abbreviation ( full attribute is an computer code, etc.) IDREF to the full name) • Replaces HTML's br • cite : a citation or source
Load more

Recommended publications
  • OMA Specification
    Scalable Vector Graphics (SVG) for the Mobile Domain Candidate Version 1.0 – 24 Oct 2008 Open Mobile Alliance OMA-TS-SVG_Mobile-V1_0-20081024-C 2008 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. [OMA-Template-Spec-20080101-I] OMA-TS-SVG_Mobile-V1_0-20081024-C Page 2 (30) Use of this document is subject to all of the terms and conditions of the Use Agreement located at http://www.openmobilealliance.org/UseAgreement.html. Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance™ specification, and is subject to revision or removal without notice. You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document.
    [Show full text]
  • Efficient XML Processing in Browsers
    Efficient XML Processing in Browsers R. Alexander Milowski ILCC, School of Informatics, University of Edinburgh [email protected] Motivation Partially, in response to the anti-XML crowd's complaints about XML in browser applications: XML slow, inefficient way to deliver data, JSON is simpler and more directly usable, and several other red herrings. Mostly because I want it! ...pretty shiny XML objects... The reality: XMLHttpRequest is insufficient for both XML and JSON delivery. Why and what do you do about processing large amounts of XML data efficiently in browsers? Inefficiencies with XMLHttpRequest Three general deficiencies: 1. If the response is not XML and not characters, there is little support for handling the entity body (e.g. images). 2. If the response is not XML but is characters, treating it as XML or as a sequence of characters may be wasteful. 3. If the response is XML, the "whole document" intermediary DOM may be wasteful. This talk is about concerned with #3. Strategy We want flexibility and choice in our processing model: whole document, subsetting, multiple DOMs, view porting, filtering, or just a stream of events. We'll replace XMLHttpRequest and: Keep the request formulation, Remove the "whole document" treatment of the response, Add event-oriented processing of the XML. The XMLReader Interface Shares a lot in common with XMLHttpRequest for making the request: send, open, overrideMimeType, setRequestHeader, etc. request model is the same, added a parse(in DOMString xml) method for completeness, added an onxml event listener attribute for receiving XML, added an "xml" event type for addEventListener() XML Events Events for: start/end document, start/end element, characters, processing instructions, comments Events are flattened - one interface for all of them.
    [Show full text]
  • 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.
    [Show full text]
  • SALT: an XML Application for Web-Based Multimodal Dialog Management
    SALT: An XML Application for Web-based Multimodal Dialog Management Kuansan Wang Speech Technology Group, Microsoft Research One Microsoft Way, Microsoft Corporation Redmond, WA, 98006, USA http://research.microsoft.com/stg devices. GUI is an immensely successful concept, Abstract notably demonstrated by the World Wide Web. Although the relevant technologies for the This paper describes the Speech Internet had long existed, it was not until the Application Language Tags, or SALT, an adoption of GUI for the Web did we witness a XML based spoken dialog standard for surge on its usage and rapid improvements in multimodal or speech-only applications. A Web applications. key premise in SALT design is that speech-enabled user interface shares a lot GUI applications have to address the issues of the design principles and computational commonly encountered in a goal-oriented dialog requirements with the graphical user system. In other words, GUI applications can be interface (GUI). As a result, it is logical to viewed as conducting a dialog with its user in an introduce into speech the object-oriented, iconic language. For example, it is very common event-driven model that is known to be for an application and its human user to undergo flexible and powerful enough in meeting many exchanges before a task is completed. The the requirements for realizing application therefore must manage the interaction sophisticated GUIs. By reusing this rich history in order to properly infer user’s intention. infrastructure, dialog designers are The interaction style is mostly system initiative relieved from having to develop the because the user often has to follow the underlying computing infrastructure and prescribed interaction flow where allowable can focus more on the core user interface branches are visualized in graphical icons.
    [Show full text]
  • Developing XML Applications for Oracle Weblogic Server 12C (12.2.1.2.0) E78038-02
    Oracle® Fusion Middleware Developing XML Applications for Oracle WebLogic Server 12c (12.2.1.2.0) E78038-02 December 2016 This document is a resource for software developers who design and develop applications that include XML processing. Oracle Fusion Middleware Developing XML Applications for Oracle WebLogic Server, 12c (12.2.1.2.0) E78038-02 Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Scalable Vector Graphics (SVG) 1.2
    Scalable Vector Graphics (SVG) 1.2 Scalable Vector Graphics (SVG) 1.2 W3C Working Draft 27 October 2004 This version: http://www.w3.org/TR/2004/WD-SVG12-20041027/ Previous version: http://www.w3.org/TR/2004/WD-SVG12-20040510/ Latest version of SVG 1.2: http://www.w3.org/TR/SVG12/ Latest SVG Recommendation: http://www.w3.org/TR/SVG/ Editor: Dean Jackson, W3C, <[email protected]> Authors: See Author List Copyright ©2004 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract SVG is a modularized XML language for describing two-dimensional graphics with animation and interactivity, and a set of APIs upon which to build graphics- based applications. This document specifies version 1.2 of Scalable Vector Graphics (SVG). Status of this Document http://www.w3.org/TR/SVG12/ (1 of 10)30-Oct-2004 04:30:53 Scalable Vector Graphics (SVG) 1.2 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/. This is a W3C Last Call Working Draft of the Scalable Vector Graphics (SVG) 1.2 specification. The SVG Working Group plans to submit this specification for consideration as a W3C Candidate Recommendation after examining feedback to this draft. Comments for this specification should have a subject starting with the prefix 'SVG 1.2 Comment:'. Please send them to [email protected], the public email list for issues related to vector graphics on the Web.
    [Show full text]
  • XML Application Components (Xacs)
    XML Application Components (XACs) Rafah A. Hosn IBM Research May 11th, 2007 TRACK Outline Backplane and Web 2.0 Web 2.0 Widgets & Composite Apps XACs, Component Model for Widget Composition Demo & Code Walkthrough Agenda Backplane and Web 2.0 Web 2.0 Widgets & Composite Apps XACs, Standard Composition Model Demo & Code Walkthrough Backplane & Web 2.0 Web 2.0 No Longer A Buzzword ?! Main themes Data-centric Collaborative Simple to author, simple to use Remixable How can the Backplane help? Standardize the programming model Easily snap various namespaces together Events Data model lifecycle Choreography Component Composition model Rich Web Application Backplane Interaction Namespaces and Frameworks XHTML SVG XForms VoiceXML SMIL Composite Apps Rich Web Application Backplane Compound Model-view Submission object Data Choreography Component Model Document binding (XMLHTTP++) Model (SCXML) and Composition Framework and events and behavior Platform technologies DOM Parser XPath, XSLT DOM Events JS Security Agenda Backplane and Web 2.0 Web 2.0 Widgets & Composite Apps XACs, Standard Composition Model Demo & Code Walkthrough Web 2.0 Widgets & Composite Apps Web 2.0 Widgets today Lots of various platforms & widget component models Google, Yahoo, Adobe, Clearspring, Netvibes, Microsoft… Composing widgets Different per platform/widget provider No standards to date Interoperability is not seamless (if at all possible) Mashing up widgets from different platforms is difficult Web 2.0 value-add proposition is weakened
    [Show full text]
  • Xforms --- Toward Light-Weight Web Applications
    Web Applications In XML XForms —Online Forms To Web Applications T. V. Raman IBM Research Web Applications In XML – p. 1 Outline Online forms to Web Applications Anatomy Of A Web Application Discovering, codifying Web patterns XForms and Web Applications Re-democratizing the Web Empowering authors, not browser vendors Web Applications In XML – p. 2 Online Forms To Web Applications Web Applications In XML – p. 3 CGI And HTML Forms Enabled interactivity on the Web. HTML forms collected data values, CGI scripts processed collected values, And served up the next step in the interaction. Server-side has stayed the same since 1993. Web Applications In XML – p. 4 Client-side Of Web Applications Evolved to enable richer client-side interaction. Scripting implements client-side behaviors. DOM enables manipulation of the HTML UI. Enables separation of data from presentation. Toward discovery of useful design patterns. Web Applications In XML – p. 5 Anatomy Of A Web Application Web Applications In XML – p. 6 Anatomy Of Web Applications Interaction widgets that collect data, Event handlers that implement behavior, Memory model synchronized with server, Server logic to knit together the application. Deploy User Interaction To A Universal Client Web Applications In XML – p. 7 Discovering Web Design Patterns Web Applications In XML – p. 8 Web Interaction Idioms Data Binding Data in ECMAScript objects, Data in XML, Bound to HTML view via DOM. Data Sources Data from multiple sources, Submit to multiple destinations. Web Applications In XML – p. 9 Web Design Idioms Dynamic Grow or shrink the interface. Customize presentation on the fly. Interactively validate user input.
    [Show full text]
  • Tivoli Netcool Support's Guide to the Message Bus Integration by Jim Hutchinson Document Release: 4.3 Support's Guide to the Message Bus Integration
    Tivoli Netcool Support's Guide to the Message Bus Integration by Jim Hutchinson Document release: 4.3 Support's Guide to the Message Bus Integration Table of Contents 1Introduction...................................................................................................................................4 1.1Overview......................................................................................................................................4 1.2Capabilities..................................................................................................................................5 1.3Probe design................................................................................................................................6 1.4Gateway design...........................................................................................................................7 2JMS Transport with Apache MQ.................................................................................................8 2.1Overview......................................................................................................................................8 2.2Requirements..............................................................................................................................8 2.3Apache ActiveMQ server.............................................................................................................9 2.3.1Downloading and installing.......................................................................................................9
    [Show full text]
  • Functional Extensions for Animation And
    Presentation Dynamism in XML Functional Programming meets SMIL Animation Patrick Schmitz Simon Thompson Peter King Ludicrum Enterprises Computing Laboratory Department of Computer Science San Francisco, CA, USA University of Kent University of Manitoba Winnipeg, MB, Canada [email protected] Canterbury, Kent, UK +44 1227 823820 +1 204 474 9935 [email protected] [email protected] ABSTRACT structure and semantics of declarative languages, and often cannot The move towards a semantic web will produce an increasing easily integrate imperative content extensions. Similarly, the use number of presentations whose creation is based upon semantic of script or code is problematic in data-driven content models queries. Intelligent presentation generation engines have already based upon XML and associated tools. begun to appear, as have models and platforms for adaptive In this paper we will motivate and describe a set of XML [10] presentations. However, in many cases these models are language extensions that will enhance these language standards. constrained by the lack of expressiveness in current generation The specific extensions are inspired by constructions from presentation and animation languages. Moreover, authors of functional programming languages, and include: dynamic, adaptive web content must often use considerable • attribute values defined as dynamically evaluated amounts of script or code, thus breaking the declarative expressions, description possible in the original presentation language. Furthermore, the scripting/coding approach does not lend itself to • custom (or ‘author defined’) events based on predicate authoring by non-programmers. In this paper we describe a set of expressions, XML language extensions that bring tools from the functional • parameterized templates for document content.
    [Show full text]
  • Oracle Fusion Middleware Programming XML for Oracle Weblogic Server, 11G Release 1 (10.3.3) E13724-02
    Oracle® Fusion Middleware Programming XML for Oracle WebLogic Server 11g Release 1 (10.3.3) E13724-02 April 2010 This document is a resource for software developers who design and develop applications that include XML processing. Oracle Fusion Middleware Programming XML for Oracle WebLogic Server, 11g Release 1 (10.3.3) E13724-02 Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • PDF Version, ZIP Archive, and Gzip’D TAR Archive
    XML Events 2 XML Events 2 XML Events 2 An Events Syntax for XML W3C Working Group Note 16 December 2010 This version: http://www.w3.org/TR/2010/NOTE-xml-events2-20101216 Latest version: http://www.w3.org/TR/xml-events2 Previous version: http://www.w3.org/TR/2007/WD-xml-events-20070216 Diff from previous version: xml-events-diff.html Previous recommendation: http://www.w3.org/TR/2003/REC-xml-events-20031014 Diff from previous recommendation: xml-events-rec-diff.html Editors: Shane McCarron, Applied Testing and Technology, Inc. Mark Birbeck, Sidewinder Labs Roland Merrick, IBM Version 1 Editors: Shane McCarron, Applied Testing and Technology, Inc. Steven Pemberton, CWI/W3C® T. V. Raman, IBM Corporation 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 © 2003-2010 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. - 1 - Contents XML Events 2 Abstract This specification defines three modules: XML Events to define events and their characteristics; XML Handlers to define mappings between events and actions; and XML Scripting to assist in defining functions to support the handlers. These modules work together to provide XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 3 event interfaces [DOM3EVENTS [p.41] ]. The result is to provide an interoperable way of associating behaviors with document-level markup.
    [Show full text]