Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Stephan's advice is in general conformance with <a href="http://www.w3.org/TR/rdfa-lite/" rel="nofollow">RDF Lite 1.1</a>, which does not include <code>@rel</code> or <code>@about</code> for precisely these reasons.</p> <p>Another good rule of thumb is to not try to include markup of more than one entity on a given element, which was often an example of specifying an images license.</p> <p><code>@property</code> and <code>@rel</code> are very similar to each others, but served different purposes in RDFa 1.0, but this was confusing, even for experts. (Formerly, <code>@rel</code> was used for specifying objects which are other nodes, and <code>@property</code> was used for specifying literal values. While there are some remaining differences, but sticking to non-clever markup, you can do everything with <code>@property</code> that you could do with <code>@rel</code>.</p> <p>Similarly, <code>@about</code> can be avoided to just use <code>@resource</code>. The difference is that <code>@about</code> sets the current subject and <code>@resource</code> the current object, but for child nodes the <code>parent object</code> (taken from the parent's <code>current object</code> becomes the <code>current subject</code>. There were another minor differences concerning the presence of <code>@typeof</code>, but if you only use <code>@resource</code>, it pretty much does what you want.</p> <p>To summarize the best practices from RDFa Lite 1.1 you can also check out the <a href="http://www.w3.org/TR/xhtml-rdfa-primer/" rel="nofollow">RDFa 1.1 Primer</a>:</p> <ul> <li>stick to <code>@vocab</code>, <code>@prefix</code>, <code>@property</code>, <code>@resource</code>, and <code>@typeof</code></li> <li>avoid making more than one statement in a given element</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POIn RDFa, difference between property="" & rel="", and resource="" & about=""?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USGregg Kellogg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the info but: "While there are some remaining differences..." & "There were another minor differences..."; could you please elaborate?
      singulars
      1. PO
      1. USSketch R
    2. COMain difference is the behavior of \@property with or without \@rel. If there is no \@rel, \@property can be used for a resource or a literal. In 1.0 \@property only works on a literal. There are also differences if \@about is present and @typeof, mainly to meet developer expectations. Some of the differences are recorded [in the spec](http://www.w3.org/TR/rdfa-syntax/#major-differences-with-rdfa-syntax-1.0). The main advice is to avoid mixing markup on a single element. See [RDFa Lite](http://www.w3.org/TR/rdfa-lite/) for suggested patterns.
      singulars
      1. PO
      1. USGregg Kellogg
 

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