 Hi, I'm Heather Staines, the Director of Partnerships for Hypothesis. Thanks for joining our first webinar in a series for publishers. I'm here today with our founder and CEO, Dan Whaley, along with our colleagues, Nate Angel and Peg Fowler, who will be helping out on webinar logistics. If you have any suggestions for future webinar ideas, please feel free to put them in the chat. We'll be collecting them throughout the course of the webinar today. And at the end, we'll do a quick poll to see what you might like to hear about from us next. This webinar is being recorded and will be accessible later from Hypothesis website publishing page. Before we get started, we just have a couple of housekeeping items because we have so many attendees today, we've placed participants on mute. We'd like you to use the Q&A function at the bottom of your screen if you have any questions. We'll be monitoring that throughout the course of the webinar and we'll take time at the end to respond. You can also use the chat feature. You can chat to everyone if you'd like to introduce yourself, for example. Or you can chat to just the panelists in the event that you have any technical difficulties or anything like that. Here's a look at what we'll go over today. First, we're going to talk about 10 questions that you should ask if you're considering annotation. Then Dan will give a quick overview of Hypothesis. I'll talk a little bit about the value proposition for publishers and then do a live demo. I'll tell you a little bit about how to work with Hypothesis and then we'll take some Q&A at the end. Before we get started, I thought it would be informative to do a quick poll to gauge how familiar you are with annotation technology. Next, I'm going to hand it over to Dan. Thanks, Heather. Hey, everybody. It's great to have you all with us today. The topic of the webinar obviously is 10 questions that you should be asking about providers and platforms of annotation. My colleagues will drop a link to this poll in the chat. I won't go through all these questions. We're specifically, but we'll be addressing each of these points throughout the presentation as we go along and happy to field questions about them later. I'll give you a little bit of background on Hypothesis. First, we're a nonprofit, as most of you probably know. We've chosen that model for a very specific reason, which is that we think that in order for this technology, this new paradigm to be successful, that it needs to be stewarded by an organization who is able to align with the interests of users or the interests of publishers and so forth over the long term. The web has been successful specifically because of that alignment by the individuals and organizations that were involved at the beginning and as successful as a result of that. We are funded through grants from a variety of foundations, the Melon Foundation, Sloan Foundation, Omidyar Network, Helmley Trust, and the Shuttleworth and Knight Foundations. We are mission-driven. Our goal is to focus on bringing the standards and the software necessary to bring this capability forward to the world and also to provide an instance of it as a service, but not the exclusive one. This is all we do here at Hypothesis and we consider ourselves to be a mission-driven organization. We have a team of 16 full-time staff that are dedicated to annotation. That's all we do here and the roughly split between technical staff that help build the software and program staff that bring it forward. Our vision is a unified, interoperable architecture for annotation across all scholarly literature built in to the very fabric of the web. This architecture we believe should be built as layers so that over any given document, in any given article, you're able to see a variety of different kinds of notes for a variety of different use cases, notes that might be post-publication conversations for the general public, layers that might be private layers where a classroom is teaching an article in private so that the annotations are a discussion just for those students, expert communities that might be annotating for a particular purpose for their audience, and also layers that are perhaps produced by the publisher or authors or reviewers or community members around the article that are available at publication. Each of these layers potentially could be hosted on a different server with the annotations coming from a different provider. This really gets to the heart of this as a web standard architecture. Just like in your web browser, different tabs might represent pages coming from different servers. In our view, the annotation client is simply a uniform structure to bring different kinds of annotations for different purposes into the context of the page wherever you are. This technology, this architecture is grounded in a new web standard that passed with full approval of the W3C, the standards body for the web in February of this year, with more support than for any other standard before it in W3C history, so there's a very strong groundswell of support behind web annotations and it's really helped to create a tremendous amount of momentum. We are fundamentally focused in bringing collaboration around knowledge and around scholarly literature to the place where it resides. The publishers platform as well as on other elements of the wider web, as most of you know, one of the fundamental values of hypothesis and the architecture we've chosen is that it works everywhere. While it benefits from being implemented on publishers content and being native and default to that content, if users want to annotate in other places, they can bring that capability into the web now through plug-in or extension and later through the native functionality capability in browsers itself, which is one of the reasons why it was so important that the W3C adopt this. In support of this view in 2015, we announced a coalition, which is now numbers over 80 of the world's leading academic publishers, platforms and libraries that have made a commitment to bring web annotation to their scholarship, to their content, to their platform over the next several years. We also run a conference every year called I Annotate, which just happened in May of this year in San Francisco, where developers, publishers, advocates, standards, individuals come and present over a series of a couple of days. The community aspect of annotation is one of the things that we focus on the most and one of the things that we think is most important to its long-term potential success. As far as how we work with organizations that want to implement annotation, we characterize it as a member-based model. For us, you all represent potential partners that can help together with us bring this capability to your platforms, to your users in order to benefit them, in order to add powerful tools to their capability in order to bring an enhanced kind of content and richness to your publications. As I mentioned, Hypothesis runs an annotation service ourselves with now over a million and a half annotations that have been made by over 100,000 users. It's interesting to note that only about 20%, 4% of annotations are public, whereas 50% of those annotations take place in private groups, for journal clubs, classrooms, co-authors working on a paper, and about the last 25% of those annotations are personal notes or private notes that people are taking for their own individual benefit. So for that, I'll turn it back over to Heather. Thanks so much, Dan. I want to tell you a little bit about the value propositions for publishers. While we've been speaking to publishers, we've heard lots of interesting use cases for annotation. We want to talk to you about a few of them here today. The first is enabling post-publication collaboration layer using annotation. Remember that Hypothesis can be used anywhere on the web. Here's an example of graduate students and their professor discussing a piece of content at the University of Texas at Austin. In this particular case, it's a monograph from the University of Michigan Press. Some publishers that we've spoken to want something a little bit more custom. They want their own annotation layer. We call this publisher groups. The first publisher group is coming later this summer from eLife. Publisher groups are publisher branded and moderated groups that are publicly visible by default when a user lands on your content. The publisher can decide who has the authority to make annotations and who has the ability to read them. It's very, very flexible. Here's an example of how your publisher layer can be made visible on your page. Through a button, the button can show that annotation capability is possible and even how many annotations exist on an article. The end user clicks on the button and the publisher branded and moderated layer appears by default at the top. In this case, the publisher is elected to have annotation accounts auto-generated for their logged-in users, so there's no need for them to have a Hypothesis account or to navigate a way to create one. They can just start annotating. One of the advantages of standards-based and interoperable annotation technology is that annotation clients can see multiple servers and even interact with other clients. In this case, in addition to the publisher layer visible at the top, I can see that there are annotations in the public layer, in a reading group I'm part of, and even in a science class. It's very, very flexible. I can direct my annotations to any one of those given layers. A key piece of Hypothesis architecture is that a private company, a publisher, and a pharmaceutical company, for example, can host their own annotation server, maybe for proprietary reasons to run behind their firewall. Now, this may not be something that you're interested in doing now, but it's good for you to know that this is possible. You won't be locked in with one company forever, particularly a for-profit entity that could eventually be sold to one of your competitors. The second use case we hear about in annotation most frequently is annotations as new content. Hypothesis can plug into existing publisher workflows so that publisher staff, authors, and other experts can use annotation to create new content. This new content might be author updates. It might be connections to additional resources. It could be expert commentary. All of it will live by default in the publisher controlled layer. Here's an example of expert commentary in this case on an article in the Washington Post. Remember, you can use Hypothesis anywhere. As you'll see in a moment in the demo, it's really easy to connect articles through direct linking. You can also add media, such as images and video, again, connect it right to the article. It's very, very useful. The third case we're hearing about from publishers is the use of annotation in peer review so that reviewers can make inline comments on documents and publishing staff and authors can reply inline on those same documents. You can use it for single blind, double blind, and even open peer review. Some publishers have indicated that they want to make peer reviewer summaries visible as additional content. Here's a screenshot of the eJournal's Press peer review workflow, in this case on an AGU journal of geophysical research. Now I'm going to do a demo. Here I'm going to do a quick live demo of the features and functionalities of Hypothesis. I'm a reviewer looking at an article, vulnerability to earthquake hazard. As I'm going along and doing my research, I come across something that's interesting that I want to take note of. I simply select the text. Hypothesis will ask me if I want to make a highlight or an annotation. I'm going to select annotation. Now I can make my annotation. This is interesting. I can add a tag. Hypothesis will then ask if I want to post that annotation to the public layer or keep it private just for me. I'll select the public layer. Now I have an annotation that lives right on top of the publisher's content. I can even share this annotation through social media or by email just by grabbing the link from the clipboard. The person that I send it to doesn't have to have a hypothesis account or even know that hypothesis exists. If they can get to the article, the article will open for them. The client will pop out and they'll be scrolled precisely to the annotation that I wanted them to see. It's very convenient for collaboration purposes. Now in addition to annotating on the HTML, annotations also transferred other formats. Let's grab the PDF. Now I mentioned HTML and PDF. We've also completed a project recently with NYU University Press to enable annotation of ePubs. We'll be making an announcement about that in just a couple of weeks. When the announcement is final, you'll be able to annotate on Redium.js and also EPUB.js documents. There's a lot of interest in that from our eBook customers. Now that we've got the PDF opening up here, let's watch for our annotation. And there it is. Now I've shown you how you can annotate to the public layer. You can also create private groups. The way that you do that is by simply selecting New Group. Hypothesis will ask you what you'd like to call the group. I'm going to call mine Earthquake Studies. It's just that simple. Now I have a dashboard for my group. I can see when the group was created, who the members of the group are, and I can use the link over here to invite additional members to the group. Let's go back to our original article. I'm going to continue reading along. Come to something else that I want to take note of. Now, instead of selecting public, I'm going to go ahead and grab my Earthquake Studies group. Now I can make an annotation just for the group. This is interesting. Add some tags. Now I've posted it to my Earthquake Studies group. Someone else from the group may come along and make or apply. I agree. In addition to responding with text, I can also drop in some math. Now I have an annotation with math. Someone else in the group might come along and decide that they would like to respond by dropping in a video. You can play it from right in the sidebar. An earthquake of magnitude 5.6 is... Now, in addition to creating threaded conversations through annotation on top of a document, you can also connect multiple documents across the web. This is the USGS site on earthquakes that have happened recently. Here's an earthquake that I want to take note of. I can drop this into my Earthquake Studies group as well. It follows me across the web. Add some more tags, post it to my Earthquake Studies group. I can now grab the link for this annotation and go back to my original article. Let's edit the very first annotation that I made. I can just drop my link in. Now I have two documents linked across the web. Again, very useful for collaboration purposes. In addition to PDF and HTML and EPUB, you can also annotate data. Here's a CSV file that I was looking at with some information on earthquakes. Let's say I've got a question. Just select the cell, annotate it. I'm gonna drop this into my Earthquake Studies group as well and say I have a question. Is this right? And post it to my group. Someone else can come along and reply. I showed you how to create a group and how to add annotations from all across the web into that group, but I never took you back to the page. Let's check out our Earthquake Studies dashboard again. All of the annotations that I've made across the web have automatically populated here to this page. I can get back to any of my articles by clicking on the arrow, view annotation and context. Also, the tags that I was making, they've accumulated here. I can select a tag and it will be added to my faceted search at the top of the page. So I can just see, for example, the articles that I tagged earthquake. It's a great way to explore and discover content through annotation. If I take off my group filter, I'll be able to see all of the annotations that have been made across the web, publicly at least. I also have an activity page just for me. That's our demo for today and I'm happy to take questions on the demo. I'm at the end. I wanna tell you just a little bit about how to work with hypothesis. Because hypothesis is open source, you can integrate the code on your platform for free. We're permissively licensed and we've got information on our publishing and developers page to help you do that. If you want something a little bit more custom, like a publisher group, we're happy to help you integrate hypothesis. We have a very simple pricing model that's based on the number of documents that you publish annually. If you're working with a platform host, we're already in conversation with them to help you enable hypothesis on your content. We also offer customization to best fit your UI as well as an outreach program that you can use internally and externally to roll out annotation. If you have questions on any of these options, don't hesitate to email me. I'm just Heather at Hypothesis and I'm happy to answer any questions that you might have. If you have any questions that you haven't yet put into the Q&A, please do so now. And remember, we're looking for webinar suggestions for the future. So please go ahead and put those in the chat and in just a moment, we'll be putting a poll up that you can respond to there. But we're happy now to take questions. Nate, are there any questions? There are a couple of questions actually. Rob has asked if the public layer can be turned off when there's a publisher group. I'll take that, yeah. So the way that publisher groups work is that when you have a publisher group over your content, it is the default group. And if the person has not signed in to another annotation server or service, then they won't see any other annotation layers. But if they have signed in, for instance, it could be hypothesis, it could be another annotation service, could be an internal annotation server. They will see the annotation layers that relate to your page, to your publisher page, along with your annotation servers in the same way that you've seen in the demos. So what we try to do is strike the balance between giving publishers control over the layers that are visible by default and in so doing, excluding other layers until the user elects to bring those layers to the content. I'll just keep going through a few more of these. What kind of support is there for applying annotation to images? It's in the W3C spec. It's not supported by hypothesis yet, but it is a frequent request that we get. And there are a number of libraries that are already compatible with the underlying annotation technology that hypothesis is based on that will be incorporating. Our product roadmap is something that we kind of co-construct with partners that are interested in implementing things. If you have a particular functionality that you're interested in implementing or having us support, we'd love to hear from you. I'll also answer a question that Rob O'Donnell put in the chat. Can you comment on the use of authorized experts as a required credential for posting comments on a competing product, similar functionality and hypothesis, warnings about such a system? We have looked at that and I think what obviously what we're all trying to get to is infrastructure that supports high quality conversation. And I think there's a variety of questions about how the best way is to get there. We don't think that it is possible to automatically screen and determine the potential credibility of participants through a system that's imposed by us on your content. The first, by creating publisher groups and giving publishers the moderation capabilities for those, our goal is to put you in charge of who you want to be able to have, make discussions and create annotations over your content in your default groups. For hypothesis, based on the million and a half annotations that we've seen, we're able to maintain a high degree of decorum through the moderation approaches that we take in our system. If we need to develop more automated systems to help screen or pre-screen annotations, we'll do so, but we did not feel that it was important to try to get in front of that with the kind of system that we've seen elsewhere. Heather Blackburn asks, can hypothesis be implemented on one annual issue of a journal rather than the whole site? The answer is absolutely yes. You can implement annotation over as much or as little of your site as possible. We're all, we're very much in favor of experiments too. If you want to try it out in a narrow place and work with us to run a little promotion to see what the response is, we think that's a great strategy. John Abrams asks, Abraham's asked, do the annotation tools allow creating annotation on images and video? It did already answer the question about images not yet and the same goes for video. We hear those requests. We do plan on implementing support for both images and video. We've got some more work to do on different group types and export and more powerful forms of notifications before we get around to those, but those are absolutely things that we'll be focused on and potentially in the next year. Audio annotation support from Allison. Thanks, that would for us falls in the category of streaming media. So for us, audio is a subset of video that absolutely would be something that we will support in the future and thanks for asking that specifically. Daniel Ruiz asks that we would love to help adding the functionality to choose the Spanish language. Just looking forward to know how and when we can do it. One thing that's important to say, the interface already supports annotation in foreign languages including Chinese and Japanese characters. So I can annotate texts including vertical Japanese texts that either in PDF, EPUB or HTML form, and I can add those foreign languages to the body of the annotation. The interface itself is not yet internationalized. We understand that that's a priority and important for the widest possible adoption in different questions or different, I'm sorry, in different countries and we'll be working on that in the next year or two as probably when that's gonna happen. Jason Barclou asks, during annotation, it seems like the text is always highlighted even though only an annotation was done. Can a highlight be turned off? Absolutely, there's a button right on the interface. It's got a little I and you can turn the annotations on and off. We do believe that it's really important for users to be able to get to a clean page. All of the webinars that we do will be recorded and connected to our publishing page. So if you're not able to attend in person on the day of the event, you'll be able to join later. In addition to the webinars, we've got lots of information, toolkits and resources that are available on our publisher as well as our developer page that you can share internally and with your technology partners and users as well. I wanna thank you again for joining us today and mentioned just once more that this will be recorded and available from our page. You can share it and along with a lot of other information available there, including just a brief demo recording if that's what you're interested in. And we'd love to hear from you in the future to continue the conversation. Thanks so much.