Abstract: A computer program which uses a set of mappings between XML logical structures and business information model logical structures, in which the mappings describe how a document in a given XML based language conveys information in a business information model.

Abstract: Motivation: The eXtensible Markup Language (XML) is an emerging standard for structuring documents, notably for the World Wide Web. In this paper, the authors present XML and examine its use as a data language for bioinformatics. In particular, XML is compared to other languages, and some of the potential uses of XML in bioinformatics applications are presented. The authors propose to adopt XML for data interchange between databases and other sources of data. Finally the discussion is illustrated by a test case of a pedigree data model in XML.

Abstract: This document specifies XML (Extensible Markup Language) digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere.

Abstract: An XML-aware file system exploits attributes encoded in an XML document. The file system presents a dynamic directory structure to the user, and breaks the conventional tight linkage between sets of files and the physical directory structure, thus allowing different users to see files organized in a different fashion. The dynamic structure is based upon content, which is extracted using an inverted index according to attributes and values defined by the XML structure.

Abstract: We present a change-centric method to manage versions in a Web WareHouse of XML data. The starting points is a sequence of snapshots of XML documents we obtain from the web. By running a di algorithm, we compute the changes between two consecutive versions. We then represent the sequence using a novel representation of changes based on completed deltas and persistent identi ers. We present the foundations of the logical representation and some aspects of the physical storage policy. The work presented here was developed in the context of the Xyleme project of massive XML warehouse for XML data from the Web. It has been implemented and tested. We brie y discuss the implementation.

Abstract: A method for converting relational data to XML (eXtensible Markup Language) is provided. The method can use a greedy algorithm to efficiently construct materialized XML views of relational databases. A greedy algorithm designed for XML view definition queries is provided for decomposing a large query into smaller queries and determining which query will run faster without actually running the query.

Abstract: In response to a user request, an Identity System generates an Output XML containing raw identity information organized in accordance with a set of XML templates. The Identity System dynamically determines the desired response type and prepares the response from the Output XML. One response type is server-side processing—the Identity System combines the Output XML with XSL stylesheets to generate a HTML response. An alternative response type is client-side processing—the Identity System supplies the user with the Output XML. In further client-side embodiments, the Identity System provides XSL stylesheet references along with the Output XML. Additional embodiments provide for the Identity System to perform customized post-processing on the Output XML.

Abstract: Techniques are provided for XML data storage and query rewrites in relational databases. According to certain embodiments of the invention, a mechanism is provided to allow the user to store an XML document in a relational database and to submit mapping information that indicates a mapping of each field of the XML document to the column in the relational database in which the data from each field is stored. If the user submits an XML query to access the data in the XML document that is stored in the relational database, then a mechanism is provided to generate a database query based on the XML query and the mapping information.

