Hi Tomasz, Karol, I recall the Linked Data API allows to add a request parameter that contains the text content of a SPARQL WHERE clause that should be matched, sounds similar. With regards to coupling, is this an issue? If the API were able to publish some kind of summary of the classes and properties used, then a client would be able to make smart choices here without a priori knowledge. Regards, John On 20 Dec 2015, at 22:02, Tomasz Pluskiewicz <tomasz@t-code.pl> wrote: > The problem with that approach was that it introduced coupling, where the client required intimate knowledge about the data structures (used terms and the graph layout) > > Tom > > On Dec 20, 2015, at 20:49, "Karol Szczepański" <karol.szczepanski@gmail.com> wrote: > Very common in current rest API is a query param like > "fields=created,modified,...". > Something like this should be easy to model with IRI templates. > > Alternatively or additionally it might make sense to let the client specify > a shape. > > Just to share my experience within this area, in one of our projects we've > approached that scenario with HTTP Expect Header where we've used SPARQL > like property paths to define which properties/graphs to > return/explode/block. > Only issue with that is that XMLHttpRequest Level 1 spec disallows that > header to be sent and we had to send a Prefer header instead (RFC 7240). > > Best > > Karol > > > > > > > >
Received on Monday, 21 December 2015 08:05:27 UTC