...
Paul: What does "containing role" mean?
Scott: SAML metadata is organized into entities and roles. And entity is a network service. Different roles are defined for different kinds of roles. IdP and SP are the principle roles. Extensions are expressed at the entity or a the role level. E.g. an entity that was acting as an IdP and an SP role.
Paul: Where Why are attributes not mentioned?
Scott: Because they are mentioned elsewhere ?(i.e. in other SAML specs). SAML's history is one of more pre-configured relationships vs. more dynamism as with Infocard.
Scott: We did reject having any alt tag for the icons. Also updated the spec that display names should be amenable to accessibility.
Keith: Is there support for localizing the graphics for each language?
Scott: Yes, that is supported
Bob: A distinction is being make between elements in here that are signable vs. things that are okay to be self-asserted. Looking at the URL statements (e.g. privacy statements), their content is variable.
Scott: Some parts of this spec were inputs from existing federation deployments. Some is overkill from my point of view.
Bob: We might want a schema that is independent of the kind of document. If you want to stick the element in metadata that's okay, if you want it in an XRD that's okay.
Scott: This is problematic because XRD has evolved to simple property-based vs. XML extensions. We might want an abstract model above the level of these two expressions.
...