This document was last revised or approved by the PSTC 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 http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=provision.

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 (http://www.oasis-open.org/committees/provision/ipr.php.

The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/provision/.

Notices

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 names "OASIS", "SPML" are trademarks 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 http://www.oasis-open.org/who/trademark.php for above guidance.

Table of Contents

1 Introduction. 5

2 Errata. 6

2.1 E1: Relaxed requirements for the use of <component>. 6

2.2 E2: The AddResponse example is missing a <pso> bracketing element. 6

2.3 E3: Remove the use of ReturnData.NOTHING. 7

2.4 E4: Add ReturnData.NOTHING to the core .xsd. 7

2.5 E5: Password psoID element namespace clarifications. 7

2.6 E6: Suspend capability namespace clarifications. 7

2.7 E7: Updates capability namespace clarifications. 8

2.8 E8: Search capability namespace clarifications. 8

2.9 E9: The Add Response is missing the <pso> element. 8

2.10 E10: The Modify Response is missing the <pso> element. 9

2.11 E11: The Lookup Response is missing the <pso> element. 9

2.12 E12: Relaxed requirements for the use of <data>. 10

A. Revision History. 11

1 Introduction

This document lists the reported errata and potential errata against the OASIS SPML 2.0 Committee Specifications and their disposition status.

Recommend changes are recorded here.

All of the recommended changes were discussed at the TC face-to-face meetings in October 2006 and various follow up conference calls.

2 Errata

2.1 E1: Relaxed requirements for the use of <component>

Document: Core

Description: The Core specification and the DSML profile are at odds, both in normative text, about the use of the <component> element.

The following lines of the core specification discuss the use of the <component>element:

1857, 1854, 1925, 1930, 1927

These should have an OR clause added that allows the use of profile-specified elements in lieu of <component>.

Original recommendation:

add "nor a " or OR to those lines, profile-specified elements.

Disposition: Approved by the TC by unanimous consent on 22 May 2007.

2.2 E2: The AddResponse example is missing a <pso> bracketing element.

Document: Core

Description: The AddResponse example, starting after line 1667, in the core specification is incorrect.

It is missing the <pso> element that encloses the <data> element, i.e.:

<spml:pso xmlns:spml="urn:oasis:names:tc:SPML:2:0">

...

</spml:pso>

The example should be:

<spml:addResponse status="spml:success" xmlns:spml="urn:oasis:names:tc:SPML:2:0">

<spml:pso xmlns:spml="urn:oasis:names:tc:SPML:2:0">

<spml:psoID ID="CN=John Doe,OU=accounting,DC=acme.com" targetID="acme.com "/>

<spml:data>

</attr>

</attr>

</attr>

</attr>

</spml:data>

</spml:pso>

</spml:addResponse>

Disposition: Approved by the TC by unanimous consent on 22 May 2007.

2.3 E3: Remove the use of ReturnData.NOTHING.

Document: Core

Description: There are several erroneous references to returnData=NOTHING. There is no enumerated type for NOTHING and all references to it should be removed.

The affected lines are:

1560-1561

1696-1697

1835-1836

3367-3368

Disposition: Approved by the TC by unanimous consent on 5 June 2007.

2.4 E4: Add ReturnData.NOTHING to the core .xsd.

Document: Core

Description: The core.xsd, as included in Appendix A, starting at line 4519, does not specify 'nothing' in the declaration of ReturnDataType. See E3.

Disposition: Disapproved by the TC by unanimous consent on 5 June 2007.

2.5 E5: Password psoID element namespace clarifications

Document: Core

Description: The password capability in the .xsd is ambiguous with regard to namespace. The specification should be changed to be clear that the psoID used in these elements should include the prefix of the password capability.

The affected lines are:

2702-2704

2749-2751

2792-2794

2841-2843

Disposition: Approved by the TC by unanimous consent on 22 May 2007.

2.6 E6: Suspend capability namespace clarifications.

Document: Core

Description: The suspend capability in the .xsd is ambiguous with regard to namespace. The specification should be changed to be clear that the psoID used in these elements should include the prefix of the suspend capability.

The affected lines are:

3807-3809

3862-3864

3916-3918

Disposition: Approved by the TC by unanimous consent on 22 May 2007.

2.7 E7: Updates capability namespace clarifications.

Document: Core

Description: The Updates capability needs namespace clarification.

The affected lines are:

4108 - The psoID should be in the updates namespace.

Disposition: Approved by the TC by unanimous consent on 22 May 2007.

2.8 E8: Search capability namespace clarifications.

Document: Core

Description: The Search capability explanations need namespace clarifications. Section 3.6.7.1.2 needs to be consistent with regard to the namespace for Search.

The affected lines are:

3417 - the PSO element should be in the search namespace

3464 - the iterator element should be in the search namespace

Disposition: Approved by the TC by unanimous consent on TBD.

2.9 E9: The Add Response is missing the <pso> element.

Document: DSML V2 Profile.

Description: The non-normative Add Response examples are missing the <pso> element. The examples on lines 203 - 219 read:

<spml:addResponse status="spml:success" xmlns:spml="urn:oasis:names:tc:SPML:2:0">

<spml:psoId ID="CN=John Doe,OU=accounting,DC=acme.com" targetID="acme.com "/>

<spml:data>

...

</spml:data>

</spml:addResponse>

The example should read:

<spml:addResponse status="spml:success" xmlns:spml="urn:oasis:names:tc:SPML:2:0">

<spml:pso>

<spml:psoId ID="CN=John Doe,OU=accounting,DC=acme.com" targetID="acme.com "/>

<spml:data>

...

</spml:data>

</spml:pso>

</spml:addResponse>

Disposition: Approved by the TC by unanimous consent on 22 May 2007.

2.10 E10: The Modify Response is missing the <pso> element.

Document: DSML V2 Profile.

Description: The non-normative Modify Response examples are missing the <pso> element. The examples on lines 235 - 238 read:

<spml:modifyResponse status="spml:success" xmlns:spml="urn:oasis:names:tc:SPML:2:0">

<spml:psoId ID="CN=Jane Doe,OU=accounting,DC=acme.com" targetID="acme.com "/>

</spml:modifyResponse>

The example should read:

<spml:modifyResponse status="spml:success" xmlns:spml="urn:oasis:names:tc:SPML:2:0">

<spml:pso>

<spml:psoId ID="CN=Jane Doe,OU=accounting,DC=acme.com" targetID="acme.com "/>

</spml:pso>

</spml:modifyResponse>

Disposition: Approved by the TC by unanimous consent on 22 May 2007.

2.11 E11: The Lookup Response is missing the <pso> element.

Document: DSML V2 Profile.

Description: The non-normative Lookup Response examples are missing the <pso> element. The examples on lines 252 - 269 read:

<spml:lookupResponse status="spml:success" xmlns:spml="urn:oasis:names:tc:SPML:2:0">

<spml:psoId ID="CN=John Doe,OU=accounting,DC=acme.com" targetID="acme.com "/>

<spml:data>

...

</spml:data>

</spml:lookupResponse>

The example should read:

<spml:lookupResponse status="spml:success" xmlns:spml="urn:oasis:names:tc:SPML:2:0">

<spml:pso>

<spml:psoId ID="CN=John Doe,OU=accounting,DC=acme.com" targetID="acme.com "/>

<spml:data>

...

</spml:data>

</spml:pso>

</spml:lookupResponse>

Disposition: Approved by the TC by unanimous consent on 22 May 2007.

2.12 E12: Relaxed requirements for the use of <data>

Document: Core

Description: The Core specification and the DSML profile are at odds, both in normative text, about the use of the <data> element within a <modification>.

The following lines of the core specification discuss the use of the <data>element:

1864-1866

These should have an OR clause added that allows the use of profile-specified elements in lieu of <data>.

Disposition: Approved by the TC by unanimous consent on 11 Sep 2007.

A. Revision History

Revision	Date	Editor	Changes Made
5	16 Jul 2007	Jeff Bohren	Converted to latest OASIS Template.
6	14 Aug 2007	Jeff Bohren	Fixed some disposition date issues.
7	11 Sep 2007	Jeff Bohren	Added issue E12.
8	8 Oct 2007	Jeff Bohren	Fixed URLs on title page.