I have written a lot lately about an instructional tactic I call layering (search this blog for the layer tag). What I mean by layering is the use of a service that allows an educator or designer to add elements such as highlights, questions or annotations on top of an existing website or online video. Just to be clear because this issue bears on the following comments, the way this work is that the designer enters the address of the content to be commented to a different service that requests the content from the original provider, allows the educator/designer or student to make additions on top of the original content, and saves a way to represent this combination. There is no actual change to the original content, the original content is served each time the composite is requested, all content including ads is served, and the composite is only visible to viewers requesting the content through the layering service.
My writing has focused on the educational potential of such services. The idea is that much of the content existing on the Internet was not designed as an instructional product. Educators/designers can add elements that help learners process this content for understanding and retention. In addition, it can be beneficial for learners to make their own additions (much as you might do while reading a book) for personal use or sharing with peers.
It is important to recognize that the developers of these layering services may not have these exact goals in mind or they may see their services in a broader way. I tend to think in terms of educators and students. The developers of these services may have a perspective closer to “annotate the web”. The idea is each of us can markup public documents as a way to provide input or challenge to the positions taken by original authors.
What has surprised me is that there is a growing backlash against these layering services. I can kind of understand the position of those who are concerned because it seems similar to the anger present in those who resent viewers blocking the ads inserted in content. I can understand the position – you do not have to view the content I created so please view it as I intended.
Another way to understand this backlash is to note that many bloggers or YouTube creators may turn off comments. Some may not want to be criticized, but many have experienced attacks or negative comments that go well beyond just disagreeing with positions taken.
I am listing two sources explaining the opposition to group annotation. One from the Chronicle of Higher Education and one from blogger Audrey Watters. I always recommend that my readers use the links I provide in case my summary of the positions taken by others are simplistic or simply wrong.
There is something kind of interesting about the way we write and link in addressing this specific situation. I see the educational value in layering and in a way I am suggesting that layering should be continued. In a way, I am doing something very similar to what layering accomplishes although in a less precise way. I am taking the work of another and arguing that the position taken fails to see another perspective. I would not have been allowed to do this as an annotation or as a comment, but I am doing pretty much the same thing. I also remember in the early days of the web that some objected to others linking to their content.
I hope there is a solution to this dilemma. It makes no sense to me that the connection of ideas on the web would require the consent of all involved. This is not the way the web has evolved and it is not the way those of us who have worked in academia have always done our work. We cite and connect, but we do not seek permission. Audrey Watters mentions a script she uses to block a specific annotation service (hypothes.is). If this type of thing were widely available, it might be one solution.
I do see public annotation (when connected to the same layering service) and educational layering (offering the composite to specific students) as different. Like so many tools for working online, the same tool can be used in both ways and I guess flexibility can lead to problems.