Proposal: tightly couple core code with documentation by pairing a code contributor with someone from the standards team who will focus on the documentation
Proposal: create a grant for building the test suite that will determine if a baseline server is compliant or not (will first need the spec to be finalized so we know what http requests must be supported)
v1 release planning:
standards spec expected to be delivered end of Q3
v1 release should closely follow the release of the spec
persistence package
should it be part of core? If so, should we specify the use of a "connector" so that all plugins do not have to be written in javascript in order to import and use the core packages?
DIDs
defined at integration - specific mapping to an internal dept
the standard can remain at an 'integration account' without requiring hard integration with an ERP user account
Agenda
Topics: