Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>1)</strong> I think you should stick with the <code>article</code> element, as </p> <blockquote> <p>[t]he <code>article</code> element represents a self-contained composition in a document, page, application, or site and that is intended to be independently distributable or reusable <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-article-element" rel="noreferrer">[source]</a></p> </blockquote> <p>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 <code>article</code> element. Besides, if you intend to quote a few sentences of the articles (instead of providing summaries), you could even use <code>blockquote</code> elements, like in <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html#the-blockquote-element" rel="noreferrer">the example of a forum post</a> showing the original posts a user is replying to.</p> <p><strong>2)</strong> If you're wondering if it's allowed to include <code>article</code> elements inside a <code>li</code> element, just feed it to the validator. As you can see, it is permitted to do so. Moreover, as the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-article-element" rel="noreferrer">Working Draft</a> says:</p> <blockquote> <p><strong>Contexts in which this element may be used:</strong></p> <p>Where <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/content-models.html#flow-content" rel="noreferrer">flow content</a> is expected.</p> </blockquote> <p><strong>3)</strong> I wouldn't use <code>nav</code> elements for those categories, as those links are not part of the main navigation of the page:</p> <blockquote> <p>only sections that consist of major navigation blocks are appropriate for the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-nav-element" rel="noreferrer"><code>nav</code></a> 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 <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-footer-element" rel="noreferrer"><code>footer</code></a> element alone is sufficient for such cases, without a <code>nav</code> element. <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-nav-element" rel="noreferrer">[source]</a></p> </blockquote> <p><strong>4)</strong> Do not use the <code>details</code> and/or <code>summary</code> elements, as those are used as part of <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-details-element" rel="noreferrer">interactive elements</a> and are not intended for plain documents.</p> <p><strong>UPDATE:</strong> Regarding if it's a good idea to use an (un)ordered list to present search results:</p> <blockquote> <p>The <code>ul</code> 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 document. <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html#the-ul-element" rel="noreferrer">[source]</a></p> </blockquote> <p>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 <em>is</em> important (I expect the best matching result to be on top of the list), I think that you should use an ordered list (<code>ol</code>) instead:</p> <blockquote> <p>The <code>ol</code> 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. <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html#the-ol-element" rel="noreferrer">[source]</a></p> </blockquote> <p>Using CSS you can simply hide the numbers.</p> <p><strong>EDIT:</strong> Whoops, I just realized you already use an <code>ol</code> (due to my fatique, I thought you used an <code>ul</code>). I'll leave my ‘update’ as is; after all, it might be useful to someone.</p>
    singulars
    1. This table or related slice is empty.
    1. POMarking up a search result list with HTML5 semantics
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMarcel Korpel
    1. USMarcel Korpel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMarking up a search result list with HTML5 semantics
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank 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.
      singulars
      1. PO
      1. USJohan
    2. COIs 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.
      singulars
      1. PO
      1. USJaffa The Cake
    3. COhttp://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-article-element 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.
      singulars
      1. PO
      1. USJaffa The Cake
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload