BTW:  isn't a path view also a vector view?  

The question is one of what forces cause an object to emerge at that
path-based location in a space and by that emergence, how does the space
around it self-organize (conform to a manifold)?  Higher order
mathematics are required to describe that because feedback implies
higher order systems.  That's why the http range issue is such a devil.
The URI is used simultaneously in lower (resource locators) and higher
dimensional spaces (topical locators) and that creates ambiguity or
wormholes.  By ignoring the http morph, one ignores the tuning filter
that sets the manifold for the task at hand.   The web isn't "one
uniform space".  It is a lumpy aggregation of multiple overlapping
dimensions.  The morph should tell the observer what space is to be
observed.

The architectural POV that it is a good idea to put HTTP on every URI is
simply wrong.

len 

From: Rick Jelliffe [mailto:rjelliffe@a...] 

... I know I have a much more XPath versus grammar viewpoint than many
people