Hamlet / DKR2 Criteria & Feature Requests
Comments
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Still loading...
ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAHAIAJAKALAMANAOAPAQARASATAUAVAWAXAYAZBABBBCBDBEBF
1
WhoSam HahnFrode HeglandStan GouldJack ParkKarl HebenstreitPavel LukshaDouglas MakepeaceDaniel BerleantMark SzpakowskiVint CerfAdam CheyerAlex&er Laszlo
2
Your Introduction: Amateur (founding) collaborologist. "Doug-Disciple"-wannabe. Managing member of "Program For The Future" (conferences 2008, 2010, 2013, 2015, Planned each December 9 through 2018 (and beyond). VP Technology at eGain Corporation. Collaborator with Doug in early 90's and 2005-2013. Founder: DocuMagix. Patents in automatic document recognition and filing, online remote cobrowsing. Coauthor: "Leading and Managing in Silicon Valley". Cochair: "Silicon Valley Engineering Leadership Community". Pioneer in GIS, intelligence fusion workstations. Linkedin: https://www.linkedin.com/in/Angelpreneur, Orchestra Conductor (Palo Alto Chamber Orchestra, Stanford Viennese Ball Orchestra), Chamber music coach (Whitson Chamber Music Workshop, San Luis Obispo)My main website is www.liquid.info and I post on wordpress.liquid.info and http://doug-50.info for this project. The documentary I did with Doug is at http://www.invisiblerevolution.netAs many of you know elements of this background to varying degrees, my professional career has been inspired by Doug's 1962 paper for over twenty years since I first discovered it and then got to hear Doug talk in person for the first time (ComNet96 in Washington, DC). The context for discovering Doug's work is that I provided technical support to employees with disabilities, which led to me working for Susan Brummel Turnbull and supporting her efforts to establish a Government Networked Improvement Community. My focus has always been Human Systems, especially conceptual frameworks, and I will be participating in the community through my augmentation system. TheBrain software is the core of my DKR.
I've put the most relevant chapters describing my thoughts online at http://ualr.edu/jdberleant/book/FoTexcerpts.doc. Aspiring earth cadet, VP TopicQuests Foundation. Starting 1972 co-designed Community Memory (which ran on the same XDS940 computer used by Doug's group). Later worked with Prograph, a pictorial objectflow programming language, and Knowledge Navigators' topic-oriented learning & collaboration systems. Student of Western philosophia, but also spent several decades with Buddhist awareness practices and studies. More recently explored personal and group leadership with ALIA (Authentic Leadership in Action) and Presencing (Theory U), and avatar-based epistemic journeys with the Play as Being community in Second Life.TCP/IP inventorTechnical Co-Founder of Siri (sold to Apple, built the voice Assistant available to 500M users)

Founding member of Change.org (world's largest petition platform for good, with more than 130M members)
Alexander Laszlo, Ph.D., is Director of the Doctoral Program in Leadership and Systemic Innovation at the Buenos Aires Institute of Technology (ITBA), Argentina; 57th President and Chair of the Board of Trustees of the International Society for the Systems Sciences (ISSS); Co-Chair of the Systemic Inquiry Group on Curating Emergence for Thrivability; and professor of Systems Science & Evolutionary Development.

more at http://en.wikipedia.org/wiki/Alexander_Laszlo_(scientist)
3
HAMLET : Demo Scenario: Participatory, interactive, co-creative, experiential.
4
HAMLET : Your Criteria for a Collective Thinking Space:Richly interactive multi-dimensonal space.There needs to be a deep structure, customization for personal views, more efficiently enabling methodologies. Minimizes disrupting attention (hide notifications, ...). How is 'collective' being defined? Does it mean a 'Networked Improvement Community? Intuitive interface for search/save/share functions in an organic rhizomic socio-technical system that demonstrates the capacity for collective intelligence.
5
HAMLET : Your Criteria for Dialog Record:Automatic recording, transcription and meta-tagging of all dialog with rich interactions of the record.Automatic recording, transcription and meta-tagging of all dialog with rich interactions of the record. +FrodeTransparent, technologically mediated multi-sensory virtual environments.
6
Your 1 Paragraph Aim:Ensure Doug's beautiful vision of "accelerating our collective capabilities to solve urgent global issues" is not lost as a legacy visionary thought, but is embraced, extended, realized, and then continually bootstrapped. Hopefully in time so that we can assure future generations a thriving antifragile meaningful life on Earth and beyond.To build an environemt which truly augments the passionate knowledge worker to collaborate more effectively with others, to a degree Doug would have been proud of. My specific proposal is here: http://wordpress.liquid.info/hamlet-action-proposal/Co-create and launch the proposed large-scale collaborative environment platform’s pilot demonstration at the 2018 Silicon Valley Super-Event Celebration of the Internet founders and their successful startups, while generating sustained promotion and funding, through the on-going Super-Event Program.If we accept that truth is an elusive concept, that truth is not the same in every context, then we are free to acknowledge that Engelbart’s real mission can be interpreted to lie in the improvement of truth seeking. That is, while the destination might be “Truth” (whatever that means), it is the journey, perhaps specifically, improvement of the conduct of journeys, which we seek to facilitate.Perhaps, indeed, facilitating improved truth-seeking journeys is our Aristotelian Final Cause.It is an event that, by leveraging the existing capacity of large scale collaboration via Internet, will demonstrate co-created collaborative environments of the future that will help solve 21 century global challenges.Finish Doug’s Work: Implement and Document his Big Ideas!Seamlessly integrate important existing collaboration systems that have been built already, while also integrating new systems to be built.Demonstrate advances in augmenting human capacity to address wicked and anthropogenic problems, through networked software technologies for harvesting and applying global knowledge married with social technologies for clarifying and augmenting personal and collaborative group intention, wisdom and decision making.‘Do something’ and maybe also ‘build something'Implement something along "Doug's Dimension" that can gain traction with a large number of users.Realize the potential of smart networks to augment human capacities to achieve individual and collectively potentials through seamlessly integrated technology enhanced information access and decision support systems.
7
Your 'offer' / role:I have dedicated (and expressed to Doug) all spare cycles for the rest of my life to making this happen. Ideally, it also becomes my MAIN cycles, not just spare :)I will be working on this for a good part of my time, along with the Author project, which should be a contributing system.User Experience, process facilitator, Content curator (my curration will be at https://webbrain.com/u/19Dw )(1) Farm out bite-sized contributions to the project as guided master's-level projects to students of varying (but modest by Stanford-level standards) performance expectations. (2) Create a "Table of Contents" page of various links that get mentioned in the discussion, in order to provide a reference source useful to participants.To hold & open the space of those UX points through which human intention nudges software behaviour; to alliance DKR2 with practitioners (such as Theory U) of the human side of such interaction; to help push such practice into the software side itself so that its intelligence is augmented by care.Doug's notion of bootstrapping suggested that any software project we build benefit the very software developers working on it. I would like to help build a Doug-inspired, next-generation software development environment; imagine something like github meets wikipedia, with OHS like features.To serve as "ambassador" of the DKR2 / HAMLET / Doug initiative to systems organizations and projects world-wide.

To serve as "host" of the DKR2 / HAMLET / Doug initiative by attracting and inviting potential players into the project to strengthen and augment this design community.
8
Problems To Solve:CoEvolve the ways we think, feel, create, behave, interact, grow along with our technological advances so that both co-inform in learning cycles.Augment our ability to solve urgent, complex probelms, colletively. DKR2 should help us with this by augmenting our ability to have a continously up to date 'handbook' on our work.Creating the true collaboration platform - defined as the shared systemic components understanding and commitment that facilitates our collectively shared collaborative innovations.Integration of disparate systems that can contribute to the overall project objective. But how to do it? Since our minds & hearts are the lens through which we experience everything, how do we clarify that lens? How do we maintain its sanity? How does our ever more autonomous software maintain its sanity and act to appropriate ends? How do we augment DKR2 with sanity?Getting traction along a common dimension so that we can make progress together. I'm worried we will each have individual goals and views and will not be able to settle on a common project that we can advance.Moving from "quick fix" technological solutions that provide augmented management information systems to paradigm shifting socio-technical systems design that create new patterns of human interaction across four levels: the intra-personal, the inter-personal, the trans-species, and the trans-generational.
9
Workflows to Integrate With:Augment brain memory and cognition, Assist as I go about daily life, Assist as I interact with others, Track my priorities, plans, projects, etc. PRepare for upcoming interactions, Act on my behalf as possible, Help me pivot how knowledge is conceived and presented.Ability to import from and export to the web and modern doucment formats, in ways that adds enough meta-data that when re-imported, they documents will have much of the attributes of native DKR documents.Our collaborative workflows that emerge from Team’s consensus adopted structures, processes and information that define the purposes of the workflows.How can we properly integrate very different systems like wikis, teleconferencing, the mouse, versioning, recording, search, ... ... ?Workflows for discovering and enhancing knowledge, ongoingly integrated into cultivated individual and group shareable repositories.Software developmentFrom connective intelligence -> collective intelligence -> collective creativity.
10
What you wish you could do but can’t today with existing tools:The above workflows. Especially shift from document to spreadsheet to outline to data-record to spatially-diagrammed views (and more)Fly and change the views of my information as smoothly as I can change the shape of my imagination. Do with my tools what AI-augmentation will accomplish.
Sophisticated software tools intended for mass use are too often frustrating to use.Toss a yummy info item over my shoulder and know that it will find a place there and be contextually related to all the other stuff there and around me.Have all documents in the software development process (e.g. requirements, marketing, project management, issues, code, tests, documentation, publications) in a single collaborative environment that shares common linking, versioning, permissions. You should be able to "surf" from brainstorming to high level docs to requirements to code to bugs to documentation in a single environment.Intuitively connect to a smart network of people and projects that provides push connections to me relating to my various project interests and objectives.
11
What do Tools do to you today that you wish they didn’t do?Each specialize their "document format" so that it is impossible for OTHER TOOLS to understand that managed by each tool. Doug had a view of knowledge all sharing a single repository and representation, and multiple tools each able to act and deliver value in that shared repository. The TOOLS ought be subservient and secondary to thte knowledge representation. Today we have the opposite.Too limited.Consume way too much low-value and duplicate time and resources.Disrupt my train of thought, fractured interface. They're application-driven, rather than being context-sensitive.They don't integrate well and they distract from getting things done with "how to use" questions.Get me distracted into their implementations.Have separate interaces, command structures, formats, and repositories.Create over-structured and constrained workflow processes.
Create under-conceptualized and constricted design environments.
12
What busy work do you wish you didn’t have to do ever again?Look for or enter the same information more than once. Transcribe audio or visual notes / record to text or diagrams. Manual filing of objects into folders (or manual tagging). Scanning paper documents to create online versions of them.Too much clerical work.The duplicative work that today's non-universal tools require to achieve my objectives.
Organize things into folders or categories.Convert document formats.Type.
13
Link Considerations:Links are paths. As Doug recognized, paths can be specified in multiple ways (eg go to that object, then "turn that way" - relative to object - and go to "that object", and then take "this part" of it...) Links ought be again that flexible. Also, objects need to persistent addressability. IE Nothing gets deleted. Nothing gets "moved".There needs to be a huge topic of itself. We currently only have directions, not links. We also need to better understand and implement implicit links and other ways to connect information and provide paths between them.Single-click recent-links access (or mind-reading clicks :))Think of all the links that have been mentioned in the discussions so far. Why not collect, organize, and save them?Across documents of all types, from code to everything else. Incorporate versioning in links so you can point back in time.Links would ideally be dynamically updatable, smart, pattern emerging.
14
Document Considerations:Knowledge representation is primary design objective. Tools ought be secondary, and flexible to provide their utility, but not restrict other tools.Documents need to be robust but also extensible, so that anyone can build software which will use all the features in the 'orignal' DKR document and also add to it, without breaking previous compatibilities. This needs to be done via human-readable headers where new features are explained.The elimination of documents and the emergence of knowledge flow and stratification access, in any chosen media.
Needs to support formats developers are comfortable using today (e.g. code formats, xml, json, slides) and output experiences end-consumers want (e.g. slides and graphics, wysiwyg formatting)Multi-modal documentation, i.e., capable of shifting/morphing and being expressed through any of the five senses (as an ideal to be approximated).
15
Context Considerations:Eventually, tho today we work on desktops / laptops, devices will inevitably become more mobile and more body-accessorized. "terminator" or "minority report" visualizations will become the norm, and then obsoleted as we get more direct neuronal or synaptic cyber connections.Context shelling - the clear access to my personal defined contexts readable and understood by my next-generation Avatar who mediates by communications for recipient user's Avatar's recontexting for the user's contextual understanding.
Context as necessary 4th dimension (ie, context + subject predicate object => quadruple/tetrahedron). Context as framing. Dynamic (re) contextualization also as what intentionality (as in a Quest) delivers.Sensitivity to temporal, cultural, linguistic (semiotic), level of expertise, technological factors.
16
Collaboration Considerations:The smarter one thinks one is, the harder it is for others to collaborate with one :)Flexible collaboration interactions so different users can effectively collaborate in different ways.Make it finally work.
Pattern: 1) Self - one's own highest future possibiity | 2) Other - hearing/seeing that in other | 3) Group - open to seeing its highest future potential: letting come / group innovationVersioning, sharing, realtime collaboration.Participatory, interactive, co-creative, experiential.
17
Security / Privacy Considerations:Nothing gets deleted. Everything is attributed, and access is granularly controlled, by person, group, or function.Full history and secure identity.Everything encrypted with unbreakable methodologies.
Permissions for groups, control of visibility and read/write privilegesUser defined. Explicit, overt, transparent, and easy to understand.
18
Publishing Considerations:PAGE notion ought be obsoleted. "knowledge object" or "knowledge chunk" needs to evolve into a thing.Publish as richly as possible. Avatar mediated content that is published using knowledge delayering methodologies that support omnidirectional queries.
Engelbart spoke in terms of addressable information resources, with no particular definition: could be an image, could be a sentence, could be a paragraph.Documents accessible from anywhereCopyleft (and other CC standards).
19
Do you agree that a core UX operational challenge is to resolve is how to ‘zoom’ / 'fly' in and out of (‘navigate’) information structures.Yes.Yes.Partially YesIt's core but not the only core challenge.I think of it more like surfing that zooming, but ok. I agree with Adam Cheyer on this.
20
Amazing Interactions:How shared understanding creates love between us. That will be amazing.Oh, let us keep dreaming here...To be contextually understood.
Those which provoke mental orgasmsFeed wikipedia into Watson. Or feed a collaborative group's collected materials into Watson. Then attach a voice assistant (like Siri for example) for interaction. Now users could have a conversation with a system that knows a lot about things they want to discuss. Magical (with unicorns, if possible).
21
Server/Local Considerations:Servers are irrelevant. They are merely compute resources. OBJECT IDENTITY is what needs to have persistent presence. Objects include entities (people, organizations, etc), knowledge objects, event objects, place objects, etc.We should not have to rely on servers but we also need the system to be online and available and up to date for everyone as much as possible.Perhaps becoming an obsolete consideration.
Server is first importance (because documents should be accessible from anywhere), but local/offline syncing is a nice feature.
22
Other (including wild dreams):Dispel fear and create love, at scale. That is my wild dream.To work with full-time collaborators, co-sharing to build all of our consensus-approved projects, using agile methodologies to drive timely performance. DKR2 Futures - my thoughts and convictions
23
In order to keep the visual metaphor coherent we need to decide where the rest of the information is, beyond what is right in front of the user. The initial suggestion is that it is behind the screen.Everything will bootstrap / iterate / improve.Behind the screen. How to differentiate between intra-DKR and extra-DKR will be an issue to discuss thoughI think this is a useful (and ancient) metaphor, especially re creating fusion views (screens distributed across multiple device types) from disparate sources shaped to and by team intentionality. Beyond this it is also useful to consider that the team is embedded in the screens it creates, and that it is acting individually and collectively from the framings of such an ecosystem.Well, cloud-based, yes? Non-local and multi-modal in terms of storage, access, and interface.
24
Any issues with the Core Attributes listed in the Core Attribbutes & Provocations document?Everything will bootstrap / iterate / improve.No. not for nowI expect that some of the assumptions will evolve or disappear when the future scenarios are developed and considered.
25
This spreadsheet is for your comments on the DKR2 Core Attributes & Specifications document. The Definition of DKR2 and the main project website is http://dkr.space
26
27
Loading...
 
 
 
Sheet1