Identity Metasystem Interoperability Version 1.0 Errata

Committee Draft 01

4 May 2010

Specification URIs:

This Version:

http://docs.oasis-open.org/imi/identity/v1.0/cd/identity-1.0-errata-cd-01.html

http://docs.oasis-open.org/imi/identity/v1.0/cd/identity-1.0-errata-cd-01.doc (Authoritative)

http://docs.oasis-open.org/imi/identity/v1.0/cd/identity-1.0-errata-cd-01.pdf

Previous Version:

N/A

Latest Version:

http://docs.oasis-open.org/imi/identity/v1.0/identity-1.0-errata.html

http://docs.oasis-open.org/imi/identity/v1.0/identity-1.0-errata.doc (Authoritative)

http://docs.oasis-open.org/imi/identity/v1.0/identity-1.0-errata.pdf

Technical Committee:

OASIS Identity Metasystem Interoperability (IMI) TC

Chair(s):

Marc Goodner, Microsoft Corporation

Anthony Nadalin, Microsoft Corporation

Editor(s):

Michael B. Jones, Microsoft Corporation

Related work:

This specification errata is related to OASIS Specification Identity Metasystem Interoperability Version 1.0.

Declared XML Namespace(s):

http://docs.oasis-open.org/imi/ns/identity-200810

http://schemas.xmlsoap.org/ws/2005/05/identity

Abstract:

This document lists errata for OASIS Standard Identity Metasystem Interoperability Version 1.0 [IMI 1.0] produced by the Identity Metasystem Interoperability (IMI) Technical Committee. The standard was approved by the OASIS membership on 1 July 2009.

Status:

This document was last revised or approved by the Identity Metasystem Interoperability TC 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/imi/.

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/imi/ipr.php).

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

Notices

Copyright © OASIS® 2010. 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 http://www.oasis-open.org/who/trademark.php for above guidance.


Table of contents

1        Introduction. 5

1.1 Issues Addressed. 5

1.1.1 Issue IMI-33. 5

1.2 Namespaces. 5

1.3 Schema. 6

1.4 Normative References. 6

1.5 Non-Normative References. 6

2        Typographical/Editorial Errors. 7

2.1 Section 3.1.1 minOccurs Values. 7

3        Normative Errors. 8

Appendix A.       Acknowledgements. 9

Appendix B.       Revision History. 10


1      Introduction

1.1 Issues Addressed

The following issues related to Identity Metasystem Interoperability Version 1.0 as recorded in the [IMI Issues] have been addressed in this document.

1.1.1 Issue IMI-33

Issue

Description

IMI-33

Published identity-1.0-os.xsd inconsistent with spec

Description:

http://docs.oasis-open.org/imi/identity/v1.0/os/identity-1.0-os.xsd contains:

  <xs:element ref="tns:TokenServiceList" minOccurs="0" />
  <xs:element ref="tns:SupportedTokenTypeList" />
  <xs:element ref="tns:SupportedClaimTypeList" />

whereas the schema in Section 3.1.1 of
http://docs.oasis-open.org/imi/identity/v1.0/os/identity-1.0-spec-os.html includes:

  <ic:TokenServiceList> ... </ic:TokenServiceList>
  <ic:SupportedTokenTypeList> ... </ic:SupportedTokenTypeList> ?
  <ic:SupportedClaimTypeList> ... </ic:SupportedClaimTypeList> ?

This is exactly backwards from the xsd in terms of which fields are optional.

Within the IMI 1.0 spec, Section 3.1.1 matches 3.1.1.2, which specifies that TokenServiceList MUST be provided, 3.1.1.3, which specifies that SupportedTokenTypeList SHOULD be provided, and 3.1.1.4, which specifies that SupportedClaimTypeList SHOULD be provided, so the spec is internally consistent.

Proposal:

Update the xsd to match the spec, as an errata action. Specifically, the lines cited would become:

  <xs:element ref="tns:TokenServiceList" />
  <xs:element ref="tns:SupportedTokenTypeList" minOccurs="0" />
  <xs:element ref="tns:SupportedClaimTypeList" minOccurs="0" />

Action Taken:

The schema file was updated to match the specification, as per the proposal.

Show »

Update the xsd to match the spec, as an errata action. Specifically, the lines cites would become:   <xs:element ref="tns:TokenServiceList" />   <xs:element ref="tns:SupportedTokenTypeList" minOccurs="0" />   <xs:element ref="tns:SupportedClaimTypeList" minOccurs="0" />

