...
| comment # | Line/Reference # | Proposed Change or Query | Proposer / Affiliation | Action / Decision (please leave blank) |
|---|---|---|---|---|
| 1 | 14 | I think we can afford to spell out the word "number" in "# of values" (applies to all of eduPerson, actually) | ||
| 2 | 20, 36 | Please clarify the example ‘She/ella* O $ او, 她/她, היא’ – what are "O $" meant to signify here? (Not that I understand the rest of the string to the right of these characters but with both "O" and "$" coming from ASCII I feel I should be able to understand those.) | ||
| 3 | 30 | There's only one 'Example', maybe drop the plural. | ||
| 4 | 22-23 | "Preferred words to reference the person" is clunky. Why not replace those words with "These personal pronoun(s)"? | Andrew Morgan | |
| 5 | 36 | The example SAML atttributeValue includes a person's name ("Mona, ...") but this is the first occurrence of that convention in this document. I suggest introducing this construct with the list of examples on lines 19-20 or replacing the attributeValue with one of the examples from lines 19-20. | Andrew Morgan | |
| 6 | 30 | Why isn't there an LDIF/LDAP example? Other eduPerson attributes include an LDAP example, although eduPersonAnalyticsTag does not. | Andrew Morgan | |
| 7 | 11 | Line 11 is blank. Should there be an "EQUALITY caseIgnoreMatch" statement here? | Andrew Morgan | |
| 8 | 36-37 | Probably just a wrapping problem in the PDF, but I don't think the closing tag "</saml:AttributeValue>" should be directly after the last character of the string (no newline, no extra spaces). | Andrew Morgan | |
| 9 | 26 | Does the list of negative inferences need to include sex assigned at birth? (Or otherwise made non-exhaustive.) | ||
| 10 | 35 | " (Quotation Mark) vs ” (Right Double Quotation Mark) for XML attributes | Guy Halse | |