PatternSmithing Alliance Blogs

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 Thaler, 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 Thaler’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 Thaler.

• (0)

The Thingk.com private beta will open up in May 2010.  Here are some details surrounding the private beta:

• This will be an invitation only beta, which means:
  • Some colleagues and friends will be asked directly to join – please feel no obligation but your feedback will be greatly appreciated if you can assist.
  • Throughout the last few years, I have been looking at interesting individuals who may be interested in patternsmithing and Thingk persistence – you will be receiving a hand-crafted email as a personal invitation – once again, no obligation please – only do this if it brings you value but if you do your feedback is greatly appreciated.
  • As expressed on this blog, if interested feel free to contact me at the contact form http://xri.net/=joel.kotarski and I will be able to accomodate you.  Also if you think you know someone who would be interested from the category above, please contact me here as well.
  • We’ll probably have limited invitations to spread around among private beta users – these will probably only be on a request-only basis, however, to control capacity initially.
• For those in town, we will most likely host an in-person meeting where we will go over some details about the site and what is being accomplished – for out-of-towners we may also host a teleconference as a separate event.
• Since we will be testing privacy and security (with potential bugs to be found), I ask that you put the kind of ideas you may spontaneously work on but not your actual work and certainly not anything you would consider intellectual property at this point.  Much of the data from the private beta will be wiped clean on launch so that we can fully test; however, I am planning to make an easy mechanism to tag content you wish to transition over to the full system – also, I will be soliciting feedback on making this process as painless as possible for those generally interested in getting value from the work they do in beta testing.
• As always, being asked to participate should not imply obligation to participate, and participating should not imply obligation to give detailed feedback.  Anything you do is greatly appreciated and will be rewarded in some manner.

• (0)

The user interface will be central to the success of the Thingk.com site.  We’ve gone through several iterations of user interface in an attempt to simplify how our users will persist their Thingks.  After several iterations, I believe we have reached a concept that will achieve all the goals we set out to accomplish – I am codenaming it “Polymeric” – a nod to combinatorial chemistry (more on this later).  This label may or may not make it beyond the source code and this blog/design meetings, but it usefully describes what is going on: I  want the user interface to not only assist those who have a Thingk ready to persist without getting in their way, but also those who are searching for a solution in a combinatorial manner (where the site becomes a source of information, components, and inspiration as well as a persistence mechanism).

Polymeric finally admits that the user interface should get out of the way of the user – that the best expression comes out of the user if they are guided and prompted along but in a non-intrusive way.  At the core of Polymeric is the ContextProvider – the context is used to provide suggested components, prompted questions, and directions for exploration.  The ContextProvider works at three levels : what the user has done before (what Thin(g)(k)s* they have created, what Thin(g)(k)s have inspired them, as well as the components of each), what they are doing right now (the current word they may be trying to type, what question they are answering), and where the engine can infer they are going (via pattern matching of current text we can infer related directions for exploration).

*: Thin(g)(k)s means Things, Thinks, and/or Thingks (or any combination thereof).

At the center is the Polyermic edit box – a text editor (with optional rich editing functionality but this is hidden away and only appears under certain circumstances) which is fed by and feeds the ContextProvider.  At the moment, we are planning to have users use WikiWord format to denote Thin(g)(k)s across the entire site – it is just a format that works well.  The ContextProvider loads several layers of information, but the first layer of information is a static list of WikiWords (that is, pointers to Thin(g)(k)s) which the user has had contact with (either by creating, being inspired by, or using as components in their other creations), primed for usage in this context.  Let’s look at the post I am writing currently on this blog – four WikiWords are at play and only three are Thin(g)(k)s.  The Thin(g)(k) WikiWords are : “ContextProvider”, “Polymeric”, and “Thin(g)(k)”.  I’ve repeatedly typed all three manually throughout this post, but if I was editing this post in Polymeric in the actual Thingk.com web site, these words would have been suggested to me.  This due to the first and second layers of information: “Polymeric” and “Thin(g)(k)” would have been loaded in context in the first layer (as my creations and/or creations I collaborated with others on), but the moment “Polymeric” was suggested to me and I picked it, the ContextProvider would have loaded all the components of the Thingk “Polyermic” into context, including (but not limited to) the “ContextProvider”.  And one of the other Thin(g)(k)s that would have been loaded is a reference to a project which inspired context suggestions and must be payed homage to: GoogleSuggest.  GoogleSuggest inspired many people as an autocomplete mechanism to use Ajax to give suggestions based on user inputs, but this is in the context of one singular input, whereas we will suggest individual parts of a larger body of text – this is of course nothing revolutionary – you can see the same feature on your cell phone.  The difference here is that a Thingk, behind the scenes, will be a RDF resource that follows the ontology defined for Thin(g)(k)s at the PatternSmithing Alliance, including linkages between Thin(g)(k)s at the RDF level.  Like most semantic web applications, we would never dream of having our users manually hand-type RDF; however, by choosing one of these WikiWords, the text of the Thin(g)(k) is not the only persisted but also the relationship/link to the Thin(g)(k) itself.  This was the crucial problem to solve – to give the user an intuitive mechanism for forging these relationships.

