DOCSLIB.ORG

Engageone Server V4.4.9 Programmer Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Engageone Server V4.4.9 Programmer Guide Customer Engagement EngageOne® Compose ® EngageOne Server Programmer's Reference Guide Version 4.4 Service Pack 9 Table of Contents Feature support for System Data Integration 69 Integration option 1 – XML data source 71 1 - Overview Integration option 2 – callback interface 75 Overview 5 Template designer 5 5 - Additional features in SOAP EngageOne Server components 10 EngageOne administration 13 Trusted Connection 87 EngageOne Interactive 14 Template search 87 Interactive document process flow 14 Write delivery information 96 Managing the work queue 99 Updating work items 102 2 - Integrating with EngageOne Reassigning a work item 106 SOAP Deleting a work item 108 OnDemand 18 6 - EngageOne notifications Interactive 18 Data push processing in EngageOne Overview 110 Interactive 18 Notification components diagram 111 Interactive Document Delivery 32 Topics and queues 113 Sample application 33 Configuration settings 114 OnDemand Document Delivery 36 Messages 118 Communication messages 119 3 - XForms Batch messages 121 Workflow messages 122 Consuming notification messages 123 About XForms 39 Using other JMS implementations 126 XForms processors 41 Sample message consumers 128 XForm/SDI Flow 42 XForms standard files 43 Data definition type and attributes 62 7 - The comparison adapter plug-in 4 - System Data Integration The custom plug-in implementation 130 SDI General Configuration 66 Example implementations 131 Using an XML file as a data source 67 Plug-in Installation and configuration 135 Using the Java callback interface 68 8 - Appendix A - Editor methods LoadContents 137 SaveContents 137 SpellCheck 138 IsComplete 138 IsModified 139 GetVersion 139 9 - Appendix B - SOAP API Identifiers 141 Search filter 142 Promotion service 143 Folder service 164 Data push service 168 Delivery management service 170 Dictionary service 178 Domain service 180 Editor service 182 Keymap service 185 Metadata service 193 Request status update service 196 Security service 198 Template service 204 Workitem service 227 Attachment service 256 Workflow service 268 Delivery service 280 10 - Upgrading 3.X to 4.X SOAP services Licensing changes 301 Security changes 302 WorkItem approval process not supported 304 DataPushService.mapData not supported 304 EngageOne® Compose EngageOne® Server Programmer's Reference Guide 3 1 - Overview EngageOne is an interactive document production system, enabling the creation and delivery of high volume, on demand and interactive customer correspondence. In this section Overview 5 Template designer 5 EngageOne Server components 10 EngageOne administration 13 EngageOne Interactive 14 Interactive document process flow 14 Overview Overview Document templates and optional content objects are defined by the template designer in a core application called Designer, and managed in the content repository. These programs are made available to front-office users through a Web-based interface. This interface allows users to create and modify a document in a controlled manner, and distribute documents through various delivery channels as required. The EngageOne Interactive Web application uses the services provided by the EngageOne Web services interface to access the server functions of EngageOne. Template designer Document templates are created by a template designer, a user who defines the document and its interactions in Designer. A template consists of a traditional publication design, along with interactive data definitions which describe the front office user interactions required to complete a document from that template. This involves designing the overall template and defining: • The data prompts included in the document using the Interactive Editor • Paragraph and content selection, using optional content selections (Active Content) • Free-form text to override content protection using editable paragraphs For more information about these functions, see the Designer User’s Guide. The template designer allows the user to edit or enter free text as required in an EngageOne document design, by selecting a section of text in a paragraph object and defining the text as editable. Any text marked as editable can be changed by the user. Text that is not marked as editable will be protected. In addition to the basic template, the template designer can create optional content. Property values are defined, enabling them to be conditionally placed in an Active Content Group. When Active Content is marked as interactive, the user is dynamically presented with content choices to help them complete their document. Once the EngageOne template has been designed and data fields defined, the template is named and published for EngageOne. The XForm files that define the document's data model are included in the template’s Zip file. The process of importing these files into the EngageOne content repository using the EngageOne Administration client, is called Template deployment. EngageOne® Compose EngageOne® Server Programmer's Reference Guide 5 Overview The interactive data model is defined and exposed using the W3C XForm standard. The XForm can be used by the system integrator to push system data into the interactive document. Content repository The content repository provides file storage and version control for EngageOne. It houses the templates used to create documents, supporting files needed for document composition, and the document instances waiting for delivery. EngageOne® Compose EngageOne® Server Programmer's Reference Guide 6 Overview About the template The template manifest (template_master.xml) describes template attributes and contents. The template manifest is made up of the following: Subfiles The Subfiles section contains a list of files in the template Zip file, and specifies each file type: Template composition HIP HIP files contain design, layout, logic and other resources required for generating publications. These files are used by Generate. There are two types of HIP file: publications, and independently publishable active content. PUB Publication files contain design, layout and logic. These files are used by the Interactive Editor. There are two types of PUB file: template publications, and independently publishable active content. XFRM XForms define electronic forms for collecting general purpose information. INST Instance data file. Initially this file contains default field values. All values entered by the user will be saved in this file. Free form text is stored in the HIP and PUB files, not the instance file. SCHEMA The instance file schema contains standard schema nodes and attributes. The schema ensures data returned in the instance file is well-formed, the right type, and meets defined field criteria. IMG Image file required by the editor for display in the template. DATAMODEL XML representation of the Designer Publication “Sample Data”, whether the original data is keyed data (for example, single value decomposition), delimited (for example, comma separated values), or on-demand XML. The DATAMODEL file type appears only for non-interactive templates. EngageOne® Compose EngageOne® Server Programmer's Reference Guide 7 Overview Template composition PREVIEW PDF file appears for both interactive and non-interactive templates, where Designer Publish for EngageOne has successfully generated a PDF “preview” example of the Designer Publication. The PREVIEW file is generated using “emergency replacement” data, where the Designer Publication data is incomplete, and may not reflect the completed document. PREVIEW file is available for the Interactive user to view a “Preview” of the Template Document at the start of the “Edit Communication” process. PROMPTLOGIC Files containing information used to prompt for, and validate, interactive template data when the ActiveX editor is not used. THUMBNAIL "Scaled" image representation of the first document. Intended as a rough guide to the layout and content of the first document. EngageOne® Compose EngageOne® Server Programmer's Reference Guide 8 Overview Resources The Resources section lists the dependencies of the template. These can be of the following types: ACTCONT Active content IMAGE Image used in the template FONT Font used in the template The following fragment demonstrates the structure of the template manifest: <?xml version="1.0" encoding="utf-8"?> <!--XML meta file for EngageOne Template--> <document ocmmetafile-vers="ocm-metafile1.0" ocm-vers="OCM Template V1.0"> <OcmMetadata> <documentClass> <metadata-field fieldName="Publish Date" fieldValue="05-May-2009" defaultValue="" fieldType="text" /> <metadata-field fieldName="Published By" fieldValue="Administrator" defaultValue="" fieldType="text" /> <metadata-field fieldName="Design Publication Name" fieldValue="Basic" defaultValue="" fieldType="text" /> </documentClass> <Subfiles> <File type="HIP">template.hip</File> <File type="PUB">template.pubx</File> <File type="XFRM">d79f96b60b2a48ee9f59c8bed5655f86.xform</File> <File type="INST">d79f96b60b2a48ee9f59c8bed5655f86.xml</File> <File type="SCHEMA">d79f96b60b2a48ee9f59c8bed5655f86.xsd</File> <File type="IMG">c52767b2d1824366b522589d550cb297.png</File> </Subfiles> <Resources> <Res type="ACTCONT" name="Basic" guid="e06d8fc2009642ddb2740495af6bf785" /> <Res type="FONT" name="Arial 11pt" guid="24e474cc2baa434cb7239457b6b90443" /> <Res type="IMAGE" name="logo.bmp" guid="c52767b2d1824366b522589d550cb297" /> </Resources> <Inputs> <HIP path="" /> <ActiveContent path="" /> </Inputs> </OcmMetadata> </document> EngageOne® Compose EngageOne® Server Programmer's Reference Guide
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]
  • 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
    [Show full text]