“Polymeric” user interface

Posted on January 2nd, 2010 in News,ThingkBlog by admin  Tagged , , ,

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 thingk; therefore, I am creating’ campaign and OpenID

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

Thingk.com / Blog

Posted on March 21st, 2009 in News,ThingkBlog by admin  Tagged , , , , , , ,

I am excited to announce the commencement of active development on Thingk.com, which will be the first of several partner sites centered around the activity of bringing ‘thingks’ into reality.  This site is for the community with the intention of inspiring people from all backgrounds and walks of life to engage in creative activity.  Ultimately, it is hoped that as people create ‘thingks’, meaningful patterns will emerge to give new discoveries for life’s works, lifelong endeavours, and previously unimagined collaborations between individuals.

A thingk, quite simply, is both an idea that someone passionately pursued/is pursuing and the thing which it was/is becoming when manifested.  Since someone (we will call them the creator of the idea) is passionate about the idea, we can’t just call it a thought, but instead borrow a present-tense term from David Bohm and call it a think.  Since it existed/exists/will exist somewhere, we also call it a thing.  Combining the two words into a portmanteau, we call it a Thingk.

In order to qualify as a thingk, the following must happen to a person’s creation (whether it starts as a thought or a thing in the beginning is irrelevant) in any order:

  • A burst of inspiration or a careful design process must bring a thing into the world* whose existence can be confirmed by a resource identifier.
  • A thought or thoughts become so activated in the person’s consciousness so as to be qualified as a think or thinks.
  • The intention to create something from an activated think or thinks or the intention to express the thinks behind a created thing must be present.
* The thing can exist physically or virtually but must have a computer-accessible and verifiable international resource identifier.

Thus, once the intention, the thing (whether existent or not), and the activated thought (whether expressed or not) come together we have a Thingk.   Stated another way:

think(s) + intention to create something= thingk

or

thing + intention to express underlying think(s) = thingk

When the think- or thing- component(s) of the thingk is partially or fully intention it is a Thingk-in-formation; once intention becomes reality, and there exists both thinks and a thing, it is now considered a Thingk.

The purpose of this site will be as follows:

  • By providing a framework to organize the creative process (with associated tools, privacy mechanisms, and attribution), it is believed that the site will increase the quality of all participants’ creative endeavours.
  • By allowing someone to release their work to selected individual(s), group(s), or the public at large, valuable feedback mechanisms will increase the quality of work as well as inspire others to new work.
  • Both technology and community are expected to further enhance and encourage the creative process for all participants.
  • By getting to the kernel of the creative process, it is desired that things we see in the world are matched with the thinks that inspired them or the thinks we hear in the world are seen manifesting into actual things.
  • By allowing individuals to catalog the creative process in (hopefully) painless ways with minimal effort, new interconnections can be found between ideas (thinks), creations (things), people (creators), and the thingks which inspired it all.  In other words, we expect lots of new discoveries in terms of collaborations, career paths, and systems effects we were not even aware of.
  • Finally, this site intends to lead all users into deeper exploration with their created Thingks, the Thingks that inspire them, and the resonances they imply.  This is meant to span the lifetime of both Thingk(s) and their creator(s).  It is envisioned that initial thingk(s) [prototypes are encouraged] may expand far beyond the scope originally envisioned.

This site is an application of Static Pattern Engineering technology as well as a member of the PatternSmithing Alliance.  It will be based on Semantic Web technology.

I am actively seeking collaborators, founders, research associates, future users, and future employees.  All feedback is welcome.  Contact me at =Joel.Kotarski.

  • Comments Off

Thingks

Posted on October 3rd, 2008 in News,StaticPatternBlog by Joel.Kotarski  Tagged , , , , ,

David Bohm, in a series of talks (that later became the book Thought as as System) once said that we should delineate between ‘thoughts’ and ‘thinks’.   Thoughts are former products of consciousness that are stored in memory and passed around from person to person, while ‘thinks’ are products of consciousness created in the present moment with active mentation (or which consicousness is actively operating on even if former products of consciousness).  Bohm’s clever wordplay has finally led me to a perfect catchy term for describing the far less catchy term ’static pattern’:  thingk. That is, a static pattern, in the form we are most interested in for application can be called a thingk.

