W3C home > Mailing lists > Public > public-awwsw@w3.org > December 2010

Re: Looking for examples of non-REST information resources

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Sat, 04 Dec 2010 12:08:02 +0000
To: Jonathan Rees <jar@creativecommons.org>
Cc: AWWSW TF <public-awwsw@w3.org>
Message-ID: <f5bvd39g2ql.fsf@calexico.inf.ed.ac.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

OK, I'll bite -- why does the second of these _not_ "fit the REST mould"?

  - has a current state consisting of "abstract information"
     Yup -- "the next random integer, given the current seed/state, as
             generated by the [xxx] algorithm and parameterised per
             the request URI"
  - the state may or may not change through time
     Yup -- as determined by the algorithm used
  - the state can be "represented" by "representations" (bit strings +
    metadata) synthesized by a server
     Yup, evidently
  - the state might be updated by PUT and POST, or by some other process
     Nope

Or, for that matter, the first -- why is

   "A topic page from Wikipedia, selected by [plug in the above or
   whatever is an accurate description of the randomisation involved]"

any _less_ a REST-mould-appropriate resource definition than "A
collection of photos and snippets comprising a view of the current UK
national and international news as determined by the editorial board
of the Guardian newspapers" is?

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFM+i8mkjnJixAXWBoRAl+AAKCDDhku+T1J7LzBLihVO1+usboNuACfcy9x
Nrpj1LoOn8lfSzBaZlX0Loc=
=eHFl
-----END PGP SIGNATURE-----
Received on Saturday, 4 December 2010 12:08:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 4 December 2010 12:08:43 GMT