On 03/02/12 00:32, Martynas Jusevicius wrote:
If I get you right and you mean following redirects, you can toggle
them in ClientConfig
http://jersey.java.net/nonav/apidocs/1.11/jersey/com/sun/jersey/api/client/config/ClientConfig.html#PROPERTY_FOLLOW_REDIRECTS
Here's a good introduction to the Jersey Client API:
http://jersey.java.net/nonav/documentation/latest/client-api.html#d4e546
In this section they're pretty much talking about the same concepts as
RDF - i.e. the Uniform RESTful Interface :)
Martynas
By being able to stop automatic redirection following, you can build a
303 compliant client. But it does mean that the RDF-aware code needs
follwo the 303 so that it knows where the redirection ended up so it can
set the base URI correctly.
For my hacked up reader, that at least manes adding a base URI to a
types stream so the code can set it when calling the parser.
(I said 303 is way too complicated...)
Hmm - also, what about the #frag pattern for IR/NIR?
Dublin Core uses this pattern and it has the advantage that you end up
getting the whole vocabulary, then you can look up each #frag locally.
The downside is that you end up getting the whole vocabulary even if you
want one term. Also, the act of accessing gives you back a model you
then need to look inside for the relevant triples rather than a single
model of just the info you want.
There's no ideal answer here, which is why the "discussion" on IR/NIR
has been going on for years.
Andy
