Contexts in which this element may be
1) I think you should stick with the article element, as
2) If you're wondering if it's allowed to include article elements inside a li element, just feed it to the validator. As you can see, it is permitted to do so. Moreover, as the Working Draft says:
3) I wouldn't use nav elements for those categories, as those links are not part of the main navigation of the page:
4) Do not use the details and/or summary elements, as those are used as part of interactive elements and are not intended for plain documents.
@Jaffa: I don't agree: comments are usually a kind of waterfall of posts, sorted by date by nature (if I'm clear enough, my vocabulary is not that great at the moment); a search result list is a list in a specific order, with the best result (#1) at the top of the list. Also see the OP's requirement to order them by increasing number.
As a list of search results actually is a list, I think this is the appropriate element to use; however, as it seems to me that the order is important (I expect the best matching result to be on top of the list), I think that you should use an ordered list (ol) instead:
EDIT: Whoops, I just realized you already use an ol (due to my fatique, I thought you used an ul). I'll leave my update as is; after all, it might be useful to someone.
Is there any semantic benefit to the <ol> in this situation? Articles are scoped to their parent sectioning element so they're already grouped. Are they assumed to be ordered already, like <p>? If so, the only thing the <ol> offers is the 'start' attribute for paging.
It's unfortunate that <ol> doesn't allow some other tags to be children of it, like <article>. It could then be understood as an ordered list of articles. <li> in this case seems as arbitrary as the pervasive <div> tags HTML5 is supposed to move us away from.
Thank you for those clueful opinions! From that point of view, <article> is a good choice for the summary. You are right about <nav> as well. I know, however, that <li> may contain more or less any tags according to the doctype. My question is more like if it is a good way of using lists.
The ol element represents a list of
items, where the items have been
intentionally ordered, such that
changing the order would change the
meaning of the document. [source]
The ul element represents a list of
items, where the order of the items is
not important that is, where
changing the order would not
materially change the meaning of the
UPDATE: Regarding if it's a good idea to use an (un)ordered list to present search results:
Using CSS you can simply hide the numbers.
You merely have a list of separate documents, so I think this is fully appropriate. The same is true for the front page of a blog, containing several posts with titles and outlines, each in a separate article element. Besides, if you intend to quote a few sentences of the articles (instead of providing summaries), you could even use blockquote elements, like in the example of a forum post showing the original posts a user is replying to.
[t]he article element represents a
self-contained composition in a
document, page, application, or site
and that is intended to be
independently distributable or
only sections that consist of major navigation blocks are appropriate for the nav element. In particular, it is common for footers to have a short list of links to various pages of a site, such as the terms of service, the home page, and a copyright page. The footer element alone is sufficient for such cases, without a nav element. [source]
whatwg.org/specs/web-apps/current-work/multipage/ One of the examples is comments on a blog post, since the ordering of comments could be essential, we could assume that <article>s are already ordered.