DOCSLIB.ORG

Ebxml Message Service Specification Defines a Set of Namespace-Qualified SOAP Header and 456 Body Element Extensions Within the SOAP Envelope

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ebxml Message Service Specification Defines a Set of Namespace-Qualified SOAP Header and 456 Body Element Extensions Within the SOAP Envelope 1 Message Service Specification 2 Version 2.0 rev C 3 OASIS ebXML Messaging Services Technical Committee 4 21 February 2002 Copyright (C) . January 2002 OASIS Open, Inc. All Rights Reserved. OASIS ebXML Messaging Services February 2002 5 Status of this Document 6 This document specifies an ebXML Message Specification for the eBusiness community. Distribution of 7 this document is unlimited. 8 The document formatting is based on the Internet Society’s Standard RFC format converted to Microsoft 9 Word 2000 format. 10 Note: Implementers of this specification should consult the OASIS ebXML Messaging Services Technical 11 Committee web site for current status and revisions to the specification 12 (http://www.oasis-open.org/committees/ebxml-msg/ ). 13 Specification 14 Version 1.0 of this Technical Specification document was approved by the ebXML Plenary in May 2001. 15 Version 2.0 of this Technical Specification document was approved by the OASIS Messaging Team as a 16 Technical Committee(TC) Specification, January 22, 2002. 17 Version 2.0 of this Technical Specification document is presented to the OASIS membership for 18 consideration as an OASIS Technical Specification, April 2002. 19 This version 20 V2.0 –Error! Hyperlink reference not valid. http://www.oasis-open.org/committees/ebxml- 21 msg/documents/ebMS_v2_0.pdf 22 Errata to this version 23 V2.0 –Error! Hyperlink reference not valid. http://www.oasis-open.org/committees/ebxml- 24 msg/documents/ebMS_v2_0_errata.html 25 Previous version 26 V1.0 – http://www.ebxml.org/specs/ebMS.doc 27 ebXML Participants 28 The authors wish to acknowledge the support of the members of the Messaging Services Team who 29 contributed ideas, comments and text to this specification by the group’s discussion eMail list, on 30 conference calls and during face-to-face meetings. Message Service Specification 2.0c Page 2 of 71 Copyright (C) The Organization for the Advancement of Structured Information Standards [OASIS], 2002. All Rights Reserved. Arvola Chan RosettaNet/TIBCO Doug Bunting Sun Microsystems, Inc Aynur Unal E2Open Himagiri Mukkamala Sybase Bob Miller GE Global eXchange Ian Jones British Telecom Brad Lund Intel™ Corporation Jeff Turpin Cyclone Commerce Brian Gibb Sterling Commerce Jim Hughes Hewlett Packard Bruce Pedretti Hewlett-Packard Kazunori Iwasa Fujitsu Limited Cedrec Vessell DISA Martin Sachs IBM Research Chris Ferris Sun Microsystems, Inc Pete Wenzel RosettaNet/SeeBeyond Cliff Collins Sybase Philippe DeSmedt Agentis Software Colleen Evans Sonic Software Prasad Yendluri WebMethods Jim Galvin Drummond Group Ralph Berwanger BTrade Dale Moberg Cyclone Commerce Sanjay Cherian Sterling Commerce Daniel Weinreb eXcelon Scott Hinkelman IBM David Burdett Commerce One Sinisa Zimek SAP David Fischer Drummond Group Yukinori Saito Ecom Dick Brooks Systrends, Inc 31 The UN/CEFACT-OASIS v1.0 Team – see Acknowledgments Copyright (C) . January 2002 OASIS Open, Inc. All Rights Reserved. OASIS ebXML Messaging Services February 2002 32 Table of Contents 33 Status of this Document ....................................................................................... 2 34 ebXML Participants .............................................................................................. 2 35 Introduction........................................................................................................... 7 36 1 Summary of Contents of this Document..............................................................................7 37 1.1.1 Document Conventions ...................................................................................................................... 8 38 1.1.2 Audience ............................................................................................................................................ 8 39 1.1.3 Caveats and Assumptions .................................................................................................................. 8 40 1.1.4 Related Documents............................................................................................................................ 8 41 1.2 Concept of Operation...............................................................................................................9 42 1.2.1 Scope................................................................................................................................................. 9 43 1.2.2 Background and Objectives................................................................................................................ 9 44 1.2.3 Operational Policies and Constraints ................................................................................................ 10 45 1.2.4 Modes of Operation.......................................................................................................................... 11 46 1.3 Minimal Requirements for Conformance ...............................................................................12 47 Part I. Core Functionality ................................................................................... 13 48 2 ebXML with SOAP.............................................................................................................13 49 2.1 Packaging Specification.........................................................................................................13 50 2.1.1 SOAP Structural Conformance......................................................................................................... 14 51 2.1.2 Message Package............................................................................................................................ 14 52 2.1.3 Header Container ............................................................................................................................. 14 53 2.1.4 Payload Container............................................................................................................................ 15 54 2.1.5 Additional MIME Parameters ............................................................................................................ 15 55 2.1.6 Reporting MIME Errors..................................................................................................................... 16 56 2.2 XML Prolog............................................................................................................................16 57 2.2.1 XML Declaration...............................................................................................................................16 58 2.2.2 Encoding Declaration ....................................................................................................................... 16 59 2.3 ebXML SOAP Envelope extensions ......................................................................................16 60 2.3.1 Namespace pseudo attribute............................................................................................................ 16 61 2.3.2 xsi:schemaLocation attribute ............................................................................................................ 16 62 2.3.3 SOAP Header Element..................................................................................................................... 17 63 2.3.4 SOAP Body Element ........................................................................................................................ 17 64 2.3.5 ebXML SOAP Extensions................................................................................................................. 17 65 2.3.6 #wildcard Element Content............................................................................................................... 18 66 2.3.7 id attribute ........................................................................................................................................ 18 67 2.3.8 version attribute................................................................................................................................18 68 2.3.9 SOAP mustUnderstand attribute....................................................................................................... 19 69 2.3.10 ebXML "Next MSH" actor URI .......................................................................................................... 19 70 2.3.11 ebXML "To Party MSH" actor URI .................................................................................................... 19 71 3 Core Extension Elements..................................................................................................19 72 3.1 MessageHeader Element ......................................................................................................19 73 3.1.1 From and To Elements ..................................................................................................................... 20 74 3.1.2 CPAId Element................................................................................................................................. 20 75 3.1.3 ConversationId Element ................................................................................................................... 21 76 3.1.4 Service Element ...............................................................................................................................21 77 3.1.5 Action Element ................................................................................................................................. 22 78 3.1.6 MessageData Element ....................................................................................................................
Load more

Recommended publications
  • TIBCO Businessconnect™ Ebxml Protocol User’S Guide — Ebms3/AS4 Standard
    TIBCO BusinessConnect™ ebXML Protocol User’s Guide — ebMS3/AS4 Standard Software Release 6.1 August 2015 Two-Second Advantage® Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO ActiveMatrix BusinessWorks Plug-in for BusinessConnect, TIBCO Administrator, TIBCO BusinessConnect, TIBCO BusinessConnect Palette, TIBCO Designer, TIBCO Enterprise Message Service, TIBCO Hawk, TIBCO Rendezvous, TIBCO Runtime Agent are either registered trademarks or trademarks of TIBCO Software Inc.
    [Show full text]
  • A SOAP-Based Model for Secure Messaging in a Global Context
    A SOAP-Based Model for Secure Messaging in a Global Context by Johannes Jurie van Eeden A SOAP-based Model for Secure Messaging in a Global Context by Johannes Jurie van Eeden Dissertation submitted in fulfillment of the requirements for the degree Magister Technologiae in Information Technology in the School of Information and Communication Technology at the Nelson Mandela Metropolitan University Promoter: Dr Maree Pather December 2005 Table of Contents Declaration ............................................................................................................. v Abstract.................................................................................................................. vi Acknowledgements................................................................................................ vii Acronyms and Abbreviations used.......................................................................viii Part I ...................................................................................................................... 1 Introduction............................................................................................................. 1 Chapter 1 ............................................................................................................... 2 Introduction............................................................................................................. 2 1.1 Problem Statement........................................................................................ 3 1.2 Objectives ....................................................................................................
    [Show full text]
  • Content Assembly Mechanism (CAM) Business Transaction Information Management
    Content Assembly Mechanism (CAM) business transaction information management What CAM Is The CAM approach provides these three The CAM specification provides an open critical abilities: – XML based system for using business rules to • documentation of business interchange define, validate and compose specific business transactions, documents from generalized schema elements • design-time assembly support with and structures. verification, and A CAM rule set and document assembly • runtime checking of information content. template defines the specific business context, content requirement, and transactional function Next we consider the limitations of current of a document. A CAM template must be approaches and technologies and how the capable of consistently reproducing documents capabilities that CAM provides can address that can successfully carry out the specific these shortcomings. transactional function that they were designed for. CAM also provides the foundation for The Present Tools and Their Limitations for creating industry libraries and dictionaries Addressing the Problem of schema elements and business document structures to support business process needs. The advent of XML has also meant that other new tools are available to advance the technology of automatic transaction content Solving the Inherent Problem of Automated handling. These include formal structure Information Integration definitions using XML schema (XSD) with Automated information integration has content control at the element level using been the Holy Grail of e-Business systems datatyping; then XSLT rules and XPath since before XML was conceived. Early expressions and semantic tools such as RDF attempts centered on the use of industry and OWL to provide machine understanding of standard transaction formats typified by EDI the role and usage of the XML based messages1.
    [Show full text]
  • Innovations in Resource Management and Mutual Aid Technology
    Innovations in Resource Management and Mutual Aid Technology July 22, 2021 National Alliance for Public Safety GIS (NAPSG) Foundation napsgfoundation.org | @napsgfoundation napsgfoundation.org | @napsgfoundation 1 Webinar Prep​ • Due to the large attendance, all participants are muted for the duration of the session to prevent background noise.​ • Please use the Q&A functionality within Zoom for questions that are relevant to the whole group.​ • We will address these Q&A at the end of the webinar!​ napsgfoundation.org | @napsgfoundation Today’s Objectives • Learn about FEMA’s National Resource Hub and how to gain access and start using the suite of resource management tools. • Gain insight into how the National Resource Hub can connect and share data with your other incident management systems, situational awareness apps, and other 3rd party systems today and in the future. • Learn what is in development to improve existing and innovate with new resource management and mutual aid technology tools and systems. • Find out what’s new in version 3.0 of the Implementation Guide on Information Sharing Standards and how you can use the guide in informing your agency’s technology selection and acquisition process to ensure interoperability and seamless information sharing. • Gain basic technical knowledge on the latest with the Emergency Data Exchange Language (EDXL) and how it supports building a National – and Global – network of interoperable incident management systems. napsgfoundation.org | @napsgfoundation 3 Agenda 2:00pm Introductions and Overview 2:10pm National Resource Hub - What It’s About - What It Can Do For You and Your Agency 2:25pm What’s Coming in the Job Aid and Technical Guidance for Incident Management Technology 2:35pm Know the Basics on EDXL and Why it Matters 2:55pm Actions & Next Steps 3:00pm Adjourned napsgfoundation.org | @napsgfoundation 4 Hosts and Panelists • Charlotte Abel, Strategic Manager, NAPSG Foundation • Harmon Rowland, Section Chief, FEMA National Integration Center • Rebecca Harned, Vice President, 4 Arrows Consulting, Inc.
    [Show full text]
  • T-Mobile International Ebxml B2B Gateway Solution
    An OASIS White Paper T-Mobile International ebXML B2B Gateway Solution Adoption of the ebXML Messaging Service and ebXML Collaboration Protocol Profiles and Agreements OASIS Standards By Pim van der Eijk For OASIS OASIS (Organization for the Advancement of Structured Information Standards) is a not-for-profit, international consortium that drives the development, convergence, and adoption of e-business standards. Members themselves set the OASIS technical agenda, using a lightweight, open process expressly designed to promote industry consensus and unite disparate efforts. The consortium produces open standards for Web services, security, e-business, and standardization efforts in the public sector and for specific industries. OASIS was founded in 1993. More information can be found on the OASIS web site at http://www.oasis-open.org/. OASIS also hosts the ebXML XML.org web site, http://ebxml.xml.org/, which serves as the official international community gathering place and information resource for the suite of ebXML standards. The ebXML Messaging Service (ebMS) OASIS Standard enables the transport, routing and packaging of e-business transactions. The ebXML Collaboration Protocol Profiles and Agreements (CPPA) OASIS Standard describes how trading partners engage in electronic business collaborations through the exchange of electronic messages. Both technical specifications are part of the ebXML modular suite of specifications. The OASIS Technical Committees working on ebMS and CPPA were originally formed in 2001. The ebXML Messaging Service specification, version 2.0 and the ebXML Collaboration Protocol Profiles and Agreements specification, version 2.0, became OASIS Standards in 2002. Along with two other specifications of the ebXML framework, both documents were approved by the International Standards Organisation as ISO/TS 15000-2 and ISO/TS 15000-1 in March 2004.
    [Show full text]
  • Emergency Management Standards
    Emergency Management Standards HL7 WGM International Council May 2019 Elysa Jones, Chair OASIS Emergency Management Technical Committee Emergency Interoperability Member Section [email protected] Agenda ▪ What is OASIS ▪ Joint work with HL7 - Tracking emergency patients - Hospital availability 2 Internationally recognized ▪ EU classifies OASIS as “one of the top three ICT consortia”. ▪ EU Regulation 1025/2012 allows OASIS specs to be referenced in public procurement ▪ OASIS is permanent member of EC’s European Multi-Stakeholder Platform on ICT Standardization ▪ OASIS TC Process is ANSI-accredited. 3 Established presence, Current agenda ▪ Nonprofit consortium ▪ Founded 1993 ▪ Global 5,000+ participants 600+ orgs & individuals in 100+ countries ▪ Home of 70+ Technical Committees ▪ Broad portfolio of standards: security, privacy, Cloud, M2M, IoT, content technologies, energy, eGov, legal, emergency management, finance, Big Data, healthcare, + other areas identified by members 4 OASIS → de jure OASIS Standard Also Approved As: Advanced Message Queuing Protocol (AMQP) ISO/IEC 19464 ebXML Collaborative Partner Profile Agreement ISO 15000-1 ebXML Messaging Service Specification ISO 15000-2 ebXML Registry Information Model ISO 15000-3 ebXML Registry Services Specification ISO 15000-4 Security Assertion Markup Language (SAML) ITU-T Rec. X.1141 Extensible Access Control Markup Language (XACML) ITU-T Rec. X.1142 OpenDocument Format (ODF) ISO/IEC 26300 Common Alerting Protocol (CAP) ITU-T Rec. X.1303 Computer Graphics Metafile (WebCGM) W3C WebCGM
    [Show full text]
  • Ebxml Web Services &
    ebXML Web Services & EDI XML Europe 2003 London 7 May 2003 Dale Waldt President, aXtive Minds, Inc. Program Development, OASIS Who Am I? Currently Director, aXtive Minds XML Training & Consulting [email protected] Program Development Consultant, OASIS XML Standards Consortium [email protected] Previously VP Technology, RIA Tax Publishing Group The Thomson Corporation XML Enables Robust e-Business Platforms Enables industry data interchange standards platform-independent data exchange electronic commerce user agents for automatic processing after receipt Enables software to handle specialized information distributed over the Web Enables use of metadata data about information help people & systems find information help information producers & consumers find each other The Complete XML Picture V V V V V V E E E E E E R R R R R R T T T T T T I I I I I I C C C C C C A A A A A A L L L L L L HORIZONTAL & WEB SERVICES PROCESS/CORE COMPONENTS MESSAGING (e.g. SOAP, ebXML TRP) FOUNDATION (e.g. XML, Schema, XSLT) CORE (e.g. TCP/IP, HTTP) The eBusiness Tidal Wave Business-to-Business Processes Sales and Distribution Consumer Services Internet Based Delivery The eBusiness Technologies Sales and Distribution B2B iMarketPlaces / Hubs XMLXML B2B iMarketPlaces / Hubs ASP’s (App’ Srvc Provider) B2C Integration Information Mining Web Services Directory Services First There Was EDI Electronic data Interchange (EDI) Fortune 1000 Facilitates global electronic trade ANSI X12 standards used in North America UN EDIFACT (EDI for Administration, Commerce & Transport) used in Europe and 95% elsewhere outside North America Purchase orders, invoices, wire transfers, Small to Medium receipts, etc.
    [Show full text]
  • 16Th ICCRTS “Collective C2 in Multinational Civil-Military Operations”
    16th ICCRTS “Collective C2 in Multinational Civil-Military Operations” Title of Paper Adapting WS-Discovery for use in tactical networks Topic(s) Primary: Topic 9: Networks and Networking Alternatives: Topic 8: Architectures, Technologies, and Tools, Topic 6: Experimentation, Metrics, and Analysis Name of Author(s) Frank T. Johnsen and Trude Hafsøe Norwegian Defence Research Establishment (FFI) P.O. Box 25 2027 Kjeller, Norway Point of Contact Frank T. Johnsen Norwegian Defence Research Establishment (FFI) P.O. Box 25 2027 Kjeller, Norway [email protected] Abstract The NATO Network Enabled Capabilities (NNEC) feasibility study has identified Web services as a key enabling technology for NNEC. The technology is founded on a number of civil standards, ensuring interoperability across different operating systems and programming languages. This also makes the technology a natural choice for interoperability also in multinational civil-military operations, where a large number of heterogeneous systems need to exchange information. Web services provide loose coupling and late binding, which are desirable properties in such a setting. Discovering available services in an operation is essential, and the discovery process must leverage standards to ensure interoperable information exchange. WS-Discovery is a standard for Web services discovery suited for dynamic environments and civil networks, but has high overhead and is not so suitable for tactical networks. Like the other Web services standards, it uses XML for encoding messages. In civil networks bandwidth is abundant, but in tactical networks XML may incur unacceptable overhead. However, the W3C has created a specification for efficient XML interchange (EXI), which reduces XML overhead by defining a binary interchange format.
    [Show full text]
  • Service Discovery in Hybrid Environments
    Service Discovery in Hybrid Environments Sabrina Alam Chowdhury Department of Informatics Faculty of mathematics and natural sciences UNIVERSITETET OF OSLO 01/08/2017 1 2 Service Discovery in Hybrid Environments 3 © 2017 Sabrina Alam Chowdhury Service Discovery in Hybrid Environments http://www.duo.uio.no/ Printed: Reprosentralen, University of Oslo 4 Abstract The thesis topic is based on Service discovery of heterogeneous Web services across hybrid environments. Here it also describes a clear definition of SOA and Web service with different standards to implement those services in different environments. Furthermore an analysis and survey of Web services standards also given in this thesis. An overview also discussed here that how different Web service discovery mechanism solution is currently available to discover services in different environments which include from cloud to non-cloud , non- cloud to cloud and other platforms with some research challenges on service discovery for SOAP and RESTful Web services. A prototype has been implemented as a proof of concept for enabling common service discovery for hybrid environments for different Web services. 5 6 Preface The thesis represents the final product of my master degree in Informatics at the University of Oslo. The work described herein is conducted under the supervision of Dr. Frank Trethan Johnsen and Cand. Scient. Trude Hafsøe Bloebaum. The thesis has been a long journey, and I would not have been able to complete it without the precious help and support given by various people. The learning curve of my career becomes so high, and I got to understand lots of interesting things while working on this thesis.
    [Show full text]
  • Department Informatik DEUS
    Department Informatik Technical Reports / ISSN 2191-5008 Christoph P. Neumann, Florian Rampp, Richard Lenz DEUS: Distributed Electronic Patient File Update System Technical Report CS-2012-02 March 2012 Please cite as: Christoph P. Neumann, Florian Rampp, Richard Lenz, “DEUS: Distributed Electronic Patient File Update System”, University of Erlangen, Dept. of Computer Science, Technical Reports, CS-2012-02, March 2012. Friedrich-Alexander-Universitat¨ Erlangen-Nurnberg¨ Department Informatik Martensstr. 3 · 91058 Erlangen · Germany www.informatik.uni-erlangen.de DEUS: Distributed Electronic Patient File Update System Christoph P. Neumann, Florian Rampp, Richard Lenz Institute of Computer Science 6 (Data Management) Dept. of Computer Science, University of Erlangen, Germany [email protected] Abstract—Inadequate availability of patient information aging of western society affects the public health sector, is a major cause for medical errors and affects costs in chronic diseases and multimorbidity become the focus of healthcare. Traditional approaches to information inte- interest, and the cost pressure rises. Chronic diseases and gration in healthcare do not solve the problem. Apply- multimorbidity, like cancer, diabetes, asthma, and cardiac ing a document-oriented paradigm to systems integra- insufficiency, require more healthcare parties than com- tion enables inter-institutional information exchange in healthcare. The goal of the proposed architecture is to mon diseases. Coevally, the rapid advance in medicine provide information exchange between strict autonomous leads to an advancing specialization of physicians that healthcare institutions, bridging the gap between primary is an additional cause for the increasing number of and secondary care. involved parties regarding a single patient’s treatment. In a long-term healthcare data distribution scenario, For improving the treatment quality and in order to the patient has to maintain sovereignty over any personal avoid unnecessary costs, an effective information and health information.
    [Show full text]
  • Ebxml Registry Information Model Version
    1 2 ebXML Registry Information Model 3 Version 3.0 4 OASIS Standard, 2 May, 2005 5 Document identifier: 6 regrep-rim-3.0-os 7 Location: 8 http://docs.oasis-open.org/regrep-rim/v3.0/ 9 Editors: Name Affiliation Sally Fuger Individual Farrukh Najmi Sun Microsystems Nikola Stojanovic RosettaNet 10 11 Contributors: Name Affiliation Diego Ballve Individual Ivan Bedini France Telecom Kathryn Breininger The Boeing Company Joseph Chiusano Booz Allen Hamilton Peter Kacandes Adobe Systems Paul Macias LMI Government Consulting Carl Mattocks CHECKMi Matthew MacKenzie Adobe Systems Monica Martin Sun Microsystems Richard Martell Galdos Systems Inc Duane Nickull Adobe Systems regrep-rim-3.0-os May 2, 2005 Copyright © OASIS Open 2005. All Rights Reserved. Page 1 of 78 12 13 Abstract: 14 This document defines the types of metadata and content that can be stored in an ebXML 15 Registry. 16 A separate document, ebXML Registry: Service and Protocols [ebRS], defines the services and 17 protocols for an ebXML Registry. 18 19 Status: 20 This document is an OASIS ebXML Registry Technical Committee Approved Draft 21 Specification. 22 Committee members should send comments on this specification to the [email protected] 23 open.org list. Others should subscribe to and send comments to the regrep- 24 [email protected] list. To subscribe, send an email message to regrep-comment- 25 [email protected] with the word "subscribe" as the body of the message. 26 For information on whether any patents have been disclosed that may be essential to 27 implementing this specification, and any offers of patent licensing terms, please refer to the 28 Intellectual Property Rights section of the OASIS ebXML Registry TC web page 29 (http://www.oasis-open.org/committees/regrep/).
    [Show full text]
  • Data Architecture (Elements/Templates/Value Sets) Tiger Team
    July 8, 2009 Version 1.0 HITSP Data Archiitecture Techniicall Note HITSP/TN903 Submitted to: Healthcare Information Technology Standards Panel Submitted by: Data Architecture (Elements/Templates/Value Sets) Tiger Team HITSP Data Architecture Technical Note Released for Implementation 20090708 V1.0 DOCUMENT CHANGE HISTORY Version Number Description of Change Name of Author Date Published 0.0.1 Review Copy Data Architecture (Elements/Templates/Value Sets) June 30, 2009 Tiger Team 1.0 Released for Implementation Data Architecture (Elements/Templates/Value Sets) July 8, 2009 Tiger Team HITSP Data Architecture Technical Note Released for Implementation 20090708 V1.0 2 TABLE OF CONTENTS 1.0 INTRODUCTION.................................................................................................................................6 1.1 Purpose and Scope ...................................................................................................................6 1.2 Intended Audience.....................................................................................................................6 1.3 Conventions used in this document ..........................................................................................6 1.4 Document Organization and Structure ......................................................................................6 1.5 Copyright Information ................................................................................................................7 2.0 EXECUTIVE SUMMARY ....................................................................................................................8
    [Show full text]