- From: Erik Wilde <dret@berkeley.edu>
- Date: Fri, 07 Jun 2013 09:54:07 -0700
- To: Elli Schwarz <eliezer_schwarz@yahoo.com>
- CC: Arnaud Le Hors <lehors@us.ibm.com>, "public-ldp@w3.org" <public-ldp@w3.org>
hello elli.
On 2013-06-07 9:15 , Elli Schwarz wrote:
> What do you expect to happen currently if a user tries to access the URL
> <http://example.org/netWorth/nw1/assetContainer/?p=55> and page 2 is the
> last page? Do you expect an empty page to be returned? Or do you also
> expect this response:
why would you ever request (or even know about) this URI? if page 55
exists it should be linked from page 54 via a "next" link (RFC 5005
standardizes this way of linking paged web resources), and then you can
simply follow this link, *if it's there*. keep in mind that if the
"next" link is there, it could say ...?p=55 or ...?page=55 or
...?page=fiftyfive; what the page resources are using as URIs is an
implementation choice (URI hacking is an anti-pattern). what matters
from the web perspective is that resources are linked, so that clients
can follow those links, and if your client sticks to this principle,
then you don't have a problem at all.
cheers,
dret.
--
erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 |
| UC Berkeley - School of Information (ISchool) |
| http://dret.net/netdret http://twitter.com/dret |
Received on Friday, 7 June 2013 16:54:35 UTC