The always-interesting Jeff Jonas wrote recently about outbound record-level accountability, i.e., tracking where sensitive data is sent.
Without outbound record-level accountability … ensuring data currency across information sharing ecosystems can be problematic. The challenge being when a record changes in the originating system, how will one be certain which recipients of the original record need to be notified?
He adds that while such accountability is desirable, “not every mission will warrant the cost.”
I wonder, though, how much of the cost might evaporate if we make the architectural shift from sending data around, like email, to publishing it, like blogging.
I love the phrase data blogging, which Gavin Carr coined in response to some of the articles in my hosted lifebits series. One of the things that falls out naturally, in a syndication-oriented architecture, is the ability to audit who your subscribers are, and which chunks of data they access.
Note also that Jeff’s caveat about “which recipients of the original record need to be notified” implies owner-initiated push. But if the recipient is a subscriber, that update channel is already open and ready for use.
In terms of the value that the syndication pattern can provide, both for inter-personal as well as for cross-organizational communication, I think we’ve hardly scratched the surface.