The approach makes sense, but I've just hit what appears to be a bug in how the serializer is chosen -
curl --user admin:admin -H "Content-Type: text/turtle" http://localhost:8080/user-management/users/anonymous returns RDF/JSON instead of Turtle this is calling against: @GET @Path("users/{username}") public TripleCollection getUserContext(@PathParam("username") String userName) throws UnsupportedEncodingException { return getUser(userName).getNodeContext(); } I'm not 100% sure, my build isn't totally fresh from svn (I've just updated, waiting for the install as I type...), but it's easy enough to check with the curl line above. Where is the magic that turns that TripleCollection into a Response? (This isn't a blocker for me, I can put in temporary forced-turtle methods for now). Cheers, Danny. -- http://dannyayers.com http://webbeep.it - text to tones and back again
