Allow arrays to be displayed in wallet

[JaceHensley]

We should allow arrays to be displayed to in a wallet. The items must be of type "string", "boolean", "number", "integer", or "array" (nested arrays)

[bumblefudge]

good suggestion on the call: inherit (or at least get inspo from) the OpenAPI data types

[andorsk]

specifically here: https://swagger.io/docs/specification/data-models/data-types/

[brentzundel]

also want this capability for arrays: https://github.com/decentralized-identity/wallet-rendering/issues/5#issue-1102078251

[colbyharrison]

Arrays of Objects should be included in this.

[andorsk]

I'm don't see a really good reason not to use the existing openapi types to do this. In fact, there's a ton of other standards we could add in from there including OneOf, etc. I think openapi types are actually very similar to JSONSchema ( if not identical ), but that seems like a reasonable way to move this forward.

Example: String array

{
  "type": "array",
  "items": 
    "type": "string"
}

Example: Object array

{
  "type": "array",
  "items": 
    "type": "object"
}

Example: Object array with properties

{
  "type": "array",
  "items": 
    "type": "object"
     "properties": {
        "id": {
           "type: "string"
        }
      }
}

The big concern here is it might be quite a big update to the specifications, so it might make sense to break this out into multiple PRs.

[andorsk]

Referencing the actual link here: https://identity.foundation/wallet-rendering/#using-path, where the issue is referencing.

[andorsk]

@brentzundel @csuwildcat Can we put this on the agenda for the next CC call. I have some thoughts here but I think this could end up being a larger change to the spec than a few tweaks, so I'd like to discuss first before putting a proposal together.

[andorsk]

linking to https://github.com/decentralized-identity/wallet-rendering/issues/21 as relevant.

[bumblefudge]

v1 or v2, important question for next week (shout out to colby for mentioning on today's call ) :D