The URI (we are talking about URIs here, not URLs, careful)
Hmm, but if you want to make the linking from outside also consistent, why inventing another scheme?
True. Consistency is one thing, but remember that is entirely possible that several URLs can point to the same object identified by even a different URI!
The URI can be used as a URL, but the "meaning" of this use is not so explicit as it seems at first sight. (read below for more)
...
I only would like to have date metadata before clicking on a link.
sorry, I'm not sure I follow you here.
How old is the page to be accessed? Information about Cocoon older than 3 years might not be of any interest for me. That's similar to the news samples I gave at the beginning.
But also note that we are still talking about URIs not URLs. Using the LO URI as a URL might not be the only way to access the object.
Maybe the date to version mapping is one thing, that can be handled when mapping URLs to URIs. So as said above the last version of a day is *the* version of that day. Then we have versioned URIs and dated URLs.
Could it be, that you already came to the same conclusion in other parts of this thread? I appologize for that. Sometimes it takes a bit longer ...
I don't remember if I made it explicit already, but I'm glad you came to the same conclusion. Yes, the "date -> version" can be part of the URL->URI translation procedure.
So, asking for
http://host/path/id/date
could yield the last revision for that particular date (if any), or could give a list of revisions that were done on that date.
but at this point, we had to differentiate between version and date... so, another option, following subversion's approach is to use something like
http://host/path/id!date=20031015
or
http://host/path/id!version=343
or even
http://host/path/id!branch='cocoon-2.1'
or, even wilder, following Kimbro Stalken's (of Xindice fame) approach at Syncato (http://www.syncato.org/)
http://host/path/!branch='cocoon-2.1'?// author[contains(@name,'Stefano')]
that would yield a list of objects in the "cocoon-2.1" branch that include at least one element named <author> that contain the string 'stefano' in their name attribute.
This example shows pretty evidently how URL->URI traslation is not such an automatic and easy thing to describe and to design.
Also shows that using URI as URLs is not transparent as well and requires some implicit contract.
-- Stefano.
After these examples the difference between URI and URL is /clear as daylight/.
Thanks,
Joerg
