Brent Miller, IBM Corporation
Julia McCarthy, IBM Corporation
Merri Jensen, SAS Institute, Inc.
Declared XML Namespace(s):
This document lists errata for Solution Deployment Descriptor (SDD) 1.0 OASIS Standard [SDD] produced by the SDD Technical Committee. The standard was approved by the OASIS membership on 1 September 2008.
This document was last revised or approved by the OASIS Solution Deployment Descriptor (SDD) Technical Committee on the above date. The level of approval is also listed above. Check the “Latest Version” or “Latest Approved Version” location noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (.
The non-normative errata page for this specification is located at
Copyright © OASIS® 2008. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The name "OASIS", is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see for above guidance.
Update pointers to schema files in Appendix A of the specification.
[SDD] OASIS Standard, “Solution Deployment Descriptor Specification", 1 September 2008
[Issue ER001 change summary: Appendix A of the SDD Specification 1.0 included direct references to schema file names and locations that reflected previous draft levels of the SDD schema. These references were not updated in the Open Standard draft of the SDD Specification 1.0 and thus referred to earlier drafts of the schema files. The content of the schema files has not changed; only the file names and URI locations are updated with this erratum. This erratum addresses issue ER001 by referring to a namespace document for the schema files, rather than to the schema files directly. In case future updates to schema files are needed, only the namespace documents will need to change; no additional changes will be required to the SDD Specification 1.0]
The SDD schema is implemented by multiple schema files. Types defined in each file are identified by a specific namespace prefix, as indicated in the following list:
[Specification 1.0 lines 4002 – 4014 follow. Change:]
§ cd04-sdd-common-1.0.xsd (prefix: sdd-common)
Contains definitions of common types used in the SDD specification, including identity and fix-identity types, UUID and version types, and the display text type.
§ cd04-sdd-deploymentDescriptor-1.0.xsd (prefix: sdd-dd)
Contains the deployment descriptor specification, including various content types.
§ cd04-sdd-packageDescriptor-1.0.xsd (prefix: sdd-pd)
Contains the package descriptor specification, including types related to packages and files.
§ sdd-common-1.0.xsd (prefix: sdd-common)
Contains definitions of common types used in the SDD specification, including identity and fix-identity types, UUID and version types, and the display text type. The following namespace document describes this namespace and contains a directory of links to related resources, including the CL1 and Full Schema files:
§ http://docs.oasis-open.org/sdd/v1.0/os/sdd-common-rddl-1.0.html sdd-deploymentDescriptor-1.0.xsd (prefix: sdd-dd)
Contains the deployment descriptor specification, including various content types. The following namespace document describes this namespace and contains a directory of links to related resources, including the CL1 and Full Schema files:
§ sdd-packageDescriptor-1.0.xsd (prefix: sdd-pd)
Contains the package descriptor specification, including types related to packages and files. The following namespace document describes this namespace and contains a directory of links to related resources, including the CL1 and Full Schema files:
Example SDDs showing the use of the schema can be found at the following address.
The following individuals have participated in the creation of this specification and are gratefully acknowledged:
Dr. Howard Abrams, CA
Mr. Lazar Borissov, SAP AG
Ms. Debra Danielson, CA
Mr. Robert DeMason, SAS Institute, Inc.
Mr. Robert Dickau, Macrovision Corporation
Mrs. Christine Draper, IBM
Mr. Adrian Dunston, SAS Institute, Inc.
Mr. James Falkner, Sun Microsystems
Mr. Keisuke Fukui, Fujitsu Limited
Mr. Randy George, IBM
Mr. Nico Groh, SAP AG
Mr. Frank Heine, SAP AG
Ms. Merri Jensen, SAS Institute, Inc.
Dr. Hiro Kishimoto, Fujitsu Limited
Mr. Thomas Klink, SAP AG
Mr. Jason Losh, SAS Institute, Inc.
Ms. Julia McCarthy, IBM
Mr. Art Middlekauff, Macrovision Corporation
Mr. Brent Miller, IBM
Mr. Ed Overton, SAS Institute, Inc.
Mr. Chris Robsahm, SAP AG
Dr. David Snelling, Fujitsu Limited