table.queryresult { border: 1px solid black; width: 100%; padding: 5px; border-collapse: collapse;}

	table.queryresult th { border-bottom: 1px solid black; border-right: 1px solid black; padding: 5px;}

	table.queryresult td { border-right: 1px solid black; padding: 5px;}

	<li><a href="#morecompany">5. More Company Information</a></li>	

  <dt><tt>http://www.example.com/acme# ... acme:</tt></dt>

  <dt><tt>http://purl.org/goodrelations/v1# ... gr:</tt></dt>

 @prefix acme: <http://www.example.com/acme#> .

 acme:corporation a gr:BusinessEntity ;

  <dt><tt>http://www.example.com/tools# ... tools:</tt></dt>

 @prefix acme: <http://www.example.com/acme#> .

 acme:corporation a gr:BusinessEntity ;

                  rdfs:seeAlso <http://www.example.com/acme/> ;

                  gr:legalName "ACME Corp." .

 acme:sf0815 a tools:AllPurposeUtility, gr:ActualProductOrServiceInstance ;

             dcterms:title "Stanley Fubar" .

 acme:sh4711 a tools:Hammer, gr:ActualProductOrServiceInstance ;

             dcterms:title "Binford 2000 hammer" .

 acme:ts0007 a tools:ScrewDriver, gr:ActualProductOrServiceInstance ;

             dcterms:title "The Screwer" .

<p>

In line 6 of the RDFa snippet in Table 4 we state that <em>ACME Corp.</em> has something to offer, the <code>acme:sf0815-offering</code>, which is defined in detail in the lines 28-32. The offering consists of two major components: the price specification (<code>acme:sf0815-price</code>) and a type/quantity node (<code>acme:sf0815-taqn</code>). The price specification is built around the existing cell content in lines 16-19 and the type/quantity node is represented in a hidden area (lines 23-27).  

</p>	

 @prefix acme: <http://www.example.com/acme#> .

 <strong>acme:corporation</strong> a gr:BusinessEntity ;

                  rdfs:seeAlso <http://www.example.com/acme/> ;

                  gr:legalName "ACME Corp." ;

                  <strong>gr:offers acme:sf0815-offering</strong> .

 <strong>acme:sf0815-offering</strong> a gr:Offering ;

                      gr:hasBusinessFunction gr:Sell ;

                      gr:hasPriceSpecification acme:sf0815-price ;

                      <strong>gr:includesObject acme:sf0815-taqn</strong> .

 acme:sf0815-price a gr:UnitPriceSpecification ;

                   gr:hasCurrency "EUR"^^xsd:string ;

                   gr:hasCurrencyValue "40"^^xsd:float ;

                   gr:hasUnitOfMeasurement "C62" .

 <strong>acme:sf0815-taqn</strong> a gr:TypeAndQuantityNode ;

                  gr:amountOfThisGood "1.0"^^xsd:float ;

                  gr:hasUnitOfMeasurement "C62" ;

                  <strong>gr:typeOfGood acme:sf0815</strong> .

 <strong>acme:sf0815</strong> a tools:AllPurposeUtility, gr:ActualProductOrServiceInstance ;

             dcterms:title "Stanley Fubar" .

A visual representation of the resulting RDF graph from the RDFa snippet in Table 4. is shown in Fig. 3, below. We note that the key path for the connection between the <em>company</em> and the <em>product</em>, that is <code>acme:corporation - gr:offers -> acme:sf0815-offering</code>, 

<code>acme:sf0815-offering - gr:includesObject -> acme:sf0815-taqn</code>, and finally <code>acme:sf0815-taqn - gr:typeOfGood -> acme:sf0815</code>

is highlighted for better understanding.

<p>

With the data we have so far, we are now able to perform a query such as shown below, allowing to retrieve pricing information about a certain tool along with the providing party (a company):

</p>

<pre class="turtlecode">

PREFIX gr: <http://purl.org/goodrelations/v1#>

PREFIX tools: <http://www.example.com/tools#>

PREFIX dcterms: <http://purl.org/dc/terms/>

SELECT ?label ?curval ?cur ?provname

WHERE { 

 ?offering a gr:Offering ;

             gr:includesObject ?object ;   

             gr:hasPriceSpecification ?pricespec .

 ?object gr:typeOfGood ?item .

 ?item a tools:Hammer ; 

       dcterms:title ?label .

 ?pricespec gr:hasCurrency ?cur ;   

            gr:hasCurrencyValue ?curval .

 ?provider gr:offers ?offering ;

           gr:legalName ?provname .

}

</pre>

<p>

When the above shown query is <a href="http://tr.im/iBRX">executed</a> in a SPARQL engine such as <a href="http://sparql.org/sparql">http://sparql.org/sparql</a> with <a href="acme.html">acme.html</a> as the input RDF document, the result is as follows (we note that, as most SPARQL engines nowadays do not support RDFa directly, one has to convert the input document first to RDF/XML, for example using the <a href="http://www.w3.org/2007/08/pyRdfa/">RDFa Distiller</a>):

</p>

<table class="queryresult">

	<tr>

		<th>label</th><th>curval</th><th>cur</th><th>provname</th>

	</tr>

	<tr>

		<td> "Binford 2000 hammer" </td><td> "20"^^<http://www.w3.org/2001/XMLSchema#float> </td><td> "EUR"^^<http://www.w3.org/2001/XMLSchema#string> </td><td>"ACME Corp." </td>

	</tr>

</table>

<!--    MORE COMPANY DETAILS    -->

<h2 id="morecompany">5. More Company Information</h2>

<p>

Let us now step back a bit and return to something simple though very useful in everyday commercial but also private life. We assume wants to express some more detailed information about how to contact a company or who are the people behind it. As usual we suggest to consult the stand-alone example <a href="acme.html">acme.html</a> to see the entire code in action.

</p>

<table class="example">

<caption><span>Table 5.:</span>  Some <em>company</em> contact details.</caption>

<tbody>

<tr><th>Human</th><th>Machine</th></tr>	

<tr>

	<td>

	</td>

	<td>

<pre class="rdfacode">

</pre>

</td>

</tr>

</tbody>

</table>