18 Dec
2008
18 Dec
'08
1:03 p.m.
Vincent Massol wrote:
On Dec 18, 2008, at 11:39 AM, Fabio Mancinelli wrote:
+1, but it depends.
A resource is identified by the path, without query parameters. The
question is, is there only one resource, with multiple variants, or each
translation/version is a resource?
And we'd still need some path to get the list of versions.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Dear all,
I haven't seen any comment about the second proposal I did.
It basically "moves" some URI path elements to the parameter list.
These
elements are the ones that introduces a degree of variability wrt to
the
resource, namely language and version.
For example with a single URI:
/spaces/{space}/pages/{page}[?lang=l&version=v]
I can get the page at its latest version in the default language (no
query parameters) or, by combining the query parameters, any page at a
specific version in a given language.
I think it is worth thinking about it because, by following the
previous
example, the 8 URIs in the "pages" section could be reduced to 4.
Similarly for other resources where the "version element" basically
introduces a doubling of the resources to be exposed (e.g., as it
happens with objects and attachments).
WDYT?
I don't like it since I'm not sure this is very RESTful.