Public Comments

The following documents underwent Public Review between 3 Oct 2011 and 2 Nov 2011:

See the OASIS official announcement for details about this Public Review.

The comments received during the Public Review period are itemized below.

SAML V2.0 Metadata Extensions for Registration and Publication Information Version 1.0

The following comments were received.

Comment 1

Reference

http://lists.oasis-open.org/archives/security-services-comment/201110/msg00000.html

From
Tom Scavo
Comment
The name of the schema file (saml-metadata-rpi-v1.0-wd06.xsd) is inconsistent with the rest of the document set.
Disposition
This is the result of OASIS's new standards process and is as intended.


Comment
[section 1.2] There is no (normative) reference to the accompanying schema.
Disposition
This is the result of OASIS's new standards process and is as intended.


Comment
[section 1.2] The reference [SAML2Errata] doesn't actually lead to SAML V2.0 Core, so I think the references need to be reorganized.
Disposition
That is the intended reference and is consistent with other SAML specifications.


Comment

[section 2.1.1] On line 66, it is indicated that the <mdrpi:RegistrationPolicy> element is optional, but the schema fragment on lines 70--79 indicates the <mdrpi:RegistrationPolicy> element is required.

Disposition
This will be fixed in the next revision.


Comment
[section 2.1.1] There are major discrepancies between the schema fragment on lines 70--79 and the schema document itself. (I won't detail each one since the differences are obvious.)
Disposition
This will be fixed in the next revision.


Comment
[section 2.2.1] Again, the schema fragment on lines 122--132 disagrees with the schema document itself.
Disposition
That will be fixed in the next revision.


Comment

[section 2.3.1] Since zero or more <mdrpi:Publication> elements are specified, that means that the <mdrpi:PublicationPath> element may be empty. Is this intended? If so, what does that mean?

Disposition
It means that no publication path is given.


Comment
[section 2.3.2] The three attributes defined in this section are redundantly defined twice. Redefine the schema so that these attributes are defined just once.
Disposition
An attribute group would increase the complexity of the schema and not offer any value. This change will not be made.


Comment

[section 2.4] Both of the <mdrpi:PublicationPath> elements illustrated in the example disagree with the element as defined in section 2.3.

Disposition
That will be fixed in the next revision.


Comment

Throughout both the document and the schema document, the XML and XML Schema code exhibits an annoying inconsistency in that there is sometimes a space before "/>" and sometimes not. To be consistent (in both this document set and other TC document sets), this extraneous space should be removed. (It is a hold over from XHTML, which is not relevant here.)

Disposition

As the whitespace is immaterial, the whitespace will be normalized such that there is consistently a space between the final double quote and '/>' in order to add some visual separation between the attribute definition and the end of the element definition.

PublicComments20111003-20111102 (last edited 2011-10-18 00:10:38 by lajoie)