Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Discussion of the problem we are trying to solve of sharing mappings and the ambiguity of a charter for the work

    • Drive agency buy-in?

    • Drive vendor buy-in and ownership?

  • Importance of governance tooling as a way of presenting agencies and others with mappings while not being embedding them in the technical details

  • Proposal: get MSPs to agree on 1 assessment mapping as as a path forward?first step

  • Discussion and agreement on difficulty to create a simple UI for this work mapping data (part of the problem solved by the ESP tools)

  • Open question of if this work might forcing mappings on Assessment assessment vendors - is that OK?

    • One perspective is that they these vendors can contribute to that mappingthose mappings

    • Another is that they should own the actual API implementation - that is the key step to having a voice in the mapping

    • Regardless: the concept is that we want them to be part of the community governance process that is being community-governed specifications

  • A way to work with 1EdTech on vendor/product IDs for the from their registry?

  • The agreed upon direction was generally to get the MSP community sharing mappings first, then think about growth elsewhere to other adjacent issues (see abovelike agency buy-in). On this, see actions below.

...

  1. EA to share a YAML file for 1 one assessment - NWEA Map Growth

  2. EA to present a how mapping decisions were made for that spec, with discussion

  3. (Ed-Fi) At the December MSP SIG, ask the questions:

    1. do MSPs like the YAML technology as a means of sharing mappings?

    2. do MSPs like the MAP Growth mapping provided?

...