- From: Andreas Kuckartz <a.kuckartz@ping.de>
- Date: 2 Jul 2014 11:42:37 +0200
- To: "Markus Lanthaler" <markus.lanthaler@gmx.net>
- Cc: public-linked-data-fragments@w3.org
Markus Lanthaler: >> Extending the segmenting idea a bit: One single request from a client >> for the whole date range could lead to a reply from a server containing >> pointers to the segments. > > Hmm... so you are saying that the client asks the server "give me everything > within this range" and the server replies "if you want that, go here, here, > and there"? I'm not sure yet what to think about that. If the server gives > the client enough information to know where to go in the first place, this > seems a bit like overkill and if results grow too big they can always be > paginated. But perhaps you had something else in mind? No (not at this time ;-) >>> However, it is also the option that involves most work to implement: >>> - a way to describe features >>> - a way for clients to discover and use those features >> >> Working on 1) and full text search should be able to help illuminating >> what is necessary for 2). Both are major use cases and the use case I >> have in mind would regularly involve combining both. > > Could you please tell us a bit more about your use cases so that we have > something concrete to discuss? Use case: A user is interested in text documents which were published within a certain time interval / date range and which contain a string of text (or something similar to that string) or where meta data contains this string. In other words: the user interface would be a form consisting of three fields: one for the start date, one for the end date and one for a search string. Cheers, Andreas
Received on Wednesday, 2 July 2014 09:44:03 UTC