Indentification in Web Arch.
XML.com: Reviewing Web Architecture: Identification [Jan. 07, 2004]
The first point the AWWW makes is what it calls a constraint, that is, that one identifies resources in the Web by providing a URI for the resource. The motivation here is that, in the absence of a URI, user agents are unable to do anything with (interaction -- AWWW's second principle) representations (AWWW's third principle) of the state of a resource. The necessary, but not sufficient, condition of a user agent interacting with a resource by means of the Web is for that resource to have a URI. The user agent is able to retrieve a representation of the state of that resource by means of the scheme encoded in the URI -- a detail which will concern us in the next two columns.
The first point the AWWW makes is what it calls a constraint, that is, that one identifies resources in the Web by providing a URI for the resource. The motivation here is that, in the absence of a URI, user agents are unable to do anything with (interaction -- AWWW's second principle) representations (AWWW's third principle) of the state of a resource. The necessary, but not sufficient, condition of a user agent interacting with a resource by means of the Web is for that resource to have a URI. The user agent is able to retrieve a representation of the state of that resource by means of the scheme encoded in the URI -- a detail which will concern us in the next two columns.