@benohanlon it is simply astonishing that you would recommend the Cardano Problem Statement (CPS) as a path forward after leaving the CIP Process entirely off of the ecosystem map.
Effectively this made the counterproductive marketing statement — very publicly at the recent convention — that the Cardano community fulfils all these ecosystem roles without a open standards process… or in fact any standards process.
This discrepancy is especially strange given that NFTs were offered for this map: since the standards for NFTs were all committed, synchronised and evolved together through some of Cardano’s earliest and most successful CIPs. Now an “ecosystem map” without a CIP process has been committed to the blockchain permanently through this round of NFTs.
This was all pointed out on the IOG Developer Discord, with no response as of this time. If you are looking for a way forward, yes of course it would help for IOG Marketing to acknowledge the CIP process in any & every way possible: since it currently appears to have escaped marketing efforts entirely.
As already emphasised on the Discord issue, there is no lack of support for CIPs from IOG itself: whose project teams remain committed through the CIP framework to documenting their work and providing vital feedback for standards proposed by the community. Newcomers to the process (including IOG Marketing team members) are welcome to learn more about the CIP process at the newly mounted Wiki:
https://github.com/cardano-foundation/CIPs/wiki
@benohanlon based on 3+ years of supporting the CIP process as an editor & co-architect, I would be happy to help you convert the ecosystem representation into a standardised document: ideally version-tracked as text. I can guarantee you would have huge support from everyone in the CIP community in this effort.
We could then be sure that further vital parts of Cardano’s ecosystem aren’t neglected… either in support or in public acknowledgement… through a document that can be continually improved by consensus, as all our CIPs are, without having to be constantly reformulated with each iteration vulnerable to manual errors and misunderstandings.