Shibboleth Developers

["RL 'Bob' Morgan" <>]

> Well, while acknowledging the differences of the scoped attributes, I
> would say that all the attributes have to be documented somewhere with
> regard to their SAML representation. Just knowing that the attribute
> value(s) would be pulled out as is doesn't define things like what the
> AttributeNamespace would be, what the schema type would be, etc. One can
> make better assumptions in the simple cases, but there's still defining
> to be done. So I don't see them as all that different.

OK, sure, even more reason for a doc to do this, and it still seems like a
future eduPerson spec could incorporate this.  I guess for now this would
be filling in the "Standard Encoding" section of Walter's doc?

And, er, what *is* the AttributeNamespace we're using for these?
"urn:mace:shibboleth:1.0:attributeNamespace:uri"?

> I'm not yet convinced there's no grouping that could be done for other
> sets of attributes, though certainly not all.

Well, maybe someday there will be standards-body-blessed URIs for these
that we can use (though maybe the "just use urn:oid" argument will prevent
this).

> Ultimately, I guess maybe I just don't think it matters all that much.
> I'd like to see DNS records put in place to resolve these URNs to our
> documents so that we can build clickable registries of these, whatever
> they're called.

Hmm, via DDDS?  Do you have a clear idea of how that would work?  I don't
...

 - RL "Bob"


------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--