Present
Notes
- Albert gives an update: Talked to Enrique yesterday. SeamlessAccess release into staging doesn't have trustinfo in, so a little more time to develop.
- LibLynx in the vanguard of SPs moving from advanced integration
- Q: will REFEDS continue to host group when SeamlessAccess takes stewardship?
- 3 uses cases: SeamlessAccess, thiss.io used somewhere in Sweden, MyAccessID
- We have worked on the assumption that SeamlessAccess is just thiss.io. Albert notes that there's pyFF as well. Pål and Björn agree.
- Bjorn: trustinfo XML to JSON is in pyFF. No overlay; that's the only thing that's missing.
- How much time for REFEDS to develop the spec or to adopt?
- Put some data about SAX versus DOM and schema. Really need to be aware of different XML parsing in consumers.
- Is REFEDS a standards group or stop doing it!
- Value of SeamlessAccess: champions standard IdP discovery
- How could Seamless take this forward
- host its own, but it's name recognition is limited and the audince is mainly publishers
- REFEDS, as we talked about
- NISO, but it's pretty much the same audience as SeamlessAccess, just publishers
- National federations need to work together with SeamlessAccess
- InCommon could generate a specific export aggregate for SeamlessAccess, but only needs one profile
- SPs want to add IdPs. Examples of that are bilateral SPs, OpenAthens federation, but also Sweden eID
- Need to get the metadata of bilateral IdPs into the discovery service
- What if we say no? Would publishers migrate?
{"serverDuration": 54, "requestCorrelationId": "546fec8c50adaa7e"}