Hmm I'd strongly contest a definition list. Maybe nested UL's would be better... but Item 1 cannot be sensibly/reasonably _defined_ as "Add", or "Edit", or "Delete".
On 1/27/06, Paul Novitski <[EMAIL PROTECTED]> wrote: > Andreas, > > I could argue either list or table, but I'd be inclined to make it a > list. I see the three editing functions being part of each list item: > > <ul> > <li> > <dl> > <dt>Item 1</dt> > <dd><a href="?add=123">Add</a></dd> > <dd><a href="?edit=123">Edit</a></dd> > <dd><a href="?delete=123">Delete</a></dd> > </dl> > </li> > ... > </ul> > > This might seem taggy, but doesn't take a whole lot more markup than > a table would. Nesting the ULs will also maintain the semantic > structure of the complex list. > > Paul ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