Thingk is a union of the words think and thing, and when pronounced sounds deceptively identical to think.  I like it because it embeds a lot of semantic hints that convey what a static pattern is:

  • The first word in static pattern, static, comes from Greek and Latin roots for standing, remaining, and implies persistence.  When something persists, we usually identify it (generically) as a thing.
  • When you first encounter (or create) a static pattern that resonates with you, it has the effect of gathering such awareness and attention in consciousness that it seems less like a thought and more like a thing.  It usually invokes active mentation and becomes a think in Bohmian terms.  This duality, as it grows, begins to qualify it as a thingk (in the cognitive domain).
  • In the physical or virtual domains, before that thingk is manifested, it is just a thought ( think ); however, as you, the creator, drive it toward manifestation, it becomes not just a thought ( think ) but also a thing that exists (stands, remains, persists) with some degree of physical persistence (depending on degree of virtuality).  Yet, behind that now existent thing is the thought(s) that resonate with the creator such that they evoke active mentation and thus are still think(s).  Thus, the manifested static pattern is a thingk spread across multiple domains (cognitive, physical, virtual).
  • If you encounter a thing that you can perceive with your senses, there are thoughts that brought it to creation.  When these thoughts and the thing itself invoke resonance in a perceiver, it can be now be described as a thingk.
  • When you find a talented individual with a personal connection to the work they create, you can certainly be assured that everything they create has the quality of also being a thingk.
  • If you begin to approach the things you work with with the intent to turn them into thingks (or to change your work so that the things you work with have a higher rate of probably of being thingks for you), or you begin to have the intent to find thoughts that resonate enough to become thingks in consciousness and then reified thingks in the cognitive, virtual, and/or physical domains, then the nature of your creative work is transformed.

I intend to not only use this term for describing static patterns in a more easily graspable semantic framework, but also intend to use it drive the fluxpoints project further.  A fluxpoint, by criteria, will be in fact a thingk; however, I am actively working on a partner project to actively get people moving from thought => think => thingk, which will ensure a natural evolution path toward turning those thingks into FluxPoints as well as physical, virtual, and/or cognitive creations.  This will most likely be a free community web site that will allow for active work on static patterns (or thingks) with the intention of bringing them about as creations.

Until then, I still prefer to use the technical term static pattern, but after discussing this more compact and expressive reduction with people who have talked to me about SPs for years, it immediately catches on and they finally ‘get it’.  Nonetheless, this particular journal about static pattern engineering will probably continue to use the technical term – I intend to post a link to the community site once I get it going and that site will probably make scarce use of the technical term, favoring the one described in this post.

Thanks for reading.


Copyright © 2010 Static Pattern Thoughts. This Feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is guilty of copyright infringement. Please contact us so we can take legal action immediately.
Plugin by Taragana
  • Comments Off

PatternSmiths, Static Pattern Engineers, and Architects

I honestly believe I will be working on SPE my entire life, and am prepared to do so; however, a life goal of mine (i.e., before I die) is to see the knowledge base of the field (core theory as well as tried and true mapping of it to case studies and implementations) developed enough so that three roles – actual professions – can emerge as viable careers for the 21st century. As I continually work on static pattern engineering, I intend to work within all three of the roles to further define their domains as well as the output these roles produce in their differing capacity is essential to the development of the field.

In order to introduce these roles, I need to talk briefly about what a static pattern is without going into much detail (a separate set of posts will be required for that***). Briefly, a static pattern is a product of consciousness[1] that has reached a degree of coherence[2] that it can persist (stay, remain) within one or more realm/domain (see virtual, cognitive, and physical in the first post on this site) or across these three domains. [ Static pattern engineering seeks to give us the ability to further operate on and transform these units of consciousness in extremely effective ways. Note that we already operate on and transform these patterns as part of our creative lives, our vocations, and perhaps even our spiritual lives; however, SPE seeks to greatly enhance the process toward expected effects as well as results. ] A static pattern can — and will — remain in one or more of the domains by its very definition, especially if an act of will has given a high degree of virtuality — that is, it has been persisted by some means into the physical realm with a high cognitive component to it; however, SPE concerns itself with –activating– the pattern (making it an active pattern) using resonance, operators, and transforms and bringing innovative results and effects back to the domain of origin (often cognitive) as well as the other domains where a pattern can manifest (virtual, physical, and/or cognitive again).

Now, for this discussion it is important to note that these products of consciousness that have coherence often don’t take an immediately analyzable form (so they can be mapped between languages and domains at will), and expressing a pattern, whether by embedding it into physical matter (giving it a higher degree of virtuality) or directly manifesting it into the world (creating it), and the resonant language[3] used to do so start to give form to these three roles/professions I see emerging.

