MSP SIG - Meeting 7 - 2023-06-20
Participants
Agenda
Overview of ODS 7.0 release
Pilot work via ACT to expose the Ed-Fi assessment as a “pull” API
Assessment vendor discussion
Materials
Data sheets for the assessment demand coordination topic LINK
Notes
ODS / API v7
See deck for details
Q: API and data standard decoupling - Can you use the same API for multiple versions?
Change in technology may require major version update to API but not data standard
Q: Is there an engineers only session where you can get into the details
The TAG can play some of this role
Q: Could decoupling be interpreted as enhancing API database and API server as principal products? Is there an official stance on this from a PR perspective?
We say fairly consistently that the database and API server are implementation artifacts and not standards. Please do surface other ways we can reinforce this.
The decoupling hopefully does the opposite: clarifies that the standard is the main artifact
For next meeting - discuss release cadence and diagramming
Pull API pilot
Some interest/support for the concept (one MSP shared a prior exploration of this concept they did)
Some concern that this changes current deployment patterns - there was a field example already where a MSP wanted to integrate ACT, but ACT wants to use their pull
One comment that a MSP would be more in favor of this kind of strategy if there is super robust ODS to ODS linkages that have first class configuration objects - pub sub kind of stuff.