Binding:
- A language binding is a language-specific implementation of the Symphony REST API, that facilitates implementations is that particular language.
- It can evolve into more elaborate clients that wrap into higher order functions
Framework:
- It can also evolve into broader framework, that allow addition of meaningful new capabilities (eg AI, NLP, etc.)

Current document refers to binding primarily.

Users expectations

As users of a "1.0" SDK, I would expect the following:

...

Foundation contribution criteria
- Active status: see Activation
Functional coverage meets, at time of release
- 0 Blockers on any functions
- 0 Critical on any functions
- 0 Major on any functions
- Need to discuss specific criticality definition
Non-functional definition
- Need to discuss what we recommend here, notably regarding:
  - load balancing, HA
  - supported topologies
  - performance/latency
- Standard built-in diagnostic
  - Connectivity status
  - Need to have a primary focus on real time capabilities and request/response (tie back to common concepts to other communications like SIP/SIMPLE, XMPP)
Functional integrity
- Primary "communication" use cases supported
  - Admin endpoints not necessary
- Other WG members/LLC to perform deep dive
- Integration test list, need to particularly address the crosspod aspect
  - Former user (Deleted) / Peter Monks think about xPod abilities in test pods
  - Former user (Deleted) / Former user (Deleted) propose a first set of integration tests
- LLC to publish Set Presence endpoint
Documentation integrity
- LLC to add SDK documentation into https://developers.symphony.com/ (or equivalent)
Working hello world sample
- Would be great to have a similar pattern

Launch activities

In addition to "standard" SSF communications:
all users of the Symphony Platform should be made aware of this significant milestone. For example:
- Outreach to Symphony LLC customers
- Joint coms on other media (eg Twitter)

...