Projects
Extending the Spime Ecosystem: OpenSpime and ScenConnect
Hello fellow OpenSpime developers,
I’ve been working on a Sourceforge project called ScenConnect, and I am interested in investigating OpenSpime as a prime component its intercommunication layer. First, I’ll briefly describe ScenConnect. Then, I will explain why OpenSpime could meet ScenConnect’s intercommunications needs. Finally, I’ll describe a partnership for further building the spime ecosystem.
Scenario connectors are tools for rapidly constructing scenarios out of tags, scoring the desirability of scenario outcomes, and then matching those tags with those found on spimes, providing information about decisions needing to be made that match the surrounding environment. ScenConnect is a Sourceforge project that is attempting a preliminary implementation of such a scenario connector.
Scenario connectors have many distributed communications needs. Scenario connectors need to be able to receive authenticated information from spimes. The scores (opinions and preferences) attributed to a given user have to be verifiably from them. Scenarios might only be shared with a limited group of other users, and need to be encrypted. The secure lightweight namespace provided by OpenSpime can be employed to these purposes to an extent, and it seems clear that further development of the capabilities of OpenSpime may lead it to being a reasonable underlying protocol for scenario connectors, generally speaking.
The development of each project only adds to the capabilities of the others. C2O sensors and other OpenSpime content providing projects only add to the content that can be tagged, scored, and deliberated in a scenario connector. Furthermore, the analytical capabilities of the scenario connector only improve the likelihood of important data to be indexed, evaluated, and deliberated in its proper context. Given these mutually reinforcing capabilities, I promote the development of a project that will plug into ScenConnect’s distribution interfaces implemented on top of OpenSpime. Furthermore, I see the OpenSpime project as a partner project in implementing the spime vision, and hope to work with OpenSpime project developers in situating their data.
Tags: Discussion
3 comments for “Extending the Spime Ecosystem: OpenSpime and ScenConnect”
Post a comment
You must be logged in to post a comment.
Recent Comments
- Roberto Ostinelli on Extending the Spime Ecosystem: OpenSpime and ScenConnect
- john.benjamin.cassel on Extending the Spime Ecosystem: OpenSpime and ScenConnect
- Roberto Ostinelli on Extending the Spime Ecosystem: OpenSpime and ScenConnect
- Roberto Ostinelli on PyOpenSpime v0.1 launched
- natch on PyOpenSpime v0.1 launched
- natch on PyOpenSpime v0.1 launched
- Roberto Ostinelli on PyOpenSpime v0.1 launched
hi john,
thank you for this input. i believe that to develop such a scenario you would need data collecting servers, aka ScopeNodes on the OpenSpime architecture, that would comply to the ScenConnect project. These would need to be in some way uniformed [maybe rdf?] so that using a ’scenconnect’ OpenSpime extension this data could be then collected by a requesting entity.
your project reminds me in many ways the ‘location linked information’ project of matt mankins: http://alumni.media.mit.edu/~mankins/lli/. do you happen to have contacted him? he might have interesting insights on this. he has a different approach than the OpenSpime one, though here too, there are definitely many common points.
i’ll look into a ’scenconnect’ protocol extension for OpenSpime asa i have some time, i.e. a protocol to allow seeking for lat/lon data.
cheers,
r.
Hi Roberto,
My kind thanks for your comments. Since ScenConnect is built to work with tags (taking a modified mutual information between clouds), it can even work on formats with much less structure than RDF, such as ordinary text. Having said that, the more structure you have, the more advantage to be had.
Thanks for the reference: I haven’t contacted Matt, and embarrassingly I wasn’t even familiar with his work until your post (Most of my input has come from the futures studies community). I look forward to my future correspondences with him.
I greatly appreciate any work you have time to do. :-D At the same time, I hope we both don’t have to do all the work: I think there is a role for other developers who want to get involved to work on an interface project. I think there is room for an ecosystem of projects around the spime idea, of which our projects are part.
Take care,
John
we’ll see about who will like to get involved. the more scenconnect can offer, the more other developers will kick in. as i said i’ll do my best to develop OpenSpime in a way scenconnect may benefit too.
please do keep me updated on matt’s responses, it would be great having him into such a project.
cheers,
r.