On Sun, Jul 5, 2009 at 4:56 PM, Scott Cantor<> wrote:
>
> To put it another way, the HoK language is trying to constrain what you do
> when you create or process a particular confirmation method. If you turn
> around and somehow change that behavior, then how do I know what to do for
> that method?
My earlier argument for an implementer of the HoK Web Browser SSO
Profile is an example---you do nothing. The HoK Web Browser SSO
Profile can forever and always depend on CS-01 of the HoK Assertion
Profile. It doesn't matter what changes are subsequently made in
CS-02 of the latter.
Tom
