Monday, September 7, 2015

Notes for the #nemetichapter

Noticed call for proposals from Neus on Twitter. Sept 1? ( needs confirmation.)

The nemetician team was pulled together on twitter. The collaboration moved to G+, Gdocs, and continued on twitter. The proposal was submitted on September 4. The same day our team received this:

Thank you for submitting your chapter proposal, "Transmedia and Transliteracy in Nemetical Analysis," for the upcoming book, "Encyclopedia of Information Science and Technology." After reviewing your recent proposal, I believe the topic of your proposed chapter is consistent with the theme of this book and could make a significant contribution to this project. I therefore encourage you to begin preparing your full article and submit a copy before Thursday, October 15, 2015 at the following URL:

The power of transmedia is to make collaboration on even serious academic documents simple with almost no strain. No meetings. No phone calls. No schedules. Everyone works in their personal Time. Inserts into any number of places. Goes away and waits for a response. Asynchronous time is the secret sauce of transmedia.  With practice of the nemetic stance, managing the complexity of transmedia social networks becomes ezpz.

I use "ezpz" as a way to communicate the reality that Transmedia is about making collaboration on academic research documents fluid, easy and very very fast.  For the Twitterverse, we use ezpz - The Nemetic Way. Our theory and practice says that if and only if we use the phrase appropriately to twitter it will eventually trigger some interest. Once it triggers interest in the form of a RT or a direct @, it is evidence the flow has begun.  The next step is to exchange. But exchange can only work if it is appropriate to the culture of the conversation itself.

In nemetic code,  neme exchange with one person creates a string. Neme exchange with two other people in the same tweet creates a nTube. With persistence and a pattern of exchange the nTube will grow. When it reaches critical threshold the nStrings ( network ) can take a non linear leap to a more robust state.


  1. Exactly. Just as it happens on a daily basis.

  2. This comment has been removed by the author.

  3. Remember, this is an encyclopedia article. In other words, we need to present the broad principles, and provide references to where people can gain deeper knowledge.

    We should be careful about entering too much into nemetic jargon, this is not the place, though we certainly will need to mention some of it. It would be well, OTOH, to have a set of references ready - for example, NIASK articles, RGB Waves posts, etc. - that do explain the code further in depth, and provide clear explanations for the uninitiated.

    If we say ezpz we have to prove it - and that means not baffling folks who are not in the "inner circles."

    1. Agreed and understand. Do you think the language in the post would be accessible?