Skip to content

Conversation

bhox
Copy link
Contributor

@bhox bhox commented May 17, 2018

No description provided.

@bhox bhox requested a review from samdozor May 17, 2018 21:17

`supported_extensions`

**REQUIRED** array of extension keys as defined in 7.1.2.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • why is it required? If a processor does not support any extension - must they return an empty-list vs. null?
  • is it worth noting that this is with the intention that requests could be federated?
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • It keeps it in line with the others: all required. Someone could conceivably have 0 supported public identities (passing an empty array) and one or more supported extensions. What do you think?
  • I don't think it needs to be called out since it could work by aggregating the discovery info.
@bhox
Copy link
Contributor Author

bhox commented May 18, 2018

Updated pull to update:

  • extension definitions: namespacing, naming, definition structure, json-schema
  • extension representation in /discovery
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants