Perhaps you're right that an ordered list is not the right list to choose, as it will be chunked and split across pages, however the scenario is such that:
* a collection of images may contain thousands of items * the collection is the highest level in the heirachy and so needs a "finding aid" in some way to access items within the collection and to describe relationships that may not be possible at lower levels (not worth going into, needless to say that there are complex relationships between items particularly in manuscript collections) * the way that's been selected is to show a thumbnail icon and the title or some descriptive metadata (similar to search results pages on the site: http://www.musicaustralia.org) * list of items/images (including file sizes) would be too long that our usability tests (and commonsense) shows that users are just unable to scroll through thousands of items - hence chunking is necesssary * while there is a fairly indepth persistent identification naming scheme for image files, again it harks back to the relationships that can't be expressed via the naming scheme and the need to build these content list pages as a way for users to view large collections perhaps I'll roll this page back to XHTML transitional so start can be used, but am hesitant to begin by knowingly working with things that aren't "the way forward" so to speak. Thanks Somaya -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Tan Sent: Thursday, 24 November 2005 12:29 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] starting ordered lists from a number other than 1 Chris Kennon <[EMAIL PROTECTED]> wrote: > Can someone explain why this incredibly useful attribute: >>> <ol> >>> <li value=40></li> > is deprecated, or is it? It is depreciated ( http://www.w3.org/TR/html401/struct/lists.html) although it is not obselete therefore will still be supported for backward compatibility. One possible reason could be that it completely destroys the semantics of an ordered list by allowing it to be broken up. I'm curious about the function of the list - does the numbering describe the images to make them meaningful in some way? An ordered list spread over multiple URIs strikes me as wrong as the list portion referenced by an individual URI may have less meaning when dislocated from other portions of the list. Something like spreading a library index over different rooms[files] in the building[domain]. Is there a reason apart from file size / download time that this list should be spread over multiple pages? I assume the archive is huge but if its just a contents list page then wouldn't it be hypertext with anchors for blocks and meaningful URIs for each image? I assume the library has some kind of tagging system or category system to classify images so access to groups of images themselves is achieved through that? Jon Tan www.gr0w.com [EMAIL PROTECTED] ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ****************************************************** ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
