Paul, > Why not just POST some kind of RDF document (or JSON-LD) that describes > what is you want and in what format, or if you really have to use GET,
Interesting thought. So what I would POST is essentially the profile/shape I want the data to conform to. Nonetheless my view of linked data is that it's using GET all the time, so I'd probably stick to that and instead serve my profile/shape under an http URI and only reference it from the GET request instead of POSTing it. > stuff it > in a GET field and hope it's not too big? What exactly do you mean with "a GET field"; is that the same thing as an http header? Best, Lars
