[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [security-services] AI-19 re: Versioning in protocol messages andassertions
Attached is the item I raised last January re: versioning in protocol messages and assertions. The referenced line numbers are no longer correct, but the point is still valid - the use of versioning in the SAML XML documents is a little ambiguous.
Actually, perhaps another question needs to be addressed before the specific questions below. That is, do we need this version info in our schema at all? The SAML protocol and assertion versions can be directly determined from the name of the schema files we define. Is this adequate? How do other TC's handle this issue? Rob Philpott -----Original Message-----
Line 1229: What does it mean to call this "SAML Protocol 1.0"?
<element name="ProtocolVersionInfo" type="samlp:ProtocolVersionInfoType"/> <complexType name="ProtocolVersionInfoType"> <attribute name="MajorVersion" type="integer" use="required"/> <attribute name="MinorVersion" type="integer" use="required"/> </complexType>
<element name="VersionInfo" type="saml: VersionInfoType"/> <complexType name="VersionInfoType"> <attribute name="MajorVersion" type="integer" use="required"/> <attribute name="MinorVersion" type="integer" use="required"/> </complexType>
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC