Always interesting to read how Engelbart builds organizational schemes which build off of themselves, very very meta

Under review at Meta-Psychology. Contribute with peer review here. The editorial process can be followed at:

https://osf.io/s6yr4/

Unless, for example, annotation was baked into the platforms, and offered any reader the opportunity to collaboratively discuss.

Well, here I am on YouTube, watching a Hypothes.is video and commenting using it. I'm annotating YouTube, which is pretty open in terms of what people can say in the comments, and almost universally derided as being where the dregs come to say whatever they want, bringing civil discourse along for the ride.

I believe in freedom of speech and eliminating censorship, but what is it about this new platform that will prevent the problems of the old? Here we are, at the intersection.

good meta-review -> weight more heavily from reviews, and why

good meta-review: -> consider all of the reviewers' opinions

Like this!

For a blog post commenting on an earlier draft of this article (many points raised remain relevant) see here.

Hello Hypo users. I've never really used it much, but was one of the backers when it launched its kickstarter in 2011. Very good to see it in action here, so I'm going to start using it to engage in conversations in the general area of open science.

If you see this comment, please take a moment to register at http://hypothes.is and say hi, even if you don't want to engage in thematic discussions about our paper :)

Really? I think they all had to move to California.

Pienso en cómo otros lenguajes y tecnologías se encuentran en Grafoscpio: Pandoc, Lua, Smalltalk, lo escritural, lo hacker y en la deconstrucción y diálogo que favorece esta herramienta, que otras maneras no logocéntricas están por venir.

¿Metaherramientas para metaculturas?

Para compartir el comienzo del Data Week.

Como la tecnología nos cambia, cambiamos la forma de cambiarnos.

el cuidado se puede estructurar en el diseño de herramientas y equipos a través de lo que denomina «presenciación” (presencing), un concepto relacionado con la noción del diseño transparente de las interfaces tecnológicas que es clave para la incorporación en las herramientas de hábitos ecológicos a través del diseño para transformar nuestras acciones rutinarias en formas de comportamiento ecológico; esto ha de lograrse mediante la incorporación de ‘guiones’ en el diseño de productos. De esta manera los diseñadores tendrían que ir mucho más allá del objetivo de satisfacer las necesidades de los usuarios para articular, de formas novedosas, las preocupaciones y deseos de una colectividad. Las nuevas rutinas encarnadas se volverían lentamente colectivas y transformarían, eventualmente, la conciencia social y las estructuras institucionales. [...] El enfoque, sin embargo, sigue siendo básicamente teórico y no aborda, explícitamente, la dimensión política.

Esto pasa en alguna medida con Grafoscopio, pues debido a su caracter de metasistema y su condición de objeto activista, embebe prácticas referidas a la disponibilidad permanente del código fuente, tanto de la herramienta, como de los escritos creados en ella y ejemplifica otras ecologías del conocimiento, asociadas al conocimiento como bien común.

La comunidad de práctica alrededor de Grafoscopio comparte, deconstruye e incorpora dichas formas de entender y ser, de modos progresivos, configurando una identidad propia, que es distinta al grueso del hackerspace. Una ventaja de nuestro enfoque es que lo político es explícito y la teoría y la práctica dialogan en él a través de dispositivos digitales hacktivistas..

La idea de meta-prototipado: prototipar la construcción de prototipos, implicaría el código fuente de las prácticas de prototipado y los prototipos mismos, como menciono en la primera parte de la tesis.

This is a pretty useful example of a paragraph with subtext, don’t you think? Could easily imagine future readers and annotators coming to this passage and scratching their heads for a minute while looking at the date. What happened nine months before June 2017? Living outside the US, it took me a few seconds to guess it (and my guess may be wrong). Of course, Martha was “playing for the audience” (though DoOO is having an impact outside the US). There’s indeed a shared understanding that events in the political arena may be relevant in our work on digital literacies.

Therein lies the rub. Especially if this is to be “easy”.

Whaa..? This sounds seriously hard. But remarkably clever.

Which is probably why @judell’s tate doesn’t show up in Chrome on my system and there’s weirdness with the scrolling once we accept to load unsafe scripts.

Speaking of which: https://hyp.is/RmUKwLvpEeezPrvjHE4Lwg/wisc.pb.unizin.org/objectivists/chapter/lorine-niedeckers-blackhawk-held/ via https://docs.google.com/presentation/d/1JoWwyQMpX8ge9Oxk3o3reECVfiJJ6SvB6zPzUbgDDt8/edit#slide=id.g2293d0c2ef_0_69 Gives:

http://media.sas.upenn.edu/pennsound/authors/Niedecker/Niedecker-Lorine_08_Foreclosure_Factory-School-Archive_11-1970.mp3

Ha! So that’s where the comment about Rory McGreal should come in.

Hence the need for #OpenAnnotation to pair up with some of the other opens. Hypothes.is people are doing their part, but still.

Years ago, link suggestions were pretty high on my wishlist for WP. Did notice early implementations of this feature but haven’t used the improved version. It does sound like the current version is pretty useful and can lead to something interesting. Might also work well with annotations, come to think of it.

A literal and more general question.

Roger on the pattern of productizing scholarly workflows.

Respect.

결국 메타언어에 존재하는 정보를 프로그래밍 언어에 합리적으로 추가하면, 더 유용하게 사용할 수 있다.

Corder is arguing that we are, each of us, an argument. That is hard to argue with.

Interesting how they see this fitting in with their mission.

An annotation about annotation.

An annotation about annotation about annotation.

We learn by doing. (And annotations do work on the text version. Neat!)

Didn’t expect to find [h] embedded here. Problem is, it doesn’t allow for annotations of the actual content.

Ah, so quizzes are fair for Rhetoric, I see.

"Blueprints for the future are a fool's errand" - Ron Swanson

"Stop being meta" could be applied in some sense to meta systems like Smalltalk and Lisp, because their tendency to develop meta tools used mostly by developers, instead of "tools" used by by mostly everyone else. Burring the distinction between "everyone else" and developers in their ability to build/use meta tools, means to deliver tools and practices that can be a bridge with meta-tools. This is something we're trying to do with Grafoscopio and the Data Week.

Oh yes, many more! (Was actually looking for a list.)

Ha! The Chronicle’s summary framed these categories somewhat differently. Interesting. To me, the “application” part is really about student retention. But maybe that’s a bit of a cynical reading, based on an over-emphasis in the Learning Analytics sphere towards teleological, linear, and insular models of learning. Then, the “representation” part sounds closer to UDL than to learner-driven microcredentials. Both approaches are really interesting and chances are that the report brings them together. Finally, the Chronicle made it sound as though the research implied here were less directed. The mention that it has “the potential to influence institutional practices and interventions” may be strategic, as applied research meant to influence “decision-makers” is more likely to sway them than the type of exploratory research we so badly need.

Also applies for sensible & concerned humans, which are worried about their own relation with the planet and other beings on it, despite of not being gods (or aspiring to be). On the case of tools for understanding and metatools for improving those tools, again Perfection & Feedback Loops, or: why worse is better seems enlightening, particularly in the context of Smalltalk legacy. Grafoscopio could make a humble contribution on the seeing, understanding and debating part

Will 2017 be “the year of annotations”?

Sounds like a description of Shepazu’s Annotation Architecture.

Cool thing is. Udell and the gang are pretty open to suggestions, it sounds like. At the same time, it’s quite possible that webmentions wouldn’t fit in their overall vision of the tool.

Had missed this announcement. The annotation scene has this interesting ambivalence between being old and new, forward-looking and somewhat nostalgic. Wish Diigo were forward-looking enough to get into Open Annotations.

This pithy statement brings together all sorts of previous annotations. Would be neat to map them.

Kind of surprised not to see other [h] annotations, here.

Shoutout to h?

Flattery will lead us nowhere… But it’s still a warm and fuzzy feeling to be in such illustrious company.

Obvious case for h. Imagine the possibilities of linked open data used in annotating presentations which would be part of scholarly books along with all the necessary material? The mind wanders…

Funny how frequently this terms comes up, when talking about Genius. The difference between annotation platforms is significantly a matter of usage. Usage of Genius has a lot to do with snarky comments made by “the smart kid at the back of the class”. My perception of Hypothesis is that it’s much more oriented towards diversifying voices. But that has less to do with technical features of the platform than with the community adopting it.

Just got in touch with @DoyleOwl. Neat approach to annotation. My sense is that Genius can have a useful effect similar to that of those programmes using basketball to keep kids off the streets.

Glad this was mentioned. To the Eric Raymonds of this world, such a response sounds “perfectly legitimate”. But it’s precisely what can differentiate communities and make one more welcoming than the other. Case in point: Arduino-related forums, in contrast with the Raspberry Pi community. Was looking for information about building a device to track knee movement. Noticed that “goniometer” was the technical term for that kind of device, measuring an angle (say, in physiotherapy). Ended up on this page, where someone had asked a legitimate question about Arduino and goniometers. First, the question:

