On Mon, Jul 6, 2009 at 8:38 PM, Moore, Jonathan (CIM) <jonathan_moore@...> wrote:
>
> Sounds like the fingerprint, portrait, and scan could all be subordinate resources. Maybe http://example.com/person/123 returns an HTML or XML document with several links in it, like:
Yes, you should certainly be able to enumerate the available resources but this gets me thinking about a server-side Accept: header (e.g. Offer:). Anyway I'm liking the idea of subordinate resources and it fits with the requirement to upload existing multi-file virtual machines.
> (excuse my not-exactly-Atom XML)...
>
> <entry>
> <id>http://example.com/person/123</id>
> <link rel="http://example.com/schemas/#portrait"
> href="http://example.com/person/123/portrait
> type="image/jpeg"/>
> <link rel="http://example.com/schemas/#fingerprint"
> href="http://example.com/person/123/fingerprint"
> type="image/jpeg"/>
> ...
> </entry>
Another way of achieving the same while eliminating the dependency on Atom & XML is to serve up the best representation available along with Link: headers (draft-nottingham-http-link-header). Given "best" often translates to "biggest" you can get just the links in advance using HEAD (which is also compatible with "simple" clients like wget/curl, thus lowering the barriers to entry).
Sam