Abstract: The growth of the Internet and the Web is revolutionizing the way companies interact with their suppliers, partners, and clients, by enabling a substantial automation of the full spectrum of their business activities. As we move into the 21st century economy, the primary form of automation will be B2B e-commerce, in which enterprises interact with each other through entirely automated means. As an example, consider an electronic market place in a vertical industry segment, in which suppliers and buyers tie into a common IT infrastructure to exchange goods and services. This forms a supply chain in which buyers need (a) to investigate possible suppliers, (b) to check the terms and conditions under which suppliers can do business, (c) to interoperate with the suppliers enterprise support systems, i.e., workflows, and (d) to monitor ordering/purchasing for possible delays, unexpected events, react to such events, etc. This paper presents an original framework for specifying, enacting and supervising e-services on the Web. This framework is based on XML and rules-based support for products/services description and workflow mediation across organizations. Traditionally, WorkFlow Management Systems (WFMS) have focused on homogeneous and centrally controlled environments for binding people and processes within the boundary of a single organization. In the context of B2B e-commerce, WFMSs need to support collaboration between various autonomous parties, some of which may even have conflicting business goals. More precisely, they must cope with heterogeneous enterprise support environments (e.g., through different WF systems), to model the interaction of independent partners by abstracting the internal details of their activities (e.g., through different WF schemas), and finally to facilitate flexible linking and monitoring of inter-enterprise processes (e.g., through different WF enactments). To address these challenges we are currently developing a workflow mediation middleware which relies on three basic technologies: (a) the XRL workflow specification language [13, 18] for representing in XML heterogeneous workflow schemas and enactments, (b) an XML query language [4, 5] for manipulating both complex product and service descriptions, and (c) the Vortex rule-based language [12, 6] that supports heuristic reasoning in order to take on-line business decisions during the workflow execution. During recent years, workflow interoperation has received considerable attention. Numerous research projects and prototypes have been proposed [16, 2] while basic interoperability between various vendor WFMSs has been a subject of standardization efforts by the Object Management Group (see Workflow

Abstract: In this paper, our objective is to define a security model for regulating access to XML documents. Our model offers a security policy with a great expressive power. An XML document is represented by a tree. Nodes of this tree are of different type (element, attribute, text, comment...etc). The smallest protection granularity of our model is the node, that is, authorisation rules granting or denying access to a single node can be defined. The authorisation rules related to a specific XML document are first defined on a separate Authorisation sheet. This Authorisation sheet is then translated into an XSLT sheet. If a user requests access to the XML document then the XSLT processor uses the XSLT sheet to provide the user with a view of the XML document which is compatible with his rights.

Abstract: A method for converting relational data to XML (Extensible Markup Language) is provided. The method, sometimes referred to as SilkRoute, provides a general, dynamic and efficient tool for viewing and querying relational data in XML. SilkRoute can express mappings of relational data in XML that conforms to arbitrary public document type definitions. Also, SilkRoute can materialize the fragment of an XML view needed by an application and it can fully exploit the query engine of a relational database management system whenever data items in an XML view need to be materialized.

Abstract: There has been recent interest in using relational database systems to store and query XML documents. Each of the techniques proposed in this context works by (a) creating tables for the purpose of storing XML documents (also called relational schema generation), (b) storing XML documents by shredding them into rows in the created tables, and (c) converting queries over XML documents into SQL queries over the created tables. Since relational schema generation is a physical database design issue -- dependent on factors such as the nature of the data, the query workload and availability of schemas -- there have been many techniques proposed for this purpose. Currently, each relational schema generation technique requires its own query processor to efficiently convert queries over XML documents into SQL queries over the created tables. In this paper, we present an efficient technique whereby the same query-processor can be used for all such relational schema generation techniques. This greatly simplifies the task of relational schema generation by eliminating the need to write a special-purpose query processor for each new solution to the problem. In addition, our proposed technique enables users to query seamlessly across relational data and XML documents. This provides users with unified access to both relational and XML data without them having to deal with separate databases.

Abstract: Many organizations and enterprises establish distributed working environments, where different users need to exchange information based on a common model. XML is widely used to facilitate this information exchange. The extensibility of XML allows the creation of generic models that integrate data from different sources. For these tasks, several applications are used to import and export information in XML format from the data repositories. In order to support this process for relational repositories we developed the X-Database system. The base of this system is an XML-Schema file that describes the logical model of interchanged information. Initially, the system analyses the syntax of the XML-Schema file and generates the relational database. Then it handles the decomposition of valid XML files according to that Schema and the composition of XML documents from the information in the database. Finally the system offers a flexible mechanism for modifying and querying database contents using only valid XML documents, which are validated over the XML-Schema file's rules.

Abstract: In this paper, we present a data and an execution model that allow for efficient storage and retrieval of XML documents in a relational database. The data model is strictly based on the notion of binary associations: by decomposing XML documents into small, flexible and semantically homogeneous units we are able to exploit the performance potential of vertical fragmentation. Moreover, our approach provides clear and intuitive semantics, which facilitates the definition of a declarative query algebra. Our experimental results with large collections of XML documents demonstrate the effectiveness of the techniques proposed.

Abstract: XML is increasingly becoming the format of choice for information exchange, in critical areas such as government, finance, healthcare and law, where integrity is of the essence. As this trend grows, one can expect that documents (or collections thereof) may get quite large, and clients may wish to query for specific segments of these documents. In critical applications, clients must be assured that they are getting complete and correct answers to their queries. Existing methods for signing XML documents cannot be used to establish that an answer to a query is complete. A simple approach has a server processing queries and certifying answers by digitally signing them with an on-line private key; however, the server, and its on-line private key, would be vulnerable to external hacking and insider attacks. We propose a new approach to signing XML documents which allows untrusted servers to answer certain types of path queries and selection queries over XML documents without the need for trusted on-line signing keys. This approach enhances both the security and scalability of publishing information in XML format over the internet. In addition, it provides greater flexibility in authenticating parts of XML documents, in response to commercial or security policy considerations.

Abstract: An Identity System delivers customized request responses that integrate the results of multiple programs. The Identity System receives and translates a user request. The Identity Systems employs a program service to identify all the programs required to complete the request. The Identity System uses a XML data registry to retrieve a XML template and XSL stylesheet for each program. The Identity System executes all of the programs for the request and organizes their results into a single data structure, based on the templates for each program. The Identity System then applies attribute display characteristics to convert the data structure into a single Output XML. The Output XML can be provided directly to the user or receive further processing using the retrieved XSL stylesheets.

Abstract: We address the problem of efficiently constructing materialized XML views of relational databases. In our setting, the XML view is specified by a query in the declarative query language of a middle-ware system, called SilkRoute. The middle-ware system evaluates a query by sending one or more SQL queries to the target relational database, integrating the resulting tuple streams, and adding the XML tags. We focus on how to best choose the SQL queries, without having control over the target RDBMS.

Abstract: Foreword. Preface. Part I. FOUNDATIONS. Chapter 1. Convergence of Communities. Models for e-Business. Stakeholder Communities. Consumer. Business Analyst. Web Application Specialist. System Integration Specialist. Content Developer. Road Map for This Book. Part I. Foundations. Part II. XML Vocabularies. Part III. Deployment. Steps for Success. Chapter 2. What Is an XML Application? HTML, XML, and XHTML. XML Vocabularies. XML Presentation. Cascading Style Sheets. XSLT Stylesheets. Chapter Summary. Steps for Success. Chapter 3. What Is a UML Model? Models and Views. Requirements Workflow. Use Case Diagram. Analysis Workflow. Activity Diagram. Model Management Diagram. Collaboration Diagram. Design Workflow. Class Diagram. Object Diagram. Sequence Diagram. Component Diagram. The Unified Process. Chapter Summary. Steps for Success. Chapter 4. e-Business Integration with XML. Use Case Analysis. Catalog Vocabulary Requirements. Shared Business Vocabularies. Define Business Vocabulary. Create XML Schema. Validate Message. Transform Message Content. Process Workflow and Messaging. Define Business Process. Build Workflow Model. Define Message Protocol. Application Integration. Create Application Classes. Create Legacy Adapter. Chapter Summary. Steps for Success. Chapter 5. Building Portals with XML. Use Case Analysis. Content Management. Define Business Vocabulary. Create Content. Assign Content Metadata. Portal Design. Design Portlet. Design Content Template. Create Stylesheet. Design Portal Layout. Customize Portal Layout. Wired and Wireless Convergence. Chapter Summary. Steps for Success. Part II. XML VOCABULARIES. Chapter 6. Modeling XML Vocabularies. What Is a Vocabulary? CatML Vocabulary. Simplified Product Catalog Model. Mapping UML to XML. XML Metadata Interchange. Disassembling UML Objects into XML. UML Classes to XML Elements. Inheritance. UML Attributes to XML Elements. UML Attributes to XML Attributes. Enumerated Attribute Values. Mapping UML Compositions. Mapping UML Associations. Roots and Broken Branches. Packaging Vocabularies. FpML Vocabulary. UML Packages. XML Namespaces. Chapter Summary. Steps for Success. Chapter 7. From Relationships to Hyperlinks. Expanded CatML Vocabulary. XML Standards for Linking. XML ID and IDREF. Xpath. Xpointer. Xlink. A Hyperlinked CatML Vocabulary. Product Bundles. Product Details. Taxonomy of Categories. Chapter Summary. Steps for Success. Chapter 8. XML DTDs and Schemas. The Role of an XML Schema. XML Document Type Definition. DTD Attribute Declarations. DTD Entity Declarations. Limitations of DTDs. W3C XML Schema. Datatypes and Datatype Refinement. Schemas Compatible with DTDs. Advanced Schema Structures. Replacement or Coexistence? Chapter Summary. Steps for Success. Chapter 9. Generating XML Schemas from the UML. Principles of Schema Generation. Generating DTDs. Relaxed DTDs. Strict DTDs. Generating W3C XML Schemas. Relaxed Schemas. Strict Schemas. XLink Support. Controlling Schema Strictness. UML Extension Profiles. An Extension Profile for XML. Profile Applied to CatML. Chapter Summary. Steps for Success. Part III. DEPLOYMENT. Chapter 10. Vocabulary Transformation. Reasons for XML Transformation. Alternative Vocabularies. Filtering Sensitive or Irrelevant Data. Presenting XML Documents. Exporting Non-XML Data. Introduction to XSLT. XSLT Processing Model. Transformation Rules. Integrating CatML with RosettaNet. Importing a RosettaNet Dictionary. Exporting a RosettaNet Sales Catalog. Chapter Summary. Steps for Success. Bibliography. Chapter 11. B2B Portal Presentation. Portal Analysis Model. Transforming XML Documents into Portlets. A Portlet for Product Display. A Portlet for Promotional Discounts. Discount Transformation. RSS Transformation. Chapter Summary. Steps for Success. Chapter 12. e-Business Architecture. Requirements for e-Business Architecture. Deploying Web Services. Message Protocols in XML. Web Service Description. Web Service Discovery. CatX Component Architecture. Display Portal Content. Update Newsfeed. Query Catalog Content. Integrate Supplier Catalog. Execute Currency Trade. Query Schema Repository. Query Service Registry. Chapter Summary. Steps for Success. Part IV. APPENDIXES. Appendix A. Reuse of FpML Vocabulary. Trading Party Model. Appendix B. MOF and XMI. Meta Object Facility. XML Metadata Interchange. Appendix C. UML Profile for XML. Introduction. Stereotypes. Bibliography Example. References. Index.

Abstract: A method and system for modifying program applications of a legacy computer system to directly output data in XML format models the legacy computer system, maps the model to an XML schema and automatically modifies one or more applications to directly output XML formatted data in cooperation with a writer engine and a context table. A modeling engine lists the incidents within the applications that write data and generates a report data model. The report data model includes statically determined value or type of the data fields and is written in a formal grammar that describes how the write operations are combined. A modification specification is created to define modifications to the legacy computer system applications that relate applications that write data to the XML schema. A code generation engine then applies the modification specification to the applications to write modified applications that, in cooperation with a writer engine and context table, directly output XML formatted data from the legacy computer system without a need for transforming the data.

Abstract: Currently dozens of XML-based applications exist or are under development. Many of them offer DTDs that define the structure of actual XML documents. Access to these documents relies on special purpose applications or on query languages that are closely tied to the document structures. Our approach uses ontologies to derive a canonical structure, i.e. a DTD, to access sets of distributed XML documents on a conceptual level.We will show how the combination of conceptual modeling, inheritance, and inference mechanisms on the one hand with the popularity, simplicity, and flexibility of XML on the other hand leads to applications providing a broad range of high quality information.

Abstract: Techniques are provided for mapping XML data and metadata from data in relational databases. According to certain embodiments of the invention, a mechanism is provided to allow the user to use a database query to retrieve data form a relational database in the form of XML documents by canonically mapping object relational data to XML data and canonically mapping object relational schemas to XML-Schemas. The mechanism causes the generation of XML-schema information for the XML documents.

Abstract: An environment for composing software permits the separation of control functions from information about the context in which the control functions operate. The software composition environment is used to make a system which will translate XML documents into models and vice-versa. The translation system is used to translate an XML document having one DTD into an XML document having another DTD by translating the first XML document into a model representing the semantics of the XML document and translating the model into the second XML document (2005). The system for translating XML documents into models employs a general technique for translating any XML documents into a mirror model (2107) that reflects the structure of the XML document and a general technique of using tag pattern models (2109) to obtain information from one model and using it to make or modify another model. In the system for translating XML document, the tag pattern models are used to translate mirror models into semantic models and vice-versa.

Abstract: Managing multiple versions of XML documents represents an important problem, because of many applications ranging from traditional ones, such as software configuration control, to new ones, such as link permanence of web documents. Research on managing multiversion XML documents seeks to provide efficient and robust techniques for (i) storing and retrieving, (ii) exchanging, and (iii) querying such documents. In this paper, we first show that traditional version control methods, such as RCS, and SCCS, fall short from satisfying these three requirements, and discuss alternative solutions. First, we enhance RCS with a temporal page clustering policy to achieve objective (i). Then, we discuss a reference-based versioning scheme that achieves both objectives (i) and (ii) and is also effective at supporting simple queries. The topic of supporting complex queries, including temporal ones, meshes with the burgeoning interest of database researchers in XML as a database description language, and in XML query languages. In this context, the XML versioning problems are akin to those of transaction time management for databases of objects and semistructured information. Nevertheless, the need to preserve the natural ordering of XML documents frequently requires different techniques.

Abstract: XML is an emerging standard for the representation and exchange of Internet data. Along with document type definition (DTD), XML permits the execution of a collection of queries, using XPath to identify data in XML documents. In this paper we examine how XML data can be stored and queried using a standard relational database management system (RDBMS). For this, we propose a technique for automatic mapping from an XML document to relations within the RDBMS. We demonstrate that our novel approach preserves the nested structure of the XML documents. By hiding database details we devise a seamless, transparent framework for user access to XML data. In order to achieve this, we propose a novel mechanism for translating an XPath query into an SQL statement. Furthermore, we propose efficient techniques for the construction of an XML document on the fly from the result set of the SQL statement. We also present findings in terms of query response time on the comparative performance of different techniques for the construction of an XML document on the fly.

Abstract: A method and system are for transforming an XML document structured according to a set of XML grammar rules to at least one XML document structured according to at least one subset of the set of XML grammar rules. The system includes a controller capable of executing a set of programmable instructions for retrieving at least one grammar restriction style sheet (GRSS) corresponding to at least one subset of a set of XML grammar rules, where the at least one GRSS includes transformation rules for transforming an XML document to at least one XML document structured according to the at least one subset of the set of XML grammar rules; and a transformation engine for using the transformation rules of each retrieved GRSS for transforming data elements of the XML document to data elements structured according to the at least one subset of the set of XML grammar rules to transform the XML document to the at least one XML document structured according to the at least one subset of the set of XML grammar rules. The method includes the steps of retrieving at least one GRSS corresponding to the at least one subset of a set of XML grammar rules, where the at least one GRSS includes transformation rules for transforming an XML document to at least one XML document structured according to the at least one subset of the set of XML grammar rules; and transforming data elements of the XML document using the transformation rules of the at least one retrieved GRSS to data elements structured according to the at least one subset of the set of XML grammar rules to transform the XML document to the at least one XML document structured according to the at least one subset of the set of XML grammar rules.

Abstract: Managing multiple versions of XML documents represents an important problem for many traditional applications, such as software configuration control, as well as new ones, such as link permanence of web documents. Research on managing multiversion XML documents seeks to provide efficient and robust techniques for storing, retrieving and querying such documents. In this paper we present a novel approach to version management that achieves these objectives by a scheme based on Durable Node Numbers and timestamps for the elements of XML documents. We first present efficient storage and retrieval techniques for multiversion documents. Then, we explore the indexing and clustering strategies needed to assure efficient support for complex queries on content and on document evolution.

Abstract: A system, method, and a computer program product for dynamically generating rules for XSL transformations by operating on an XML/XSL DOM representing a tree structure of an XML document in memory. User generated properties are received and transformed into XML/XSL nodes in memory. XML/XSL DOM is modified with the transformed XML/XSL nodes containing XSL rules of transformation with a variable dynamically generated by the user. The modified XML/XSL DOM is processed to generate a document in a specified format. Newly generated dynamic XSL rules override imported rules in the XML/XSL DOM.

Abstract: This document standardizes five new media types -- text/xml, application/xml, text/xml-external-parsed-entity, application/xml- external-parsed-entity, and application/xml-dtd -- for use in exchanging network entities that are related to the Extensible Markup Language (XML). This document also standardizes a convention (using the suffix '+xml') for naming media types outside of these five types when those media types represent XML MIME (Multipurpose Internet Mail Extensions) entities. XML MIME entities are currently exchanged via the HyperText Transfer Protocol on the World Wide Web, are an integral part of the WebDAV protocol for remote web authoring, and are expected to have utility in many domains.

Abstract: A method, system, and computer program product for efficient processing of Extensible Markup Language (XML) documents in Content Based Routing (“CBR”) networks. Specifically, the method involves converting existing XML documents to a machine-oriented notation (“mXML”) which is significantly more compact than XML, while still conveying the content and semantics of the data and the structure of the document. Documents are converted from XML to mXML upon entering a CBR subnetwork and/or upon receipt by an mXML-capable device. The documents are then processed in mXML format. Devices within the inventive system are provided with an awareness of whether target devices or processes are mXML-capable. Documents being routed to a target which is mXML-capable are passed in mXML format while documents being routed to a target which is not mXML-capable are converted to XML before they are passed.