On Jan 24, 2007, at 10:30 PM, anders conbere wrote:
All over the web there are code snippets and code examples, and just plain people showing of little programs they've written. This data is typical acompanied by an author or list of authors, a lisence, the language type and version and various other bits of meta data. This seems to me to be an excelent place for microformats.
It seems like this would be an interesting place to suggest an (optional) extension of this proposal to create a standard for class based syntax highlighting. It may too ambitious but marking up stuff inside <code> with class names corresponding to what is is (variable, function, array indirection, operator, etc) could lead the way towards making things that could, for example, find all `php` code with calls to the `function` named `ldap_connect`.
Also, we should keep in mind that <code> isn't always procedural programming code can be examples of CSS, XML, HTML, YAML, TeX, etc. Would we want to consider methods of categorizing code in a rich taxonomy -- distinguishing between `markup`, `functional` `procedural`, `object-oriented` <code> above the level of language? I'm guessing this approach is not a good idea.
-- Jonathan Williams NYU Steinhardt [EMAIL PROTECTED] +1 212 998 5308 _______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
