Our Internet of Objects

I'd like to thank Caroline for highlighting this passage from Ambient Findability:

As we build our Internet of objects, the permutations of sociosemantic metadata will create new avenues of findability. Where has this object been? Which objects were in close proximity to this object? Who touched my object? Where are they now? The era of ambient findability will overflow with metadata, as every object and location sprouts tags: social and semantic, embedded and unembedded, controlled and uncontrollable. Imagine the sensory overload of a walk in the park. Every path shimmers with the flow of humanity. Every person drips with the scent of information: experience, opinion, karma, contacts. Every tree has a story: taxonomies and ontologies form bright lattices of logic. Desire lines flicker with unthinkable complexity in this consensual hallucination of space and non-space, a delicious yet overwhelming sociosemantic experience.

Reading this from a distance reminds me how much fun it can be to write.

Are the puns/allusions deliberate, or just the by-product of being immersed in the subject matter for so long?

All the ones I'm aware of are deliberate :-) These include the Neuromancer allusions (e.g., bright lattices of logic) and the nods to de.licio.us and Flickr.

This is a very late comment but I use your Internet of Objects definition frequently.
I believe it to be the Dr. Who of definitions --- timeless.

I have been proposing an Information object concept that has two main classes:
1. scalar - magnitude only
2. vector - magnitude and direction

The "vector" object can then have properties like acceleration and trajectory.

The Front End is still the "Findability" which is Implemented with the Search-Find-Obtain (SFO) function. The "scalar" object would be sufficient for this process in the Front End.

It is the Back End where the "vector" object would have real value. The "vector" object wrapper could generate much useful Information for the Line of Business (LOB) and its Business Process Management (BPM). Save a lot of application processing overhead.

I'm going to keep this short to see what you think of the concept. I suspect some very bright people are working very hard on this outside my awareness. You might be aware of them and could point me in the right direction.