Shibboleth Developers

["Scott Cantor" <>]

I've answered most of this elsewhere, but there was one specific point I
wanted to correct.

> Shibboleth has its fingerprint on other portions of section 2, as
> well.  For example, the Scope attribute is a Shib addition, isn't it? 

No. The Scope XML attribute is supported by Shibboleth because that's the
profile of these eduPerson attributes we chose to use. This is merely
retroactive documentation of that profile.

A better understanding of XML at the time would have probably led to it
being namespace-qualified, but again, I'm sorry. I did the best I could. I
had a lot to juggle and I knew nothing about XML when this all started (and
now I kind of wish I could forget all of it).

In practice, it doesn't really matter that it's not qualified. The
AttributeValue element has no rules. Anything is fair game. The content is
100% dictated by the attribute definition. That's what this document is, a
set of definitions.

Also, the scope *concept* has nothing to do with Shibboleth. It's my opinion
that it was a useful abstraction to use when handling attributes of certain
types and the fact that I got serious push back when I made some noise about
dropping it suggests that I'm not completely out in left field on that.

-- Scott