- markup (76)
- xml (11)
- xslt (23)
- pipelines (8)
- atom (9)
- overlapping markup (6)
- schema (11)
- creole (5)
- dtll (1)
- xforms (1)
- xpath (1)
- xquery (2)
- coding (2)
- datagovuk (1)
- genealogy (4)
- hardware (1)
- linked data (16)
- modelling (1)
- named graphs (1)
- opendata (1)
- provenance (1)
- psi (3)
- skos (1)
- sparql (4)
- Talis (7)
- unicode (1)
- uri (4)
- versioning (1)
- visualisation (6)
- web (78)
- google (4)
- html5 (5)
- jQuery (2)
- rdf (46)
- ontologies (2)
- rdfa (8)
- rdfQuery (5)
- rest (6)
- wikis (1)
- work (3)
- legislation (2)
- xmlsummerschool09 (2)
- life (28)
- children (5)
- equality (6)
- gtd (1)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (11)
- ukgc09 (1)
- xtech (9)
- xtech2008 (3)
- blog (8)
- drupal (3)
Re: Evolving Standards
I pretty much agree. This is why HTML5 is being designed as evolutions of HTML4 rather than a big overhaul (indeed, we keep punting things that people suggest to HTML6 or beyond, to avoid succumbing to too serious feature-creep).
I don’t think anyone wants to eliminate RDFa, eRDF, Microformats, ruby, <marquee>, <blink>, or any number of other extensions to HTML. Some of them (e.g. the drag and drop model Microsoft invented for IE) eventually get adopted as core parts of the language, others (e.g. <ruby>) get simplified, adapted and included, yet others (<marquee>, <blink>) get replaced by features in other languages (e.g. CSS).
BTW HTML has a number of extension mechanisms, for details please see the FAQ entry on extensions in HTML5.
HTML6, 7, 8 will continue extending HTML in the directions we need.