> From: Eve L. Maler [mailto:]
>
> I'm discovering that the descriptions of the operation of
> AuthorityKind
> and RespondWith are a bit misleading when it comes to QNames.
> I'd like
> to suggest a change that I'm happy to consider editorial, but I will
> wait for the group's consensus on this before making the change.
...
> It would be better to say something like this (underscores
> around new or
> changed material):
>
> For AuthorityKind: "For example, an attribute authority would be
> identified by AuthorityKind="samlp:AttributeQuery", _where there is a
> namespace declaration in the scope of this attribute that binds the
> saml: prefix to the SAML protocol namespace_."
the samlp: prefix, but otherwise OK.
> For RespondWith: "For example, a requestor that wishes to receive
> assertions containing only attribute statements _would_ [this was a
> lowercase "must"] specify
> <RespondWith>saml:AttributeStatement</RespondWith>, _where
> the prefix is
> bound to the SAML assertion namespace in a namespace
> declaration that is
> in the scope of this element_."
I think I put together the original text for these; I like the proposed
clarification.
- irving -
-----------------------------------------------------------------------------------------------------------------
The information contained in this message is confidential and is intended
for the addressee(s) only. If you have received this message in error or
there are any problems please notify the originator immediately. The
unauthorised use, disclosure, copying or alteration of this message is
strictly forbidden. Baltimore Technologies plc will not be liable for
direct, special, indirect or consequential damages arising from alteration of the
contents of this message by a third party or as a result of any virus being
passed on.
This footnote confirms that this email message has been swept for Content Security threats, including
computer viruses.
http://www.baltimore.com
This footnote confirms that this email message has been swept by
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.