My previous stub post on Artist, Artisan, Artificer finally comes into play in this discussion as well. The act of expressing/manifesting a pattern into the world usually can be categorized as the work of an artisan, artificer, or an artist. The label of artisan is usually associated with a craftsperson or skilled worker who can usually do a standardized operation or piece together standardized operations to produce an instantiation of a desired template or a unique combination or evolution of previous templates. The label of artificer is usually associated with skilled devising, inventing, construction, design of something entirely new or a more complex derivation/transformation of previous creations (thus, implying a longer time scale) but will nonetheless become a template. The label of artist is usually associated with someone who has imagination and noticeable talent in a particular domain that can produce something (through sometimes more mysterious and less-defined processes) that may be described as aesthetically pleasing, unique, original, such that the concept of template is utterly meaningless – it is an individual act of willed creation.

  • PatternSmiths will forge a static pattern into the physical, virtual, and/or cognitive domains based on their highly refined resonant language. The act of PatternSmithing itself will be shared by all three disciplines — and actually I dream of a day when every single person with knowledge, experience, and associated resonance in some language can be qualified as a PatternSmith of some type. The desire for ‘every person’s SPE’ that this represents doesn’t detract from the pattern-smithing role in the least or elevate the others; rather, if the engineering role does its job properly (see below), the vast array of fields (vocation[4]) and resonances possible will allow for everyone to become a skilled craftsperson to some degree or another. This fact in itself will confirm the success of the entire body of research and application for static pattern engineering — the patternsmithing is the application of the field.
  • Static Pattern Architects will draw on many domains of knowledge, experience, and language to conceptualize and transmit the design for large scale projects that straddle the cognitive, virtual, and physical domains. Working closely with Static Pattern Engineers, an inspiring and innovative design will emerge that will be further improved by the design aspects of SPE’s processing and collaborational technology for identifying the larger context the creation exists in across all three domains as well as the resources that can improve its implementation and continued existence/evolution in aspects of each domain. Because the Architect is examining all three domains in the design, he or she is in fact working not only at a physical level (as we have currently with traditional architecture), nor at just a computerized level (as we have with software architecture), but at a cognitive level and considering -all- virtual manifestations (e.g., creation of a business model is virtual, or defining a set of publications, or designing ways of disseminating the requisite knowledge, etc.).
  • Static Pattern Engineers work on multiple dimensions across the field of static pattern engineering and it is going to take a separate post*** to enumerate all the various aspects this will entail, but briefly it will involve managing the movement of knowledge and matching resonances across multidisciplinary teams to actualize (engineer) a complex product that can span multiple domains, operating/facilitating the process of collaboration and innovation in analysis, design, and implementation phases of that product, serving as a subject matter expert in one or more specialties (which they resonate highly with) within the domain of engineering, cognitive science, or computer science to serve as a contributing team member in analysis, design, and implementation phases of that product, developing artifacts which allow for more effective execution of static pattern engineering processes, developing tools which allow for improved detection of resonances (and thus location/training of qualified PatternSmiths), driving teams toward higher challenges and ensuring a high rate of innovation, and doing experiments and/or research which will advance the field on a continual basis.

The important thing to note is that all three of these roles at any point in time be acting as an artist, artificer, or artisan — the large difference between them is the granularity and function of their work (what they are focusing on). A PatternSmith could
in fact be a full-time artist and producing nothing but one of a kind, original productions in any domain, or they could be a craftsperson (artisan) that produces templated results with skill, or even they could be called upon for their artificer skills in producing something unique and innovative. Additionally, the PatternSmith’s varied resonance may allow them to serve in all three capacities across different domains or knowledge areas. Likewise, in their larger scale context, a SPA (StaticPatternArchitect) may use (and often will be required to use) a blend of all three modes of working to produce their initial and continued design, and the output itself will probably be considered a blend of the three — carrying out its refinement and implementation will likewise require a blend of the three in most cases, which the SPE (StaticPatternEngineer will facilitate, as well as initial design). Unlike the other two, however, the StaticPatternEngineer will be –required– to use a blend of all three. He or she has to be a skilled artisan in using the technology for matching resonances, moving knowledge, or invoking collaborations throughout a distributed system of thought – there is no time for innovation or art for this extremely important functional need; however, there will be a need for an artificer skill set in the unique design constraints of each product where only the static pattern engineer will have the requisite ability to perceive and identify unique approaches for that team. I will elaborate further on the SPE’s mapping to these labels in their activities, as well as the artistic output, in a future post***.

I hope you enjoyed reading about this as much as I enjoyed writing it — for some who have asked me questions, I hope it also gives a _much_ deeper glimpse into what this whole field is going to be about. Until next time I post, I wish you the best!
___
[1] Don’t be mislead into thinking this is restricted to only human consciousness. More on this later.

[2] I literally mean this in both the sense of coherence we see in physics (explaining how thought patterns can have this kind of coherence requires a much larger discussion) as well as a sense of cohesiveness (with other patterns, with the consciousness hosting it, with a requirement/necessity (perceived or real)) that literally ensures the pattern’s existence.

[3] In a paper on resonance, titled “The Power of Resonance“, I worked on in 2001 with Christopher Galtenberg, we carefully qualified language this way:

In our framework, language serves a critical two-fold mechanism: it converts experience into explicit, transmittable knowledge and transmits knowledge to invoke experiences. Language [thus] can take many forms, and in this framework, fits this broader definition: A language arises from a set of elements allowing transmission (expression) and reception of knowledge and/or experience.

The paper went on to then qualify resonant language, which I will do later in a future post***.

[4] I hope one day we can return to vocation as a calling (where really resonance represents the increasing call itself), and that a vocation, as a way of life, can encompass diverse fields, knowledge, associations, experiences, and possibly roles, as resonance implies a –set of callings– rather than just a singular one. Then we can have career-crafting as an ongoing process.

*** I am just explicitly marking my promises for posts now as a reminder to myself.


Copyright © 2010 Static Pattern Thoughts. This Feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is guilty of copyright infringement. Please contact us so we can take legal action immediately.
Plugin by Taragana
  • Comments Off
Next Page »