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

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

From: Story Henry <henry.story@bblfish.net>
Date: Sat, 10 Apr 2010 11:01:35 +0100
Cc: public-lod <public-lod@w3.org>, Vasiliy Faronov <vfaronov@gmail.com>, "giovanni.tummarello" <giovanni.tummarello@deri.org>
Message-Id: <5465B573-858C-4895-A66D-C339EDC62793@bblfish.net>
To: Leigh Dodds <leigh.dodds@talis.com>

On 7 Apr 2010, at 09:55, Leigh Dodds wrote:

> Linked Data can be consumed by a wide variety of different client
> applications and libraries. Not all of these will have ready access to
> an RDFS or OWL reasoner, e.g. Javascript libraries running within a
> browser or mobile devices with limited processing power. How can a
> publisher provide access to data which can be inferred from the
> triples they are publishing?

It's not that difficult really to add basic reasoning to your data. Using SPARQL
you can easily write out the most common rules.  http://spinrdf.org/

My guess is that small devices will have more problems parsing and downloading 
large files than reasoning.

I think more important is to get applications to use data. Then it will 
soon become clear as these applications grow, what data is useful to
place at a location. Just as the web browser helped simpify choices of what needed
to be published, so something like interacting foaf+ssl endpoints will end up
making clear what it is best to publish, and what is best left for inferencing.

So I'd say write apps that are viral and that consume the data. Then it
will be clear what to publish, and also what reasoning is useful.

Received on Saturday, 10 April 2010 10:02:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:16:05 UTC