Support multiple nationalities?

Comments (6)

1. 

   Nat Sakimura

   • changed status to open

   Questions is to support an array. Use case clarification needed

   • 2019-07-18T14:27:33+00:00
2. 

   gffletch

   It seems like it’s safer to allow the nationality attribute to be an array, but if there is only one, it can be presented as the direct value of the claim. This is a something many specs with JSON data support. This provides a future proof mechanism while not requiring implementation of more than one until we have a clear use case.

   • 2019-07-18T14:28:41+00:00
3. 

   Torsten Lodderstedt reporter

   I‘m leaning towards having a single value as long as we do not have a use case.

   We can make it an array later if needed.

   • 2019-07-18T14:33:11+00:00
4. 

   gffletch

   Going from a single value to an array will be a breaking change. Probably ok if this is between implementors draft and final, but something to consider.

   • 2019-07-18T20:02:52+00:00
5. 

   Torsten Lodderstedt reporter

   decision in the call on Aug 1st: we make it an array

   • 2019-08-01T15:14:21+00:00
6. 

   Torsten Lodderstedt reporter

   • changed status to resolved

   changed definition in -07 to array of strings

   • 2019-08-12T14:45:55+00:00
7. Log in to comment