dive into mark: “I’ve retired my use of the Q tag, after deciding that it creates more problems than it solves.” This time I don't share Marks solution. I'd suggest to still use the Q tag, but add your own quotes around them. And to prevent browsers from adding their own quotes, use this bit of CSS: q:before, q:after { content: ''; }

My weblog archive page has been defunct for a while now. Today I replaced it with a dynamic search page, which uses the Google web service through XooMLe. The disadvantage of using Google is that it doesn't seem to return every possible result. But the advantages are that the results are ordered by relevance, and it shows the sentences that contain the search terms.

Today I tried a different approach for XHTML 2.0. I created an XSL stylesheet that converts XHTML 2.0 to XHTML 1.0. Mozilla and IE6 can apply the tranformation themselves. Other browsers can use the w3c xslt service.

Some more info for those who'd like to start using XHTML 2.0 for every day use. The XHTML 2.0 example page is for the browsers plain XML. So absolutely nothing works what you'd expect from normal HTML. Every functionality has to be explained to the browser. CSS makes it easy to provide the site layout. Yesterday I coded the link functionality. Today I added support for images in Mozilla and Opera 6. But don't expect to be able to add an input element any time soon.

I converted an archive page to XHTML 2.0. It works in IE6, Opera 6 and Mozilla. It is styled with CSS. I had to do some coding to get the links to work. For IE6 I made an HTC behavior that creates handlers for mouse events (yuck). For Mozilla I made an XBL binding that adds XLink attributes. And Opera 6 has CSS extensions for links. Being allowed to make every element a link makes the html code very clean. Sections structure the page very well. And the navigation lists are perfect for weblogs. So don't say it's just markupbation or that we'll be stuck with XHTML 1.1 for quite a while.

The HTML Working Group has released the first public Working Draft of XHTML 2.0. XHTML 2.0 is a relative of the Web's familiar publishing languages, HTML 4 and XHTML 1.0 and 1.1, and is not intended to be backward compatible with them. The draft contains the XHTML 2.0 markup language in modules for creating rich, portable Web-based applications. [Archive of W3C News in 2002]

A few new things I noticed: The hypertext and event attribute groups are part of the common attribute group. This means that most elements can be links, and can fire events. Very cool new text elements: <h> and <section> instead of the <hn> elements and <line> instead of <br>. <q> becomes <quote>. New list elements: <nl> and <name> for navigation lists (ie. menus). XFrames is not yet published, but referred to in this standard.

For all those Radio Userland bloggers who want to have links to the previous and next page in their archives: Dixiblog has been so very kind to provide a tutorial explaining how to do that. And she's used my macros, for which I was too lazy to provide a proper explanation.

But what's up with the new #1 Dave? Methinks there's a kink in the algorithm somewhere. [dive into mark/August 1, 2002]

Try this search. This Dave created a multi router traffic grapher. And he made sure to link to his homepage using his name, on every page the tool generated. Thats 10,000 links. Sure, Google knows of more than 20,000 links to scripting.com, but the links apparently say "Scripting News" more often than "Dave Winer".

The Web Ontology Working Group has released three first Working Drafts. The Feature Synopsis, Abstract Syntax and Language Reference describe the OWL Web Ontology Language 1.0 and its subset OWL Lite. Automated tools can use common sets of terms called ontologies to power services such as more accurate Web search, intelligent software agents, and knowledge management. OWL is used to publish and share ontologies on the Web. [Archive of W3C News in 2002]