We'll need a good representational form first, a UI/UX language or family of languages, something we can standardize on, develop, and use regularly to first est

We'll need a good representational form first, a UI/UX language or family of languages, something we can standardize on, develop, and use regularly to first establish representations of key, foundational concepts. Basically, we would need to scrape http://ui-patterns.com/ http://ui-patterns.com/ into a UI object ontology, map a bunch of its unstructured data about why each pattern solves some set of problems, and then we'd need a-whole-nother related problem solving analyzer system that could use that data to produce a software model. OMG recently released an Interaction Flow Modeling Language, http://www.ifml.org/ http://www.ifml.org/ , and that seems like it has some added range of expressiveness compared to UML and some of their other description languages. I like these OMG guys since they seem to synthesize Semantic Web research and ongoing best practices pretty well.