RE: Arch Doc: 18 Sep: abstract

Going off the deep end, Sandro, but the topic tempts 
the abstractor in me. :-)

If the term 'information space' is going to be used, 
it will need some formal or informal definition whose 
scope may only be the arch document itself.  The 
web architecture itself, is defined in terms of the 
systems.  One can say that the web space is a product 
of the use of these systems.  One can say that use 
of the these systems creates the space by mapping names 
to addresses and that any *time* a name is mapped 
to an address, and information space is created.  There 
is no distinction between a resource as a provider and 
as information.  Information 'on the web' is different 
from 'information space'.  It is in it's own space 
whose dimensions does not concern the web as they are 
always in local space and subject to local measures.

This is not dissimilar to creating a coordinate space by 
declaring an origin.  The abstraction of web space exists 
independently such that there can be many origins but 
there must be one world origin.  For the purpose of 
this architecture, the world origin is the concept 
of the web space, but any origin for any information 
space within it is declared by mapping a name to 
an address.  The web space is abstract, but spaces
created within it are real and are self-organizing. 
What is found within the space may be abstract, but 
is a different information than the existence of the 
information space.

That is too mystical for me too, but I am not submitting 
text to be included in the document, just trying to 
suggest that the operation of declaration creates the 
space and avoiding the issues of measures and dimensions 
within the space (thus ducking out on scale relativity 
and the hobgoblins of uncertainty given probabilistic 
estimators).

len

Received on Wednesday, 24 September 2003 13:39:19 UTC