Trying to make a goniometer using imu (gy-85). Hoe do I aquire data from the imu using the arduino? How do I code the data acquisition? Are there any tutorials avaible online? Thanks =)

Maybe it wouldn’t pass the Raymond test for “smart questions”, but it’s easy to understand and a straight answer could help others (e.g., me).

Now, the answer:

For me, google found 87,000,000 hits for gy-85. I wonder why it failed for you.

Wow. Just, wow.

Then, on the key part of the question (the goniometer):

No idea what that is or why I should have to google it for you.

While this one aborted Q&A is enough to put somebody off Arduino forever, it’s just an example among many. Like Stack Overflow, Quora, and geek hideouts, Arduino-related forums are filled with these kinds of snarky comments about #LMGTFY.

Contrast this with the Raspberry Pi. Liz Upton said it best in a recent interview (ca. 25:30):

People find it difficult to remember that sometimes when somebody comes along… and appears to be “not thinking very hard”, it could well be because they’re ten years old.

And we understand (from the context and such) that it’s about appearance (not about “not thinking clearly”). It’s also not really about age.

So, imagine this scenario. You’re teacher a class, seminar, workshop… Someone asks a question about using data from a device to make it into a goniometer. What’s the most appropriate strategy? Sure, you might ask the person to look for some of that information online. But there are ways to do so which are much more effective than the offputting ’tude behind #LMGTFY. Assuming they do search for that kind of information, you might want to help them dig through the massive results to find something usable, which is a remarkably difficult task which is misunderstood by someone who answer questions about goniometers without knowing the least thing about them.

The situation also applies to the notion that a question which has already been asked isn’t a legitimate question. A teacher adopting this notion would probably have a very difficult time teaching anyone who’s not in extremely narrow a field. (Those teachers do exist, but they complain bitterly about their job.)

Further, the same logic applies to the pedantry of correcting others. Despite the fact that English-speakers’ language ideology allows for a lot of non-normative speech, the kind of online #WordRage which leads to the creation of “language police” bots is more than a mere annoyance. Notice the name of this Twitter account (and the profile of the account which “liked” this tweet).

Lots of insight from @BiellaColeman on people who do things “for the lulz”. Her work is becoming increasingly relevant to thoughtful dialogue on annotations.

Same experience, even in the Genius guidelines. The tool’s affordances (and name) revolve around snark. In the abstract, there’s nothing wrong with that. We need spaces for people to have fun, even if it’s at the expense of others. But the startup is based on a very specific idea of what constitutes useful commentary. That idea is closer to pedantry, snark, intellectual bullying, and animated gifs than on respectful exchange.

That part never worked. But maybe these annotations will? That’d be neat.

It may annoy many, but overtagging can be playful.

We’re here! We’re always here. You can hide us, but we’re in your webpages, annotating away.

In my wishlist to Jon Udell (still in draft), these two modes can be separate phases with Hypothesis. But in reverse order. First pass is the distributed commentary about the whole piece, similar to social bookmarking and potentially affording a very cursory look (or even just a glance at a headline). It says: “Hey, please read this and tell me what you think!” The second pass could be the deep reading, with one’s personal comments visible, but not influenced by other comments. Then comes the “fun part”, which is also a form of distributed commentary, but is much more conversational. “Distributed” might not be as appropriate, though. At least in computer lingo.

This one remains to be demonstrated. As we keep saying, exclusion may be passive but inclusion is by definition active. Open annotations may not sound so exclusive for those who appropriated it as a technology, the same way literacies are often taken for granted. But we often tend to take “democratization” as a given.

Despite an important continuity.

Could soooo imagine a presentation on using #Hypothesis with #PressBooks!

Just got to think about our roles, in view of annotation. Using “curation” as a term for collecting URLs sounds like usurping the title of “curator”. But there’s something to be said about the role involved. From the whole “guide on the side” angle to the issue with finding appropriate resources based on a wealth of expertise.

Wish [h] had a similar feature. And that NB supported #OpenAnnotation.

Sounds like something interesting for Dr. Jeremy Dean.

Like an algorithmic version of Hypothesis? Is McGraw-Hill part of the Coalition? Looks like it isn’t. Is it a “for us or against us” situation?

Oops! Started annotating the Forbes version but this one might be better (no preload). Wish I could transfer my annotations from one version to the other…

Useful list, almost a roadmap or set of scenarios. The last two might be especially intriguing, in view of the Semantic Web.