1.2 Namespaces

Table 1 lists the XML namespaces that are used in this document.

Prefix

XML Namespace

Specification(s)

tns

http://schemas.xmlsoap.org/ws/2005/05/identity

IMI 1.0 [IMI 1.0]

xs

http://www.w3.org/2001/XMLSchema

XML Schema [Part 1, 2]

Note that the versions identified in the above table supersede versions identified in referenced specifications.

1.3 Schema

A copy of the XML Schemas for this document can be found at:

http://docs.oasis-open.org/imi/identity/v1.0/cd/identity-1.0-errata-cd-01.xsd

1.4 Normative References

[IMI Issues]            IMI TC Issues List
http://tools.oasis-open.org/issues/browse/imi

[IMI 1.0]                  OASIS Standard, “Identity Metasystem Interoperability V1.0”, July 2009. http://docs.oasis-open.org/imi/identity/v1.0/os/identity-1.0-spec-os.pdf

[XML Schema, Part 1] H. Thompson et al., “XML Schema Part 1: Structures”, May 2001.  http://www.w3.org/TR/xmlschema-1/

[XML Schema, Part 2] P. Biron et al., “XML Schema Part 2: Datatypes”, May 2001.  http://www.w3.org/TR/xmlschema-2/

1.5 Non-Normative References

N/A

2      Typographical/Editorial Errors

2.1 Section 3.1.1 minOccurs Values

The tns:InformationCard schema had minOccurs values defined that did not match the values defined in the specification. The following schema fragment was corrected.

Original, incorrect, schema fragment

  <xs:element name="InformationCard" type="tns:InformationCardType" />

  <xs:complexType name="InformationCardType">

    <xs:sequence>

      <xs:element ref="tns:InformationCardReference" />

      <xs:element ref="tns:CardName" minOccurs="0" />

      <xs:element ref="tns:CardImage" minOccurs="0" />

      <xs:element ref="tns:Issuer" />

      <xs:element ref="tns:TimeIssued" />

      <xs:element ref="tns:TimeExpires" minOccurs="0" />

      <xs:element ref="tns:TokenServiceList" minOccurs="0"/>

      <xs:element ref="tns:SupportedTokenTypeList" />

      <xs:element ref="tns:SupportedClaimTypeList" />

      <xs:element ref="tns:RequireAppliesTo" minOccurs="0" />

      <xs:element ref="tns:PrivacyNotice" minOccurs="0" />

      <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

    </xs:sequence>

    <xs:attribute ref="xml:lang" use="required"/>

  </xs:complexType>

Updated, correct, schema fragment

  <xs:element name="InformationCard" type="tns:InformationCardType" />

  <xs:complexType name="InformationCardType">

    <xs:sequence>

      <xs:element ref="tns:InformationCardReference" />

      <xs:element ref="tns:CardName" minOccurs="0" />

      <xs:element ref="tns:CardImage" minOccurs="0" />

      <xs:element ref="tns:Issuer" />

      <xs:element ref="tns:TimeIssued" />

      <xs:element ref="tns:TimeExpires" minOccurs="0" />

      <xs:element ref="tns:TokenServiceList" />

      <xs:element ref="tns:SupportedTokenTypeList" minOccurs="0" />

      <xs:element ref="tns:SupportedClaimTypeList" minOccurs="0" />

      <xs:element ref="tns:RequireAppliesTo" minOccurs="0" />

      <xs:element ref="tns:PrivacyNotice" minOccurs="0" />

      <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

    </xs:sequence>

    <xs:attribute ref="xml:lang" use="required"/>

  </xs:complexType>

3      Normative Errors

N/A

Appendix A. Acknowledgements

The editor would like to acknowledge the contributions of the OASIS Identity Metasystem Interoperability Technical Committee, whose voting members at the time of publication were:

Participants:

John Bradley, Individual

Scott Cantor, Internet2

Marc Goodner, Microsoft (Chair)

Michael B. Jones, Microsoft (Editor)

Dale Olds, Novell

Anthony Nadalin, Microsoft (Chair)

Drummond Reed, Cordance

Appendix B. Revision History

Revision

Date

Editor

Changes Made

cd-01

4 May 2010

Michael B. Jones

Incorporate formatting feedback from OASIS staff

cd-01

27 April 2010

Michael B. Jones

Produce committee draft 1 from editor’s draft 1

ed-01

14 April 2010

Michael B. Jones

First draft, correcting issue IMI-33