Shibboleth Developers

[Scott Cantor <>]

> This is just a terminology clash, then.  "Attribute type" is 
> precisely the phrase used in X.500 and LDAP for this entity.  

Ok. What do they call the type of the attribute type? I know there are 
"types" of LDAP attribute types, but I assume they don't call
them attribute type types...

> I suppose my intent with "urn:mace:dir:attribute-type:" was 
> to have a URN that could refer to both the 
> LDAP-context-defined and SAML/XML-context-defined object with 
> the same semantic.  I guess "attribute-type" is too 
> overloaded.  Just "attribute" is already overloaded of 
> course, since in XML it means something else.  I could live 
> with "attribute-def", but of course that means changing things ...

I guess I could live with that. Your proposal was just to remove the 
eduPerson "sub-arc", and put everything under one heading. I
guess that avoids the concern about what to call the sub-arc for other 
attributes, though I understand Keith's point about eduPerson
incoporating the other classes.

I think without the sub-arc, we'd have your proposal, with colons, and no 
fragids, since there's no real document behind a one-level
collection of attributes.

If we kept the sub-arc, we'd just be tweaking our current proposal:

urn:mace:dir:attribute-def:eduPerson#<name>

-- Scott

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

    http://archives.internet2.edu/

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