The Polymeric user interface has an additional set of features which are fed by the ContextProvider.  Several of these are based off the usage of WikiWords – for instance, it is possible to use a WikiWord for a Thin(g)(k) not currently on the site (for instance, my mention of GoogleSuggest would have started the process of creating an authorative reference on the site to Google’s project, pending Google’s permission to create such a thing) as well as suggestions to the user to turn a repeated pattern of text into a WikiWord and therefore a Thin(g)(k) on the site.  Additionally, the outer borders of the user interface will have bits of context floating in based on what is going on inside the editing area: a cloud of moving WikiWords that can be grabbed and dragged onto the editing surface that changes over time, and prompting questions that fade in and fade out  to guide the user to starting or evolving their work.

Once we open up the private beta, we will be soliciting feedback from some of you, so please contact me at http://xri.net/=joel.kotarski if interested.

• Comments Off

I’m happy to announce the “launch” of DreamSpawn, which effectively gives an overview of this company’s overarching strategy for the next few years, as well as how all of the products and initiatives will work together.  Essentially, the concept of ThingKs and the practice of patternsmithing (crafting ThingKs, whether they are your own or others,  into physical or virtual reality using your innate talents) are central to everything.

Thingk.com will be a free community product; however, we are looking to encourage a revenue stream by offering premium tools for crafting the representation of the Thingks on the site and for patternsmithing them into the world.  I have neither the delusion that this company will be capable of inventing all of the possible ways of expressing or creating representations into the world nor the desire to corner that, so we will be looking to offer partners the ability to sell their tools on this site.  Now that brings up a few questions and all of them relate to if the site will immediately become littered with commercialism and the answer is a firm no.  That means the following things outright:

• The desire to give the web community an incredible free basic toolset for persisting, discovering, and using thingks will be fully realized — this base functionality will always be available for free.
• Opportunities to buy more powerful tools will be non-intrusive – the screen real estate will not be littered with it.  It will only be available when you really seek it out, tucked away neatly in the user interface.  Also there won’t be annoying intrusions on experience, trying to prod a user into upgrading – people are quite intelligent enough to seek out things they want.  This is not to imply that it will be difficult to find what you want or that there won’t be a good user interface once you begin seeking out premium tools.
• Users with premium tools will not have an obvious advantage over others, its just a matter of preference.  As a physical analogy, think of an art community where everyone is given a sketchpad, a basic set of pencils, brushes, and paint – the refined artist may choose to purchase an easel, premium paper, brushes, oil paint, etc; however, this doesn’t imply that either will produce better art – it is up to the artist to use the tools given or purchases along with their creativity.

The intention for DreamSpawn is to give the clients who use this service the full array of premium tools as they are made available — which brings up another point: companies and individuals who choose to do so may purchase the full array of tools available (with royalties paid to each of the partners who are represented as well).  This will be done for DreamSpawn for a reason that is explained below:

DreamSpawn is a concept I’ve been trying to tackle for years – probably since I was a teenager.  I wanted people to unlock their full potential but it would take me a long time to see the pieces of the puzzle and even more time to put them together.  I believe that once people reorient their mind toward viewing their larger dreams (which might span a large problem/solution domain) as a set of ThingKs, or thoughts on their way to becoming things, they have a whole new way of tackling the problem — this is typical analysis; however, there is a new spin on it:  By giving the dream itself (and thingks in general) value once persisted, people will begin to move forward with bringing their dreams about.

The other pieces of the puzzle attempt to solve three other problems:

• Dreams and thingks are often kept internal – and often get buried or forgotten.
• People don’t always find the right connections with other individuals and concepts – when this ‘serindipitous event’ happens in life we usually witness the great events (company foundings, product launches, etc) that we all have come to celebrate.
• We all constantly work on skills to complete our vocational work, but all too often we don’t have the general skills or specific schools to create the dreams (set of thingks) that inspire us from time to time.

These needs are addressed by thingk.com, fluxpoints.com, and patternsmithing.com – not respectively or exclusively, but overlapping in interesting ways.  DreamSpawn brings all of this together by flipping it around to one individual – giving incredible attention to that client (and forcing them in turn to give attention to their dreams) to ensure no impedances keep that from happening.  As individuals choose to invest in time, attention, and money into their dreams, I want to give them a literal arsenal of tools to obliterate potential impedances.  I want their creativity to flow and want a full support network to wipe those three bullet points above off the table for reasons why they may look back and regret not creating this or that dream.

