...
For discussion: The normative form of most existing schemas is LDAP object classes. The Internet2 Software Integration Working Group is working toward a more abstract specification language for schema. This work is introduced in the document TAP Attribute Terminology. These normative specifications will be collected into A TAP Attribute Dictionary. For implementation in code, subsets of the attributes in the dictionary can be mapped to a choice of syntaxes, representations, and/or protocols as needed.
Proposed Document Relationships
| Code Block |
|---|
Schema Editorial Board
|
+-REFEDS/TAP Attribute Dictionary *
| |
| +-Representations
| |
| +-JSON
| +-XML
| +-RFC4512
| +-YAML
|
+-REFEDS Profiles
| |
| +-eduPerson *
| | |
| | +-Protocols
| | |
| | +-LDAP
| | +-SAML
| | +-OIDC
| |
| +-SCHAC *
| |
| +-Protocols
| |
| +-LDAP
| +-SAML
| +-OIDC
|
+-TAP Protocols
|
+-TAP ID Match Protocol * |
(This diagram includes Internet2 TAP work that could ultimately be merged with/into the SEB management structure.)
Items denoted with a * get their own git repositories for versioning.