| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Logistics
...
1) Roll Call
- Paul Trevithick *
- Axel Nennker *
- Scott Cantor
- Keith Uber *
- Philip Philippe Clement
- Gael Gourmelen
- Bob Morgan
- Benoit Bailleux
Regrets:
- John Bradley
*Voting members
This meeting is was quorate (3 of 4).
2) Minutes
Approve We approved the following minutes:
3) Nominations for co-chairs
Scott: Proposed Made the motion that Bob Morgan and Paul Trevithick continue as co-chairs
Gael: Seconded
Vote ...the vote passed unanimously thus Bob, Philippe and Paul are now the co-chairs
4) OASIS UI Profile for SAML Metadata
Paul: What does "containing role" meansmean?
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 [].
5) Paris ULX meeting
Proposed agenda topics:
- Next documents to publish from ULX WG
- Extension of the "driven-by-RP" UX scenario to an "ISA based" scenario: Is there any additional work to do
- Claims & Metadata: What are they, and how to circulate them among the actors (RP, IdP, ISA)
- Other suggestions?
Scott: the problem with the ISA model is that the ISA knows a lot less about the RP/SP. We've looked at it this way: if you want to get the ISA involved then we assume it has access to metadata, but and if it wanted to get some more RP/SP-specific informaiton (e.g. a filtered list of IdPs) it could fetch the XRD from the RP/SP.
Paul: Coming It appears that coming up with the RP/SP XRD is the next logical piece of work. Perhaps we could work on this in Paris.
...