>From the proposal:
<table typeof="Painting" vocab="http://schema.org/">
<thead>
<tr>
<th property="image">Image</th>
<th property="name">Title</th>
<th property="dateCreated">Year</th>
<th>Technique</th>
<th>Dimensions</th>
<th property="contentLocation">Gallery</th>
</tr>
</thead>
<tbody>...</tbody>
</table>
It should be noted that parsers which are not aware of this table extension
would generate this information:
<>
rdf:type schema:Painting;
schema:image "Image";
schema:name "Title";
schema:dateCreated "Year";
schema:contentLocation "Gallery" .
How do you plane to cope with this situation? Leave it be? Would it have
unintended consequences on some applications?
Steph.
On Tue, Aug 13, 2013 at 5:04 PM, Omar Benjelloun (عمر بنجلون) <
benjello@google.com> wrote:
> Hi,
>
> Many useful datasets on the Web take the form of tables. The goal of this
> proposal is to provide a simple, schema.org-friendly way to "look inside"
> these tables, and map their contents into triples.
>
> This is an early draft proposal developed at Google. We're seeking
> feedback from the community.
>
> The proposal is attached to this e-mail, and will be uploaded to the
> WebSchemas/SchemaDotOrgProposals page shortly.
>
> Thanks,
> -Omar
>
--
Steph.