I read the title, went to the link, then started to read the "understanding" document and still don't know what this actually is and its application. It must a

I read the title, went to the link, then started to read the "understanding" document and still don't know what this actually is and its application. It must assume that all of the jargon words are already well known by its readers but it should definitely start with what problem a "schema framework" solves, which might then allow me to understand how this fixes it. My concern with many high-level constructs is that they quickly become a bureaucratic exercise divorced from how people actually do their work so only corporates will use it even if it is super useful.