The “Open World Assumption” is central to this post and to the actual shift in paradigm when it comes to moving from documents to data. People/institutions have an alleged interest in protecting the way their assets are described. Even libraries. The Open World Assumption makes it sound quite chaotic, to some ears. And claims that machine learning will solve everything tend not to help the unconvinced too much. Something to note is that this ability to say something about a third party’s resource connects really well with Web annotations (which do more than “add metadata” to those resources) and with the fact that no-cost access to some item of content isn’t the end of the openness.

Sometimes an annotation is just an annotation.

Let’s imagine that future. What else could [h] do, if we were to make a wishlist?

Chain of attribution, as @Shepazu would have it.

Will our annotations issues be solved, in nine years?

Interesting that SVG guru Shepazu would talk about Hypothes.is…

Besides the piece’s content, the interactions which happened through a layer of Diigo annotations were quite interesting.

The future of news is still about journalism? We can annotate any content. This piece makes it sound as though journalism should become even more controlling.

Wonder how Colwiz compares to Annotator.js …

Tell that to Genius!

Indeed! The only tricky thing is the current bookmarklet, but this can be integrated into sites themselves.

what is this resource? what does it do?

Altmetric guidelines for optimising web pages

This documentation describes the technology behind indexing of websites with scholarly articles in Google Scholar. It's written for webmasters who would like their papers included in Google Scholar search results. Detailed technical information is helpful if you're trying to fix an error in indexing of your own website, or you need to make sure that your article hosting product is compatible with Google and Google Scholar search services.

I need a way to add tags to a document that will apply to all annotations in a particular document (except where explicitly canceled).

The problem is that I often want to query all annotations related to a specific document, collection of documents, or type of activity.

Type of activity requires further explanation: Given a document or collection of documents I may annotate the document for different reasons at different times.

For example, while annotating the reading materials, video transcripts, and related documents for the CopyrightX course there are certain types of annotations that may be "bundled together" so that when I search for those things later I can easily narrow my searches to just that subset of annotations; but at the same time I need a way to globally group things together.

While reading judicial opinions the first activity/mode of interaction with a particular document may be to identify the structure of the judicial opinion (the document attached to this annotation describes the parts of the judicial opinion I might want to identify: *caption, case citation, author, facts of the case, law of the case, disposition, concurring and/or dissenting opinions, etc).

The above-described mode I may use for multiple documents in one session related to the course syllabus for the week.

To connect each of these documents together I might add the tags: copyx (my shorthand for the name of the course, CopyrightX), week 1 (how far into the course syllabus), foundations (the subject matter in the syllabus which may span week 1, week 2, etc), judicial opinions (the specific topic I am focused on learning at the moment (may or may not be related to the syllabus).

Later on another day I might update my existing annotations or add new ones when I am preparing to study for an exam. I might add tags like to study, on midterm, on final to mark areas I need to review.

After the exam I might add more tags based on my test score, especially focusing on areas that received a poor score so I can study that section more or, if I missed some sections so didn't study and it resulted in a poor score in that area, add tags to study for later if necessary.

I have many more examples and modes of interaction in mind that I can explain more later, but it all hinges on a rich and flexible tagging system that:

• allows tagging a document once in a way that applies to all annotations in a document
• allows tagging a session once in a way that applies to all annotations in all documents connected to a particular session
• allows tagging a session and/or a document that bundles together new tags added to an annotation (e.g. tags for grammar/spelling, tags for rhetological fallacy classification, etc)
• fast keyboard-based selection of content
• batch selection of annotation areas with incremental filling-- I may want to simply select all the parts of a document to annotate first and then increment through each of those placeholders to fill in tags and commentary
• Mark multiple sections of the document at once to combine into a single annotation
• Excerpting only parts of a text selection, but still carry the surrounding textual context with the excerpt to easily expose the surrounding context when necessary
• A summary view of a document that is the result of remixing parts of the original document with both clarifications or self-containing summary re-writes and/or commentary from the reader
• structural tagging vs content tagging

Towards the end of our last conversation the text following "common appropriation" seemed an interesting place to dive into further for our future discussions.

I have tagged this annotation with "meta" because it is a comment about our discussion and where to continue it rather than an annotation focused on the content itself.

In the future I would be interested in exploring the idea of "annotation types" that can be selectively turned on and off, but for now will handle that with ad hoc tags like "meta".

Note that this disclaimer only says the document should not be used for citation purposes, but doesn't say we can't use it for annotation purposes like testing out the Chrome PDF.js + Hypothes.is extension! :)

You can install the extension from the Chrome Web Store with this link:

https://chrome.google.com/webstore/detail/pdfjs-%2B-hypothesis/bipacimpfefoidapjkknffflfpfmjdog/related