On Github ucla / app-sharing-presentation
ebollens [GitHub] / ebollens [LinkedIn] / @ericbollens [Twitter]
At first, we built obvious campus apps
But then, we started getting niche apps
Taxonomy is hard
People want choice
How can we provide the richest possible ecosystem?
Each organization contacts each affiliate
(1/2)*N*(N-1) connections
Aggregator for hub-and-spoke connectedness
Homogeneous world view and centralized trust
Peer trust relationships
Acceptance and sharing policies
Heterogenous and asymmetric
Suppose peer is sharing app...
Query AdjInPeer
Filer and transform metadata
Add to local ecosystem
Exposed to outlets
If app marked for propagation...
Filter and transform metadata
Expose to AdjOutPeers
Prototyped several months ago
Protocol is now under development
Once complete, implementation will be pursued
:identity => { :id => String, :originator => String, :checksum => String }
:attributes => { :name => String, :url => String, :share => true || false || undefined, :propagate => true || false || undefined, :capabilities => { # .. (peer may regard these capabilities) }, :require => { # .. (peer must implement & process) }, :use => { # .. (peer may implement & process) } }
:original => { # .. (original :attributes section) }
ebollens [GitHub] / ebollens [LinkedIn] / @ericbollens [Twitter]