- From: Andraz Tori <andraz@zemanta.com>
- Date: Tue, 30 Dec 2008 16:12:36 +0100
- To: public-lod@w3.org
On Tue, 2008-12-30 at 12:29 +0100, Georgi Kobilarov wrote:
> Hi Aldo,
>
> How dynamic is ex:dynamic1? Does the value change for every request?
> Can't you use caching? I'd say you should try to optimize your backend
> instead of breaking conventions. Think of pre-computing all
> rdf-documents and then serving static files, and updating them
> periodically for example.
This really isn't a useful suggestion for most of the cases of dynamic
content or content analysis. Especially when either intensive processing
needs to be done (NLP, etc) or when third party services have to be
called.
Approach from MusicBrainz is interesting where they basically provide a
way to express how deep structure should be returned by simply adding
another part (a number) to main url.
bye
andraz
> Best,
> Georgi
>
> --
> Georgi Kobilarov
> Freie Universität Berlin
> www.georgikobilarov.com
>
> > -----Original Message-----
> > From: public-lod-request@w3.org [mailto:public-lod-request@w3.org] On
> > Behalf Of Aldo Bucchi
> > Sent: Monday, December 29, 2008 4:51 PM
> > To: public-lod@w3.org
> > Subject: Granular dereferencing ( prop by prop ) using REST +
> > LinkedData; Ideas?
> >
> >
> > Hi All,
> >
> > I am in the process of LODing a dataset in which certain properties
> > are generated on the fly ( props derived from aggregate calculations
> > over the dataset, remote calls, etc ). I would like to let the clients
> > choose which of these expensive properties they need on demand and on
> > a granular level.
> >
> > For example, lets say I am interested in knowing more about resource
> > <http://ex.com/a>.
> > Per LD conventions, dereferencing http://ex.com/a ( via 303 ) returns
> >
> > <http://ex.com/a> a ex:Thing ;
> > rdfs:label "a sample dynamic resource";
> > ex:dynamic1 45567 .
> >
> > The problem is that the value for ex:dynamic1 is very expensive to
> > compute. Therefore, I would like to "partition" the document in such a
> > way that the client can ask for the property on a lazy, deferred
> > manner ( a second call in the future ).
> > The same is true for dynamic2, dynamic3, dynamic4, etc. All should be
> > retrievable independently and on demand.
> >
> > * I am aware that this can be achieved by extending SPARQL in some
> > toolkits. But I need LOD.
> > * I am also aware that most solutions require us to break URI
> > obscurity by stuffing the subject and predicate in the uri for a doc.
> > * Finally, seeAlso is too broad as it doesn't convey the information I
> > need.
> >
> > Anyone came up with a clean pattern for this?
> > Ideas?
> >
> > Something as simple as:
> > GET http://x.com/sp?s={subject}&p={predicate} ---> required RDF
> >
> > works for me... but... .
> > If possible, I would like to break conventions in a conventional
> manner
> > ;)
> >
> > Best,
> > A
> >
> > --
> > Aldo Bucchi
> > U N I V R Z
> > Office: +56 2 795 4532
> > Mobile:+56 9 7623 8653
> > skype:aldo.bucchi
> > http://www.univrz.com/
> > http://aldobucchi.com
> >
> > PRIVILEGED AND CONFIDENTIAL INFORMATION
> > This message is only for the use of the individual or entity to which
> > it is
> > addressed and may contain information that is privileged and
> > confidential. If
> > you are not the intended recipient, please do not distribute or copy
> > this
> > communication, by e-mail or otherwise. Instead, please notify us
> > immediately by
> > return e-mail.
> > INFORMACIÓN PRIVILEGIADA Y CONFIDENCIAL
> > Este mensaje está destinado sólo a la persona u organización al cual
> > está
> > dirigido y podría contener información privilegiada y confidencial. Si
> > usted no
> > es el destinatario, por favor no distribuya ni copie esta
> comunicación,
> > por
> > email o por otra vía. Por el contrario, por favor notifíquenos
> > inmediatamente
> > vía e-mail.
>
--
Andraz Tori, CTO
Zemanta Ltd, London, Ljubljana
www.zemanta.com
mail: andraz@zemanta.com
tel: +386 41 515 767
twitter: andraz, skype: minmax_test
Received on Tuesday, 30 December 2008 15:13:21 UTC