422 Matching Annotations
  1. May 2016
  2. Apr 2016
    1. If, at the dawn of the web, I was to take a list of things the web would bring about and show them to a researcher, they might disagree on the level of interest people would have in things (what’s with the cat pictures, spaceman?) but there’d be little there to surprise them except for one item: the most used reference work in the world will be collaboratively maintained by a group of anonymous and pseudonymous volunteers as part of a self-organizing network.

      It would be nice if on this day, as we marvel about the rise of Wikipedia, we could turn some of our attention to the Wikipedias of the future. Where are opportunities for this mode of collaboration that we’ve missed? Why are we not confronted by more impossible things? How can we move from the electronic dreams of the 1970s to visions informed by the lessons of wiki and Wikipedia? Some people might think we’ve already done that. But I’m pretty sure we’re barely getting started.

  3. Jan 2016
  4. Dec 2015
  5. Nov 2015
  6. Aug 2015
  7. Jun 2015
  8. May 2015
    1. I first discovered the power of collaborative annotation

      Collins actually imagines a moment of shared marginalia in his poem. In a copy of A Catcher in the Rye that he borrows from a library as a boy, he finds the following: “Pardon the egg salad stains, but I’m in love.” The young Collins imagines the note to be written by a beautiful girl and feels himself in a sense falling in love with that other reader. Though we need not develop a dating service out of the modern technologies that allow for social reading, we can at least see the humanity that can be shared in the margin of a digital page: the teachable moments, the conversations that might occur. We have glimpsed such moments on other social media like Twitter and Facebook, but I argue they lack the depth of annotation, which brings together text, comment, and now, readers.

  9. Apr 2015
    1. Sixty percent of those surveyed said too little emphasis is placed on collaborations with other learners outside the classroom, while 46 and 40 percent, respectively, said there should be more emphasis on group achievement and working in teams. The two soft skills respondents said were important most often were problem solving, at 96 percent, and the ability to collaborate, at 95 percent.
    1. The blog post in which Ben Balter proposes that term was unpublished when I read it. But since the blog is hosted on a public GitHub repository I could not only read the post in draft form but also follow the discussion with invited reviewers and observe how that discussion influenced the draft.

      With Hypothesis this kind of thing becomes available for /any web page/.

  10. Mar 2015
  11. Feb 2015
  12. Jun 2014
    1. Technology leadership is not defined by patents, which history has repeatedly shown to be small protection indeed against a determined competitor, but rather by the ability of a company to attract and motivate the world’s most talented engineers. We believe that applying the open source philosophy to our patents will strengthen rather than diminish Tesla’s position in this regard.

      "Technology leadership is....defined by...the ability of a company to attract and motivate the world's most talented engineers."

      The key components of this applied "open source philosophy" seem to be about increasing input, visibility, and collective motivation by taking fear out of the interaction equation.

  13. May 2014
    1. Collaborate for God's sake!: EVERY organization dealing with data is dealing with these problems. And governments need to work together on this. This is where open source presents invaluable process lessons for government: working collaboratively, and in the open, can float all boats much higher than they currently are. Whether it's putting your scripts on GitHub, asking and answering questions on the Open Data StackExchange, or helping out others on the Socrata support forums, collaboration is a key lever for this government technology problem.

      Collaboration is clearly key, but it's not obvious what that means. The suggestion here is a good first step in an organization:

      • scripts on github
      • asking and answering questions on stackexchange
      • and (for data) joining the Socrata support forums

      What does it take to get organizations on this path?

      And what steps are next once the organization has evolved to this point?

  14. Feb 2014
  15. Jan 2014