- From: Peter Ansell <ansell.peter@gmail.com>
- Date: Tue, 30 Dec 2008 08:14:25 +1000
- To: "Aldo Bucchi" <aldo.bucchi@gmail.com>
- Cc: "public-lod@w3.org" <public-lod@w3.org>
2008/12/30 Aldo Bucchi <aldo.bucchi@gmail.com>: > > 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 . If you are expecting the value to always be directly integrated as a plain literal you either put it in or you don't. If you are willing to say that it doesn't have to be a literal you can make it "ex:dynamicUri1 <http://ex.com/dynamic1/a>" or some similar way to allow them to resolve that URI that if they recognise the predicate, but ignore it and hence ignore the computation otherwise. LD conventions don't say that properties always have to be directly attributed to their elements. Having the URI link to another RDF document, even for literals fits all the guidelines as far as I can see. Cheers, Peter
Received on Monday, 29 December 2008 22:15:12 UTC