Tracing the long lineage of software that brought us Vim.
Some 4500 words after I decided to add a few comments and insights ... it’s a good idea to consider what happens when follow a handful rather simple and obvious rules of how to write code.
… concerned not just with the packaging of data (syntax), but the simultaneous transmission of the meaning with the data (semantics).
HTML and CSS have very good semantic compatibility, often appearing together in the same document.
This is on my mind lately as I consider the compatibility of web application sources with microformats, while building a utility to help identify any aspects of the web application sources which interfere with the desired interoperability embodied by microformats.
I currently describe my pre-release project as: “A utility which checks webapp sources for compatibility with microformats semantics”. Based on the foregoing, I’m considering changing the description a little. At the end of the day, the work is the program that helps find the issues in the code. I’m hopeful that someone with greater comfort discussing the topic will help me to gain some confidence in how I present the program. So long as it is providing some useful and desired outcome, I’ll be working on it for awhile longer. Hopefully work to benefit more than myself!
Before: it saw
a:hover>span and errored, saying “there is no such pseudo-class as
After: it sees
a:hover>span and putters along happily with element
:hover, child combinator
>, and element
Typical programming mistake, a missing plus (+)!