I think 2) and 3) are simple editorial. There may be
something more involved with 1)
1)
Core AC schema defines
RestrictedPasswordType with a minInclusive length for the password of 3
characters.
<xs:complexType
name="RestrictedLengthType">
<xs:complexContent>
<xs:restriction
base="LengthType">
<xs:attribute name="min"
use="required">
<xs:simpleType>
<xs:restriction
base="xs:integer">
<xs:minInclusive
value="3"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="max" type="xs:integer"
use="optional"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
Not clear to me why Core
should define a specific requirement of a minimum password length.
Putting such a restriction into Core rather than a particular
class would prevent anybody from defining
a new class with a minimum length of 2 characters?
2)
The class schemas all? still have the <AuthenticatingAuthority>
element. It was removed from the Core
schema and elevated to a child of
<AuthnStatement>
Propose removing
<AuthenticatingAuthority> from the class
schemas.
3) The Core
AC schema defines AuthnContextDeclarationBaseType with an
<AuthenticationMethod>, the classes use <AuthnMethod>
Propose renaming <AuthnMethod> in class schemas
to <AuthenticationMethod>
Paul