This blog entry is not a sales pitch to get you to sign up as a dreamspawn client – in fact, we’re not ready for you – that’s why this is an announcement of the “launch” of the sister site.  This is meant to only give a larger perspective of what’s going on behind the scenes, and I’m choosing to do what future users of this site may or may not choose to do – I am persisting out publicly a set of Thingks I am actively working on to bring about as a reality.  That is, I am releasing the concepts out there to spark interest, keep myself accountable, and get the dream in front of myself and others.  Collaborators, angel investors, future partners, volunteers, and future employees, as always, are always welcome.  Contact me at http://xri.net/=joel.kotarski or on the contact form on DreamSpawn if interested (also, feedback in general is welcome).

Finally, the PatternSmithing alliance — anyone interested in joining this alliance or learning more, contact me as well.

jdk

• Comments Off

As the core infrastructure is being put together for the site, I have made an initial technical decision that will also enable a (future) marketing campaign.  Without being able to seek his permission, I am tweaking one of René Descartes‘s most famous expressions ‘I think, therefore I am‘ to signify what I want to represent a fundamental shift in our relationship to thoughts and creativity.  Admittedly, I think that the term ‘thingk’ is catchy – it finally came to me after six years of using a far more technical term in other work; therefore, I am anticipating that it may give us a useful way to describe  both an expanded approach to the creative process as well as more coherent and reusable artifacts of the creative process.

Once the framework is in place, I want people to be able to exclaim:

I thingk; therefore, I am creating…

as a representation that they are participating in being intentionally connected to the entire process from thought => think => thing or from thing => think and by expressing the entire process they are likewise engaged in inspiring others to create as well.

In order to express that notion across the web, I want people to have an online identity that succinctly expresses that.  I am a big advocate of OpenID and am building provider support for OpenID into the site in the beginning.  Therefore, anyone who has an account will be able to use this URL as an authentication mechanism for OpenID-enabled sites:

http://i.thingk.com/UserName

This URL will also correspond to the user’s public profile which will expose out any Thingks they have released to the public (or if an authenticated thingk.com user lands there, any Thingks they have exposed out to the appropriate group(s) that individual is in or uniquely to them).

Also, as aggregated identities centered around intention become more commonplace — tightly knit groups would be able to appoint delegates who could authenticate under the identity:

http://we.thingk.com/IntentionName

The intention for this is not to simply add to the growing list of URLs that a person uses to identify themselves* in the current internet ecosystem (though in a way it will do that and unfortunately add to that list); instead, it is a way to identify that which is being created by them beyond the current internet ecosystem – which as a whole other dimension we all now participate in to varying degrees is interesting in itself.  This identity represents not only them, but the thoughts which activated them enough to become thinks and have received intention enough that they will on their way to becoming things (or the opposite case things which they have created which have received intention to be expressed as thinks).  In essence, this represents not just the person (in an abstract way), but their intentions being manifested (thingks-in-formation) and the creations they have accomplished (thingks-as-artifact).

* Current examples span blog URLs, social networking for fun sites, feed aggregation sites, professional networking sites, etc.

So, depending on context, it may or may not be appropriate to use this provided online identity.  There are two lines to draw where it will or may be appropriate to use this online identity and a third class where it is up to the discretion of the user:

• The intentional web+ - a grassroots initiative started around this about four years ago and hasn’t gained a significant amount of momentum; however, this project embodies one aspect of the spirit of this movement.  Where people are using technology to actively aid in carrying out intentions (e.g., aggregating information based around a certain intention, or using technology to carry out an intention).  As these sort of sites begin to multiply again, it will absolutely make sense to use this sort of identity as those who see the URL will be able to use it to intentionally aggregate information or use it to find inspiration for their own intentions.  [This will be further amplified by the FluxPoints project later]
• The semantic web - an initiative that is slowly but surely gaining a lot of ground and I believe will soon cause a groundswell of potential on the web.  Due to the fact that semantic web technology is being built-in to Thingk.com from the ground up, semantic information will be exposed at this identity endpoint – so if a user chooses to express this online identity at sites which are likewise rich in semantic markup or have active semantic agents, the mutual information exchange available by simply exercising the identity depending on the context may bring benefit to multiple parties. [This will be further amplified by the FluxPoints project later]
• The third class I spoke about is the myriad places where someone can express identity on the web currently via OpenID- posting a comment on a blog entry, setting up an account on a forum, etc.  Depending on context, it might make sense to use one of several options available for authentication (several are shown below if you comment on this post) instead of this identity and it might make absolutely no sense to use this new identity at all (except of course to spread awareness of the new initiative).

+ Here is the homepage for the intentional web initiative established in 2005: http://intentionalweb.org/

Another post is forthcoming about the place for a site centered around Thingks in the current web ecosystem, as well as long term discussions about where Thingks will be hosted in the future if all goes well (that is, will they have to be hosted at thingk.com forever or like web sites, blogs, etc. can they be eventually decentralized).  Until then, if you’re ready to start wearing the T-shirts or hats, let me know. 

• Comments Off