[OASIS Issue Tracker] Created: (IMI-33) Publishedidentity-1.0-os.xsd inconsistent with spec

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Published identity-1.0-os.xsd inconsistent with spec
----------------------------------------------------

                 Key: IMI-33
                 URL: http://tools.oasis-open.org/issues/browse/IMI-33
             Project: OASIS Identity Metasystem Interoperability (IMI) TC
          Issue Type: Bug
          Components: Schema
    Affects Versions: IMI 1.0 PR1
            Reporter: Michael Jones
            Priority: Critical


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.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira