VoxPoints, NeoReQuest, and PatternSmithing Alliance

Posted on April 5th, 2010 in FluxPointsBlog,Uncategorized by admin
FluxPoints fits into a larger set of projects and the plan has been to add its technology in after some of the other layers have been built in.  This was always due to its complexity, and to avoid any tight-coupling to the fluxpoints framework; however, some recent work on static pattern engineering and the Thingk framework have prompted the need to inject the underlying concepts in FluxPoints into all of the projects.  The developments are quite exciting and I expect tremendous momentum on all projects over the next few months, so there will be plenty of opportunity for those who would like to contribute. I can’t talk about detailed specifics on two core components of the FluxPoints framework; however, after working with their consequences, I believe they can bring about a transformation of how we use the web.  Both are geared around the goal of bringing flux to endpoints that wrap around static patterns or Thingks (that is, fluxpoints).  There will be several mechanisms for bringing flux to these endpoints, but these two additions, it is hoped, will change the nature of how people respond to information on the web. The first, and oldest, mechanism is the NeoReQuest framework, and changes the way we look at the standard web request and the way we frame a sequence of interactions with the web.  The notions of context, intention, and most importantly, autotelic behavior surround this longer running transaction we frame as a new form of web request.  Eventually, NeoReQuest will be a standalone site as the value this way of walking the web will bring will far outgrow the fluxpoints project; however, the fluxpoints framework will frame the activities on partner sites (thingk.com, dreamspawn.net) as NeoReQuests.  This serves a two-fold purpose: to bring flux from the partner sites to these activated endpoints and to evolve the neorequest framework so that it can be effortlessly incorporated into future partner sites when it is time to go public. The second project focuses on one of the best forms of analog flux that carries meaning that we have encountered and has been completely overlooked on the web.  Armed with the technological platform we are arranging and some basic concepts, this form of flux provides us some of the best measurements and provisioning of flux from the human mind than we could ever hope to achieve without it.  To be honest, since this idea came to me I have not been able to tuck it away for future work.  This is probably the most active Thingk in my mind at the moment and the energy of it will drive all of the other initiatives forward (except it will probably slow work on the book I am writing).  Of course, I’m being purposely vague, but those who work with the beta testing of Thingk.com will be able to experience early stages of this technology. Finally, the PatternSmithing Alliance is the “centralized organizing and guiding body for the core activities, knowledge, and applications of static pattern engineering technologies”, and these are three such technologies (that is, fluxpoints, neorequests, and voxpoints).  All three are semantic web technologies at root (that is, they both expose and consume data using the semantic web framework) and the Alliance will maintain the specifications for the ontologies and schemas used for all three.  This is also an invitation – I am interested in collaborating with individuals who are interested in any of these technologies. As a last note, I want to pay homage to Dr Stephen Thayer, whose series of Thingks and experiments he performed with Imagination Engines, and his generous sharing of information to the web community all along and my subsequent exposure to them, gave the initial inspiration for the FluxPoints project.  Although I am not using any of Dr Thayer’s technology in this site, the spirit of his ideas and the results he obtained live inside this project – I have no doubt exposure to his ideas directly transformed my own conceptions of SPE technology back in early 2001.  This sort of attribution (the “inspiredBy” attribute in the Thingk-related ontologies) is essential to track.  Thank you, Dr Thayer.

FluxPoints project

Posted on August 15th, 2009 in FluxPointsBlog,Uncategorized by Joel.Kotarski

The FluxPoints project is a direct application of Static Pattern Engineering theory to the Internet — it is tightly coupled to the Thingk project.  Whereas the Thingk project allows anyone to express a static pattern into the virtual domain as a combined expression of an idea (think) someone pursued/is pursuing and the manifestation (thing) it was/is becoming, the FluxPoints project takes the expressed Thingk further with a technology infrastructure that adds the following:

  • The Thingk is now embeddable and transportable via a comprehensive API that allows it to be composed into larger bodies of work (for an example, see the DreamSpawn project).
  • Once properly qualified with further metadata, the Thingk can be used to expand an ontology and/or represent itself as an instance of an existing ontology in the Semantic web.  The FluxPoint enables full partipication of the Thingk in (most) semantic web technologies.
  • The Thingk now acts a web service endpoint (with standard behaviors defined in the API), a linked data endpoint (according to semantic web standards), and a web resource renderable in multiple formats (including those supported by the NeoReQuest project).
  • While creators (of Thingks) can collaborate with other creators and Thingks via the Thingk project website, this technology infrastructure allows collaboration of Thingks and creators by a more automated process — this is a combination of an agent API that leverages both the standard API and the semantic web technology to use inferencing and categorization to find unexpected connections.
  • The FluxPoint now gathers data as it is exposed to the Ambient Flux — a new technology exposed via the FluxPoints hosting platform (and further enabled by NeoRequest project).  As requests are issued for the web service, semantic, and web resource interfaces for this technology, the surrounding context is also made available to the hosting fluxpoint.  The automated agents run random and targeted permutations across all fluxpoints on the hosting platform in an effort to find collaborations of Thingks and FluxPoints.  This is an intense collaboration of all the associated technologies above and is one of many planned.

Essentially, on a structural level, both the Thingk and FluxPoints projects follow a semantic web ontology established and maintained by the PatternSmithing Alliance; therefore, any Thingk is easily upgradable to a FluxPoint (and later, other entities) – the FluxPoint is a Thingk with added meta-data not applicable to an ordinary Thingk.  On a behavioral level, a FluxPoint is a container that wraps the Thingk with added functionality that operates on this extra meta-data.  For the hosting aspect, it is envisioned that a FluxPoint can eventually be hosted anywhere; however, as the API and behaviors continue to evolve in the beginning phases, it will be mandatory that all FluxPoints be hosted on our servers (to receive automatic upgrades in behavior).

  • Comments Off