The Extensible Markup Language (XML) is an open, general-purpose specification for creating markup languages. Its primary purpose is to help information systems share structured data, particularly via the Internet, and it is used both to encode documents and to serialize data. It is used in a wide variety of technical communication document formats, including Microsoft Word, OpenOffice, XHTML, DITA, DocBook, and RSS, among others.
#33900
Functional XML: A Preliminary Sketch
Existing XML processing models are pipelines, controlled by pipeline descriptions which resemble shell scripts. Functional XML allows XML documents to specify their own processing explicitly, without losing the generality of the pipeline script approach.
Thompson, Henry S. IDEAlliance (2005). Articles>Information Design>XML
#33901
Service Oriented Architectures (SOA) in the Real World
Management is an essential for any organization planning to make production use of SOA. Even at the outset of a Web services project, success hinges on defining, tracking and controlling appropriate service levels. When implementing Web services, organizations need to review and analyze quality-of-service (QoS) metrics in order to plan for growth, minimize risk and justify additional investments. Once in production, loosely coupled systems require heightened security measures and a means for handling unexpected business conditions. In this session, the author will review how two leading financial services organizations built and deployed production-ready SOA systems, and, as a result, significantly reduced development cycles and total cost of ownership. Ed will also discuss the benefits these companies have achieved from implementing their SOA systems, the challenges they overcame and how they plan to extend their SOA systems to realize greater business benefit in the future.
Horst, Ed and Christopher Sirna. IDEAlliance (2005). Articles>Information Design>XML
#33902
XML schema analysis aims to extract quantitative and qualitative information from actual XML schemas. To this end, XML schemas are measured through systematic algorithms, on the basis of the intrinsic feature model of the XSD language. XML schema analysis is a derivative of software analysis (program analysis) and of software code metrics, in particular. The present article introduces essential concepts of XML schema analysis and applies them to the important problem of understanding XML schema usage in practice. Analyses for feature counts, idiosyncrasy counts, size metrics, complexity metrics, and XML schema styles are executed on a large corpus of real-world XML schemas.
Lammel, Ralf, Stan Kitsis and Dave Remy. IDEAlliance (2005). Articles>Information Design>Standards>XML
#33903
The Future of XML Information Management
Discusses how XML is changing the definition of 'Information Management' and the challenges associated with this change. XML provides endless opportunities when it comes to solving complex data issues companies face today from data integration to implementation of Service Oriented Architectures(SOA). Companies that choose to exploit the advantages of XML will undoubtly gain an edge over their competitors but will also be required to solve the challenges around how to best manage and service XML data without compromising data security and integrity.
Picciano, Robert. IDEAlliance (2005). Articles>Information Design>XML>Planning
#33904
The Session Concept and Web Services 
This paper describes the session concept as it relates to middleware systems in general and Web services in particular. Common applications of the session concept are found in distributed object systems, the Web, and messaging middleware systems. The purpose of a session is to allow multiple individual Web Services to enter a relationship by sharing certain common attributes as an externally modeled entity. For example, multiple Web Services executing within the scope of a single authorized/secure session. In the context of Web services, explicit building blocks for session-oriented protocols and services have been proposed in two specifications, WS-Addressing and WS-Context. The distinguishing characteristic of these two proposals is the degree of coupling they introduce between session participants. In this paper we shall compare and contrast the underlying models these specifications present, as they relate to the session concept in Web services. The aim is to illustrate the advantages and disadvantages of both approaches and summarize best-practices and techniques for supporting a scalable Web services architecture. Note, although this paper is not purely research oriented, it does make an important contribution in the area of software practices and experiences for current and future researchers. The authors believe that it is important to ensure that the Web services architecture scales as well as the World Wide Web and as we shall see, the session concept and how it is provided play an integral role in that arena.
Hildebrand, Hal, Anish Karmarkar, Mark Little and Greg Pavlik. IDEAlliance (2005). Articles>Web Design>Information Design>XML
#33905
XML Authoring for Those Who Don't Like Markup
Advances in word processing technology now enable people to author simple documents in an interface they are familiar with. They no longer need to know a lot about markup, the schema in use, or be distracted by other concerns than writing what they want to write. This simpler interface, built upon a Microsoft "Smart Doc" solution provides support for authors who are focused on the content they are writing rather than the markup that describes it. At the same time, the author is producing valid XML that can be routed for review and approval, used for multi-channel delivery, or reused by other authors in the enterprise. Several scenarios of how such an authoring/management system could be used to solve business challenges are described.
Parsons, Jon. IDEAlliance (2005). Articles>Information Design>Software>XML
#33906
Serving XML is a markup language for expressing XML pipelines, and an extendible Java framework for defining the elements of the language. It provides a markup language for expressing flat-XML, XML-flat, flat-flat, and XML-XML transformations in pipelines. This article provides a brief introduction to the vocabulary of this language, and some examples of its flat-XML capabilities.
Parker, Daniel. IDEAlliance (2005). Articles>Information Design>XML>Workflow
#33907
Extending XML in the Enterprise
This presentation explores how recent advances in user interfaces have blurred the once clear distinction between structured and unstructured data. It examines how these tools can be used to empower a new class of user to participate in an XML workflow and a managed content environment.
Parsons, Jon. IDEAlliance (2005). Articles>Content Management>XML>Workflow
#33908
Microsoft Office Open XML Formats
This session will provide a technical description of the new Microsoft Office Open XML formats that will become the default XML based formats of the coming version of Microsoft Office (Office 12). The Microsoft Office XML formats provides a great Open and standard-based XML format for Office Documents that enables new XML document scenarios that were not possible before.
Paoli, Jean and Brian Jones. IDEAlliance (2005). Articles>Word Processing>Information Design>XML
#33974
Peaceful Coexistence: The SGML/XML Transition at Cessna Aircraft
The transition in a markup-based publishing environment from SGML- to XML-based tools and procedures can sometimes be complex. This session details Cessna Aircraft Company's implementation as it moves from an SGML environment to an XML enviroment.
Hahn, Michael. XML 2006 (2006). Articles>Information Design>XML>Case Studies
#33975
Building Dynamic Applications With Mozilla, REX and XQuery.
The Mozilla platform offers a rich support of XML techniques, from low level ones (XPath, RDF, DOM, e4x) to rendering dialects like XHTML, SVG, XUL and XForms, thus making this platform a natural choice for the XML inclined. It is becoming a platform of choice when developing rich connected applications. When building dynamic applications, the developer is often facing a common set of programming patterns : gathering data from various remote and local sources, storing data with an optional transformation phase, and updating parts of the GUI to reflect the modifications in the data store. With today's ubiquitous use of XML as a data exchange syntax, a major part of these tasks can be achieved with XML based solutions. In this article we will present an XML centric solution that aims at minimizing the impedance mismatch between different data models that plagues classical architectures involving for instance XML/object/relationnal translation. It combines some of Mozilla's existing capabilities with REX (Remote Events for XML) and a native XML database with XQuery support. REX provides means to update the XUL based GUI and the database, while the XML database is used as a versatile storage engine.
Desré, Fabrice. XML 2006 (2006). Articles>Web Design>Information Design>XML
#33976
XQueryP: An XML Application Development Language
XQuery is a language that operates on XML in its native data model, using the type system of XML Schema. By the time of the XML 2006 conference, XQuery Version 1.0 will probably be adopted as a W3C Recommendation. Like SQL, XQuery is declarative and functional, which makes it well-suited for automatic optimization. XQuery Version 1.0 is designed for querying and transforming XML data, and W3C has published a working draft of an XQuery extension for updating XML data. With an additional small extension, XQuery could be turned into a native application development language for XML, eliminating the impedance mismatch problem. An earlier paper briefly outlined such an extension, called XQueryP. This paper expands on the XQueryP proposal, adding more details, additional features such as error handling, and some use cases that illustrate the use of the extended language in various different environments.
Kossmann, Donald. XML 2006 (2006). Articles>Information Design>XSL>XML
#33977
A Study of the Adoption and Usage of XML Schema - Its Design and Results
There is an obvious need to understand the current adoption and the current usage of XML Schema by the IT industry. That is, XML standardization bodies, XML tool providers, and IT decision makers need to know about the current position of XML Schema on the 'adoption curve'; they would like to know who is using XML Schema, what it is used for, and how users reflect on their usage. All sorts of more detailed questions arise: Is XML Schema usage observably increasing? Who is authoring schemas? (Developers? DBA's? Analysts? Who else?) Who is consuming schemas? What tools are used to author and consume schemas? What other meta-data languages are used in the same corporation? The study at hand covered these and some more questions. The goal was to gather broad information on XML Schema adoption and usage, leaving room for studies that dive into more detailed subtopics. There were 2,000 solicited participants of the study with 59 completed responses. The presentation (paper) does not just present the results of the study, but also motivates the study, describes its design, and draws some conclusions. This study has been carried out in collaboration with the Stephen M. Ross School of Business at the University of Michigan.
Kitsis, Stan. XML 2006 (2006). Articles>Information Design>XML
#33978
XML Project Management Best Practices
Three panellists talk about the challenges of managing an XML publishing and documentation project. After brief introductory remarks from each speaker, there will be a general discussion with the audience about the challenges of XML project management in the publishing world.
Hamilton, Kate, Sarah S. O'Keefe and Mike Sherlock. XML 2006 (2006). Articles>Project Management>Information Design>XML
#33980
Daddy? Where Do Schemas Come From? Some Facts of Life for Schema Users
The rules for finding schema components when validating a document using W3C's XML Schema 1.0 are widely misunderstood. This presentation will the rules for constructing a schema and describe the reasoning behind the design.
Sperberg-McQueen, C.M. XML 2006 (2006). Articles>Information Design>XML>Standards
#33981
The OpenDocument Format ("ODF") shows promise for bringing the eXtensible Markup Language (XML) to the common desktop PC of the future as the native file format for office documents in the next-generation office suites including OpenOffice, StarOffice, KOffice, Workplace, Writely and others. An ODF Plugin for MS Office -- currently under development by the OpenDocument Foundation -- can deliver this promise to the 450 million legacy Windows desktop PCs already in place. Sam Hiser, an officer of the OpenDocument Foundation, will discuss the origins and design objectives of the Foundation's ODF Plugin. He will also discuss the strategic goals of the Foundation's ODF Plugin while showing how the Plugin effort is already influencing the development of the ODF standard itself at OASIS. An audience of general business people and software developers will leave Hiser's presentation with a clear understanding of the ODF Plugin, its context of relevance and development, and how it can alter the landscape for XML.
Hiser, Sam. XML 2006 (2006). Articles>Word Processing>XML>Microsoft Word
#33982
The Essence of Declarative, XML-based Web Applications: XForms and XSLT
In this session, the author discusses best practices, common patterns and pitfalls in using XSLT as a host language for generating web-based user interfaces expressed in XForms.
Thomas-Ogbuji, Chimezie. XML 2006 (2006). Articles>Web Design>XML>XForms
#33983
Language Support for Web Service Development
We will demonstrate how enhancements to the XJ language (http://alphaworks.ibm.com/tech/xj) facilitate the development of Web Service applications.
Peshansky, Igor and Mukund Raghavachari. XML 2006 (2006). Articles>Web Design>Programming>XML
#33984
Word and OpenOffice for XML Authoring
In this session, three panellists and audience members will discuss creating XML documents using two familiar word processors: Microsoft Word and OpenOffice. Paul Bernard will introduce some real-world examples of how publishers are using Microsoft Word in XML workflows, and how Office 2007 and OpenXML will affect those processes. Jon Parsons will discuss XML, Office 2007, and content management for document integration in the middle tier. Lisa Richards will discuss XML authoring in OpenOffice.
Hatter, Clyde, Mark Jacobson and Jon Parsons. XML 2006 (2006). Articles>Word Processing>Information Design>XML
#33985
Making the Most of XML with Adobe InCopy and InDesign
This session provides an overview of several real-world case studies describing publishers who have implemented an XML-based process with Adobe InDesign, InCopy, and editorial and production management systems, such as K4 and Woodwing. The session also provides best practices for incorporating these products in a production workflow covering activities such as: How to import XML into the Adobe products; How to export XML out of the Adobe products; How to structure templates (styles to tag and tags to styles mapping).
Edson, Mike and Mark Jacobson. XML 2006 (2006). Articles>Content Management>XML>Adobe InDesign
#33986
Resistance is Futile: You Will Store XML
Industry standards consortia have defined thousands of exchange formats for business related messages in XML Increasingly, data conforming to industry exchange formats are being stored in files and database systems as XML (as well being mapped to relational data). This talk describes what happens when the exchange formats and the storage formats become one. Business applications can be built in new ways that can reduce development costs and more readily accommodate evolving business requirements. The use of generic tools rather than bespoke software becomes more attractive. The criteria for managing XML schemas and for XML schema evolution change. The talk will outline trends arising from the unification of storage formats and exchange formats. It will incorporate a case study to illustrate the main points.
Malaika, Susan. XML 2006 (2006). Articles>Information Design>XML>Case Studies
#33987
Pipeline processing is a powerful programming technique that can lead to programs that are easier to maintain and enhance and monolithic imperative programs. Developers familiar with the power of pipeline operations central to the UNIX operating system know how simple, modular tools can be chained together to accomplish a wide variety of complex tasks. XSLT pipelines offer the same advantage for XML transformation. Where UNIX pipelines are based around standard input and output of lines of text, XSLT pipelines rely on the structure of well-formed XML between stages. The panel members will demonstrate the value of a pipeline processing approach and discuss implementation specifics.
Page, Sam and Norman Walsh. XML 2006 (2006). Articles>Information Design>XML>Workflow
#33988
Three panellists talk about how they've applied agile development techniques to XML, followed by audience discussion and Q&A: Tony Coates will discuss XML and schema quality assurance using unit test frameworks. David Carver will discuss agile XML schema development. Claudia Lucia Jimenez-Guarin will discuss software construction for evolving systems with incomplete data definition.
Carver, David, Anthony Coates and Claudia Lucía Jimenez-Guarin. XML 2006 (2006). Articles>Information Design>XML>Agile
#33989
The "Unleashing the power of XML" presentation provides insight, from 20 years personal experience in the publishing industry, on the value of good markup and the challenges of migrating from SGML to XML based systems. We will review the results of an informal survey of the publishing industry that focuses on how XML is (and is not) being leveraged and the rationale behind these decisions. Finally, we will discuss a 'new' technology that has the potential to revolutionize the publishing industry as well as highlight some real world applications already leveraging this technology.
McBeath, Darin. XML 2006 (2006). Articles>Information Design>XML>Case Studies
#33991
Content Management System APIs
Panellists talk about two vendor-neutral programming interfaces for content-management systems. Joel Amoussou discusses JSR 170, a vendor-neutral Java API designed to work across many different content management systems. Michael Wechner discusses Neutron, an Open Content Management User Interface based on XML.
Amoussou, Joel and Michael Wechner. XML 2006 (2006). Articles>Content Management>Programming>XML
