This is a draft weblog post that I’m writing & editing out in the open. It started as an email thread with two designers, Luke Wroblewski and Jamie Hoover.
Luke kicked things off:
In Semantic Typography: Bridging the XHTML gap, Mark Boulton explains how to turn a visual design into a semantically marked-up document by taking a real-world example and breaking it down into structural elements. Mark’s article is a good introduction to semantics and document structure for anyone who hasn’t already started thinking structurally when marking up documents.
For some reason, the whole concept of document structure and actually using structural elements like headings and lists seems alien to most content authors I have met. And if authors aren’t semantically structuring documents in their word processors, they sure won’t do it before publishing their documents on the web.
I’ve been thinking a bit about why most people don’t structure their word processing documents properly, and I’m not sure why that feature is so underused. It could be a usability problem with word processors though – it’s often less obvious how to use styles properly than how to change the font and text size.
Here was my response:
I’ve been thinking a bit about why most people don’t structure their word processing documents properly, and I’m not sure why that feature is so underused.
Luke, I think it’s because many people think of structure and semantics as a means, rather than an end. Also, most word processing tools do a poor job exposing the
benefits of structure.
Apple’s Pages product is an
exception as its based around predefined (although
mailable) document structures. Office 12, with it’s new
gallery features may also increase
adopting of visual templates with underlying structure.
Structure can enable findability, a consistent visual look, and the organization of complex ideas. I think the key is developing more tools (
particularly in the web space) that help make the structure
visible and an
inherent aspect of
manipulating the
information.
Outliners for example add value because they
encourage users to manipulate the structure of
their data. We need to do a better job
evangelizing shared
semantic structures (eg1 eg2) which are tied to a
consistent visual look,
whether that’s ratings and reviews or
consistent css templates. The
consistency in visual and semantic
structure will help with
findabilty and recognition.
Here are some related initiatives to bring improved structure and shared semantics to the web.
1. W3C forms ‘Web Application Formats Working Group’
Specification of a declarative format for applications and user interfaces.
this deliverable should be based on an existing application/UI format, such as Mozilla’s XUL, Microsoft’s XAML, Macromedia’s MXML or Laszlo Systems’ LZX, provided the owners of the format are willing to contribute. The format should allow embedded program code. This format, combined with the deliverables below and existing technologies including XHTML, CSS, XForms, SVG and SMIL, should provide a strong basis for rich client application development.
2. What WG: Web Hypertext Application Technology
It is a loose unofficial collaboration of Web browser manufacturers and interested parties who wish to develop new technologies designed to allow authors to write and deploy Applications over the World Wide Web.
Here’s a review of a some of the goings on in this space:
http://www.xml.com/pub/a/2005/06/01/deviant.html?page=2
By the way, I discovered there’s another Micah out there who works in the web space. And he’s into microformats and XML. And he works on Forms.. And he works at Yahoo. Funny.
Later I added this post script:
Apple’s Pages product is an execption as its based around predefined (although mailable) document structures. Office 12, with it’s new gallery features may also increase adopting of visual templates with underlying structure.
One more thought… The fact that Pages is based around “predefined document structures” is important, but stated backwards. What matters is that it’s based around an end user goal (eg. creating a newsletter) and it helps writers get their formatting to the “basically done, just tweaking” stage as quickly as possible. Plus the visual structure give hints as to the best type of content (eg. length guidance, pull quotes, etc).