On Mon, Apr 8, 2013 at 3:30 PM, Marvin Addison <marvin.addi...@gmail.com> wrote: > +1 for the process outline generally. I have some concerns about target dates. > >> * Community Review/Feedback - April 8th - April 20nd > > May not be enough time for client maintainers. If we want them to > carefully review the specification and consider the impact to their > project, which I hope is the intent, then it's likely not enough time. > I think one of the design goals of the spec, backward compatibility, > is particularly important for client maintainer feedback. I'm fairly > pessimistic it's achievable in some clients where the XML parsing libs > are weaker (mod_auth_cas), but maintainers' thoughtful feedback is far > more valuable.
Given the limited nature of the change and the fact that process has been going on publicly, I'm hopeful that client devs were already aware of the changes and that two weeks would be enough for anyone who hasn't yet reviewed the draft. The biggest issue for clients is the potential for the optional cas attributes to show up in validate response. Most (all?) of them already handle this case? Best, Bill > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: wgt...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
