• Date: Wednesday, October 16, 2019

• Time: 16:30 EDT

• Keith Wessel (co-chair) (v)

• Alan Buxey (v)

• Scott Cantor (v)

• Walter Hoehn (v)

• Nick Roy (v)

• Eric Goodman

1. Roll call (QV group participation agreement) 

2. Agenda bash

3. Approval of 9/18 meeting minutes

4. Review of Scott’s edits to SDP-SP23 sent to the list on 10/15

5. Possible confusion around wording of SDP-G02 and Nick’s proposed change

1. Quorum achieved

2. Agenda looks good

3. Approval of 9/18 meeting minutes

4.  

   1. Alan motioned

   2. Walter seconds

   3. Minutes approved

5. Review of Scott’s edits to SDP-SP23 sent to the list on 10/15

6.  

   1. Removing the reference was appropriate

   2. Shorter - that seemed good

   3. Not sure about references to other work so did not add any

   4. Might  want to consider changing the word ‘some’ to ‘most’ under discovery description.

   5. Could put ‘in many cases’ and not try to quantify it

   6. Less aspirational than a way of telling people that they’re doing it wrong.

   7. Anyone unhappy with what’s been presented?

   8. Scott would maybe rethink the wording in the normative requirement: We understand that it’s self-evident.

   9. Implementation profile calls out idpdisco as a MUST

   10. Seems like not a drop-able item, and wording seems good.

   11. Wording complements the implementation profile.

   12. No misgivings - we have rough consensus.

   13. AI: Scott commit - DONE

7. Possible confusion around wording of SDP-G02 and Nick’s proposed change

8.  

   1. REFEDS assurance list discussion - Pål and Eskil

   2. Put to rest with the minor wording tweak?

   3.  

      1. ...deployments MUST limit the size of each individual XML element's and attribute's text value they produce to 256 characters

   4. References content rather than making it clear you’re talking about string content. “XML attribute content”

   5. We have a recommendation

   6. Hard to be confused by the existing wording

   7. Discussion of which elements/attributes this applies to

   8. IDP-19 caused similar confusion

   9. This will be clearer if we are allowed to have FAQs. OASIS didn’t used to allow that.

   10. To define versus to not define via xs:String. Injects a level of understand of XML into the doc that is probably best avoided in this case. Could make it more confusing/lead to more pedantic complaints.

   11. AI: Scott going to come up with a suggestion offline.

   12. We aren’t going to be able to make it completely bullet-proof.

9. Next call: November 6, 2019. Waiting to hear back from Colin on process.

10. SP22 language needs to be moved up - italicized text should have been moved up under SP21.

11.  

    1. Seems right

    2. Scott will do at same time as other edits.

12. eduGAIN slack channel comment:

13.  

    1. Pål - SDP-SP39: SP requirement SDP-MD10:Common requirements - why SP logos a MUST? Not an error on our part. There for *reasons*.

• Date: Weds, Nov 06, 2019

• Time: 16:30 EDT

• Code: https://global.gotomeeting.com/join/110596309

• You can also dial in using your phone.
  
  
  

  United States: +1 (669) 224-3318

  
  
  

  Access Code: 110-596-309

  
  
  

  More phone numbers
  
  
  

  Australia: +61 2 8355 1038
  
  
  

  Austria: +43 1 2530 22500
  
  
  

  Belgium: +32 28 93 7002
  
  
  

  Canada: +1 (647) 497-9380
  
  
  

  Denmark: +45 32 72 03 69
  
  
  

  Finland: +358 923 17 0556
  
  
  

  France: +33 170 950 590
  
  
  

  Germany: +49 692 5736 7300
  
  
  

  Ireland: +353 15 360 756
  
  
  

  Italy: +39 0 230 57 81 80
  
  
  

  Netherlands: +31 207 941 375
  
  
  

  New Zealand: +64 9 282 9510
  
  
  

  Norway: +47 21 93 37 37
  
  
  

  Spain: +34 932 75 1230
  
  
  

  Sweden: +46 853 527 818
  
  
  

  Switzerland: +41 225 4599 60
  
  
  

  United Kingdom: +44 330 221 0097

NOTE: Do not follow the code with a "#" symbol as it may cause the code not to be recognized.