InCommon Technical Discussions

[Tom Barton <>]

I think everyone, including every AAC member, agrees that errorURL belongs among the Baseline required metadata elements. It was my failure to recognize early in the Baseline Expectations development process that different perspectives were being applied to the term "MDUI information", and that the associated SAML specification that emerged as the "right" perspective does not mention errorURL. AAC has already considered whether to declare it as included within Baseline Expectations v1 and decided that it must be explicitly incorporated into v2. Hence recommended for now, but will be required in v2. I'm really sorry that my oversight led us to this situation!

Speculating a bit about timing, the AAC has a very full plate of Baseline process implementation tasks that will likely take them through ~May 2018 (cf. https://spaces.internet2.edu/display/BE/Baseline+Processes+Roadmap), and they can't realistically take up v2 matters until sometime afterward.

Tom

On 11/10/2017 1:12 PM, Steven Carmody wrote:

On 11/8/17 3:58 PM, Cantor, Scott wrote:

I'd like to see errorURL be required with guidance around what should be behind it.

+1

We all know how many years it will take to develop consensus on version 2, get it approved, get it accepted, and get it widely implemented. Not to mention the versioning problems.

If we send this back to the AAC right now, it will add an extra 2-3 on this to the process for this version. That's trivial, compared to how long it will take to promulgate V2.

In addition, given all the comments int his thread, we're probably sending it back to the AAC anyway.

So, I'd vote strongly for making errorURL a MUST, along with guidance.

-- 
Tom Barton
Sr Consultant for Cyber Security & Data Privacy
IT Services, University of Chicago
+1 773 834 1700 (w)

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature