3 Matching Annotations
- Jun 2024
-
-
you can take a lot more than you are and have a lot more information
for - adjacency - open source - Stop Reset Go complexity mapping - objective - Nora Bateson comment on more information - diversity - Indyweb/Indranet - progress trap mitigation
adjacency - between - Nora Bateson comment - Stop Reset Go complexity mapping<br /> - open source - progress trap mitigation - Indyweb/Indranet
- adjacency relationship
- When Nora talks about the
- oversimplified,
- reductionist
- problem-solving approach that most of modernity employs to tackle wicked problems,
- it boils down to oversimplification.
- There are usually far more causes and conditions to a problem than are known to construct the solution
- In Deep Humanity praxis, this is how we get into progress traps, the shadow side of progress
- The Stop Reset Go complexity mapping system is designed to reveal greater information by
- creating a space for diverse perspectives to systematically engage in addressing the same wicked problem
- This system must be open source in order to create the space for maximum diversity
- The Stop Reset Go process is specifically designed as a workspace for diversity for the purpose of
- mitigating progress traps and
- helping find more effective ways to address wicked problems
- This is done by using Trailmark Markin notation within the Indyweb/Indranet people-centered, interpersonal software ecosystem
- When Nora talks about the
- adjacency relationship
-
- Feb 2021
-
github.com github.com
-
Source maps eliminate the need to serve these separate files. Instead, a special source map file can be read by the browser to help it understand how to unpack your assets. It "maps" the current, modified asset to its "source" so you can view the source when debugging. This way you can serve assets in development in the exact same way as in production.
-
- Feb 2014
-
github.com github.com
-
For example, imagine you are annotating the second page of a New York Times article. You probably want to see your annotation when you are looking at the article later as a single page, right? Or perhaps you've annotated the HTML for a PLOS ONE article. Wouldn't you like to see those annotations when you are looking at the PDF version of the same article? If annotations were only associated with the URL you happened to be looking at in your browser then the scenarios above would not work, because the documents being annotated all have different URLs.
Publisher Best Practices is a great idea that I would like to see codified in the authoring and publishing tools to make the practices commonplace by default.
I would like to mix PBP with other techniques, though, for richer connection between source and rendering-- I have some source mapping ideas that make it possible to keep annotations linked even as the original source is edited over time.
-