ISSUE-33

hello all.

sorry for holding things up a bit about ISSUE-33. i guess i am still
wondering what ISSUE-33 is all about. as we have agreed, LDP is about an
RDF service surface, so what we serve as resources apart from LDP protocol
data can be anything. if we want to encourage people to implement servers
that can handle large amounts of data (i.e., large resources), we should
look at HTTP range requests and HTTP chunked encoding, and see if there is
anything that cannot be accomplished with these mechanisms. if there is a
specific RDF paging a server wants to implement, then i guess for LDP it
only matters for containers when listing members. for members themselves
it is not quite clear to me how pages would map to a proper resource
model, if we're splitting up triples into "triple pages" (that's what i
understood the non-container paging would be about). but i am still
suspecting that i am missing something here, so like eric suggested, a use
case and some explanation would be greatly appreciated.

thanks a lot and cheers,

dret.

Received on Monday, 11 February 2013 16:09:48 UTC