Re: Harvesting from Roy's paper

Jonathan Rees wrote:
> Blog post including this material:
> http://odontomachus.wordpress.com/2011/03/07/are-you-confused-yet-about-the-word-representation/

:) the last one made me chuckle a bit!

definitions I that "sit right" with me:

[
Niklaus Wirth.
Program Development by Stepwise Refinement.
Communications of the ACM, Vol. 14, No. 4, April 1971, pp. 221-227.

In order to refine these instructions and predicates further in the 
direction of instructions and predicates available in common programming 
languages, it becomes necessary to express them in terms of data 
representable in those languages. A decision on how to represent the 
relevant facts in terms of data can therefore no longer be postponed.
]

[
Tim Berners-Lee. Generic Resources. Web page, 1996-2009.

A resource may be generic in that as a concept it is well specified but 
not so specifically specified that it can only be represented by a 
single bit stream.
]

[
RFC 1945, IETF, May 1996.

A feature of HTTP is the typing of data representation, allowing systems 
to be built independently of the data being transferred.
]

[
RFC 2616, IETF, June 1999.

A feature of HTTP is the typing and negotiation of data representation, 
allowing systems to be built independently of the data being transferred.

Resources may be available in multiple representations (e.g. multiple 
languages, data formats, size, and resolutions).

representation [definition from glossary]:
An entity included with a response that is subject to content negotiation.
]

[
Tim Berners-Lee.
“The range of the HTTP dereference function.”
Email to www-tag list, March 2002.

HTTP is a protocol which provides, for the client, a mapping (the http 
URI dereference function) from URI starting with “http:” and not 
containing a “#” to a representation of a document. The document is the 
abstract thing and the representation is bits.
]

Received on Monday, 7 March 2011 14:32:54 UTC