search

SDShare / Specification

SDShare - Protocol for the syndication and synchronisation of RDF
Other
10 stars 1 forks source link

All feeds should allow RFC 5005 (Pagination) #50

Closed heuer closed 12 years ago

heuer commented 12 years ago

Limit RFC 5005 to the fragments feed is narrow-minded, a client should support pagination for all feeds except for the collection feed which contains two entries only.

larsga commented 12 years ago

Well, it is true that it could be useful for the overview and snapshot feeds as well. Graham?

gra-moore commented 12 years ago

YAGNI.

heuer commented 12 years ago

IMO it would be useful for the overview feed.

... and if it's allowed for the fragments feed and overview feed, it would be strange if it's explicitly forbidden for the snapshots feed.

gra-moore commented 12 years ago

Overview feed? This lists collections and is only ever really used by humans to find the link to the collection they are going to configure a client with. [An aside if we had a collection id in the overview feed, then a client could be given this id as the thing to find and process. I know there is the atom id and maybe it could be discussed as best practice that these ids could be used to connect clients to specific feeds As opposed to hard coding the collection url in there.] As a human I would rather get a single atom page with 1000 items in it so I could ctrl+f to search in the text for what I want. But then again, I dont see servers exposing a 1000 sources very often.

heuer commented 12 years ago

Overview feed? This lists collections and is only ever really used by humans to find the link to the collection they are going to configure a client with.

I thought I could give a client a SDShare endpoint (the overview feed) and the client could report available graphs (that's why I proposed the graph URI extension in issue #49). So, aside from SDShare's feature to update graphs via fragments I thought that a SDShare server is a repository of graphs. And a server may host a lot of graphs or decide that only the most important 10 graphs a listed (initially) within the overview feed; or a service aggregates overview feeds from different servers etc.

And if clients MUST support pagination for the fragments feed anyway, it wouldn't much work to support it everywhere.

Anyway, this minor proposal is not worth to waste more time, so I'll close it.