W3C home > Mailing lists > Public > public-lod@w3.org > April 2010

Re: [Patterns] Materialize Inferences (was Re: Triple materialization at publisher level)

From: Giovanni Tummarello <giovanni.tummarello@deri.org>
Date: Wed, 7 Apr 2010 13:06:04 +0200
Message-ID: <j2o210271541004070406j85065a9coe9aed498b70280dd@mail.gmail.com>
To: Vasiliy Faronov <vfaronov@gmail.com>
Cc: Leigh Dodds <leigh.dodds@talis.com>, public-lod <public-lod@w3.org>
The problem is not the standard but its the process.

a webmaster should dump the data in a owl or so reasoner (or rdfs
whatever) , then pick the outcoming triples and basically hand write
those extra classes in the nice HTML template.. mmm :-)

many extra triples (subject to change if ontologies change or better
reasoning happens or new data etc) + serialization not fully perfomred
automatically would seem an irrealistic



On Wed, Apr 7, 2010 at 12:38 PM, Vasiliy Faronov <vfaronov@gmail.com> wrote:
> Giovanni Tummarello wrote:
>> In this casematerialization is likely not going to happen much (you
>> wouldnt want to materialize inside something visible for the end user
>> etc).
>
> Why not? RDFa has easy support for the most common case of
> materialization, which is subclass and subproperty inference: you just
> write all the classes and properties separated by spaces. Like this:
>
>        <div about="#me" typeof="foaf:Person dcterms:Agent">
>                <h1 property="foaf:name rdfs:label">John Doe</h1>
>        </div>
>
> Drupal 7 does this for its SIOC export (at least that used to be shown
> on their demo site[1] which is now empty for whatever reason).
>
> [1] http://drupalrdf.openspring.net/
>
> --
> Vasiliy Faronov
>
>
Received on Wednesday, 7 April 2010 11:06:37 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:26 UTC