 So my name is Josh Hadrow. I'm the managing director of the AAAF consortium. So this is the AAAF community and technology highlight session. So I with my two colleagues here, Glenn Robson and Bego Hearn, are going to go through some of the updates, specifically about the AAAF community groups and the technical specification groups. And we're going to break it up a little bit. We have an hour here the three of us are each going to take a section of these updates and go through them. And there should be a bit of time at the end for questions if folks have them. But by all means, feel free to put in questions as we are talking into the Huvva Chat and platform. So really what this session is about, just to give you a sense of what it is, is to give you a bit of insight into the workings of the AAAF community. There's a whole array of community groups, as well as what we call technical specification groups that do kind of dedicated and specific work of moving ahead different elements of things that need working on in the AAAF community. And so for the technical specification groups, that means quite literally working on something related to the specifications, working on solving technical problems or amending the current specifications to address new user stories, new issues that come up with web standards, things like that. And then the counterpart groups, the community groups, are less, are not charged with changing or addressing the technical specifications, but really are geared toward other aspects. So sometimes it's related to a particular domain or a particular set of ways of working with AAAF. And so that's kind of the bulk of what we're going to go through here today. Just in case this is somewhat new to you, and we're really excited that we have so many newcomers at this conference, we're going to kind of talk about a lot of these community groups, but you can see the whole list of them there. All the ones that we're talking about are listed on this page, so AAAF.io slash community slash groups. And there you can find a lot more details about each of the groups, particularly useful if you hear us talk about one of these and you think that's really interesting and something you'd like to be a part of. The meetings, the whole point of the AAAF community is that it's very open and transparent. It's why we're doing this. All the meeting notes are available to everyone. So if you hear something about a group and you want to join in, that's the whole idea. We really encourage you to do that and welcome you to do that. And so the meeting times are available on those group pages, as well as the charters and other information about how those groups came together. In one other piece I'll mention before we dive right into some of the first set of updates is that we also have recorded a newcomer welcome to the AAAF community, which talks at a little bit of a higher level just about the processes that we use. The open meetings, the ways that we meet twice a year at formal conferences and then other regional aspects. The way that the AAAF consortium supports the work of these various groups and the staff who are here to present some of this stuff. So that's a recorded presentation. It's available at any time. So it's on the HOVA schedule as basically the second session of the entire conference. So if you go back to it, you can watch it at any time. And it'll also be available on YouTube if you're looking for it later. So that's a great way to get a sense of kind of a large scale way that a lot of these things work. So moving ahead, we'll dive into some of these community group updates. I will handle I think the first four of these groups and hand it over to Meg. But I will also say just to really be clear that we asked this is the community groups are the work of dozens of volunteers in the community, not just to attend these meetings, but to do really important work of organizing all the meetings, setting the agendas, putting out announcements, putting the other sessions at conferences like this. So we're going through these slides, but it is really just meant to reflect the work of all the community co-chairs without whom we couldn't do nearly the volume of work and progress that we do. So I will try to talk about the co-chairs and the work they do, but I just want to be clear that this is not all stuff we're doing. We're helping reflect the work of these groups. So and I'll also say we're going through these alphabetically. There is no good way to rank these. They all are making great progress in their own right. So we'll start with the 3D group, which is the only one I believe with a numeral. Oh no, that's not true. B4H has one, but starts with a numeral. So the 3D community group is a really robust set of interested folks with the kind of root interest of figuring out how 3D might work in a AAAF context, right? So that seems fairly simple, but it turns out it's an extremely complex problem for a variety of reasons. And I encourage you, if you're interested, to join their meetings, because they're really making great progress. So they meet monthly as a community group, their main goal and remit is to kind of share best practices, share existing work, and kind of gather together interest and momentum toward making some progress together as a community. So they've done tons of demos. You can see examples here, whoops, examples here on the screen. Let me move my Zoom interface. They've done a really amazing job of bringing in speakers from other parts of the community, so speakers from Mozilla, from Google, really coordinating efforts from major initiatives like the Smithsonian, from Morphosaurus, from Sketchfab. And a lot of that is in the aims of, as I said, trying to figure out how 3D might work in a AAAF context. And the most specific goal there is to form a technical specification group. So that's a whole set of different requirements. And there's a lot of hard work that has to go into that about just aligning on the scope and what it would mean for 3D to work in a AAAF context. It doesn't mean solving all those problems beforehand, but it does mean agreeing on which problems would be the focus of work like that. And so beyond that, yeah, just really, I want to give a lot of credit to Ronald Haynes, Julie Winchester, and Ed Silverton for doing some great work of marshaling interest in the community and really trying to move toward that particular goal. And so a lot of the challenges they face are very much related to that idea of not just showcasing current, you know, the constellation of things happening in the world of 3D, but also then trying to figure out what we can accomplish in the 3D canvas environment. And then, you know, a lot of things following from that is, you know, making sure that we document it, consider options for sustainability and coordination and interoperability within that entire community, doing a lot of interesting work around workflows, and also figuring out how to make this, you know, useful and viable for institutions that aren't kind of the largest scale national libraries or, you know, major research institutions. So as with all these groups, I really urge you to join one of those monthly calls. They're at a great phase for you to join in that work and help make some progress. Okay. And next we turn to the archives community group, which is at a bit of a crossroads, which we'll come to in a moment. But this is another one of those domain specific community groups. And, you know, we saw this come out of a couple of conferences a few years ago just looking at kind of some of the unique ways and some of the unique elements of vocabulary and structure that come out of the archival community, particularly. So the goals of the archive group are geared toward that end to promote, you know, what kind of usage and what kind of best practices exist for specifically archival materials and that kind of set of hierarchies that are specific to archival collections, providing a venue for demonstrations of folks who have already done some of the work of trying to map those different things. Taking a look at use cases that, you know, haven't yet been covered by some of the AAAF elements. And some of this is I think related to, you know, potentially working towards a cookbook recipes or other documentations of best practices for how people are making use of these materials already. And as with all these community groups just doing that work of disseminating, gathering together interested parties and making a good solid locus of discussion for these different things. So they've had a couple of really popular conversations recently. In particular, I will say one of the big topics that I think has sparked interest and maybe is a good locus of interest for the, you know, the near term or medium term is this idea of how you might connect born digital resources in the AAAF context. And there are actually some really interesting conceptual elements also related to 3D in a AAAF context, some of the similar issues that have to be worked through. So examples there include eBooks, ePubs, web archives, work files, things like that. So they've seen really good interest on the calls, for example, 60 plus folks on the October 27th call. They are talking about moving to quarterly calls, but that sort of relates to this big piece of info. Is they're basically looking to figure, to reconfigure how the archives group works. So, you know, through sort of natural processes, you know, as happens with almost all groups, some of the co-chairs have had to step away. So they're basically put out this call to get feedback on how the archives group might work. So we encourage you to look at that URL bit.ly slash archives hyphen cg hyphen futures. And maybe actually somebody could paste that into the chat if they're able to copy that down. Thanks Meg. So that's a document that explains in much greater detail, kind of what they're looking at and how they might, how they want to kind of talk about moving forward. But I think this is, you know, this is kind of a healthy sign of a lot of these community groups is, you know, is figuring out how to evolve and not just kind of keep doing everything kind of for the sake of momentum. So the community, as I said, the archives community group is looking for input, potentially even co-chairing if what I've been talking about here is of interest. Do get in touch, take a look at that document and get in touch. The co-chairs are Adrian Stevenson, Mark Medienzo, Rebecca Hirsch, and Josh Schneider. And their info is available on that community group page from a little bit earlier. Okay, the AV community group. So this is an interesting example, I believe the first example of a community group that or the evolution from a technical specification group to a community group. So the AV there stands for audio visual. And, and really it comes from the a TSG, a technical specification group that was put together a number of years ago to help us get to the 3.0 version of the presentation API. And with that version of the presentation API came the ability to work with audio and visual materials in the specifications. And so that was just a heroic amount of work. The editors, the TSG, the technical review committee all came together and did, you know, did some amazing things, got the process done. And we released that last June of 2020. And with that, the work of the TSG was done. They had accomplished everything that was listed in their charter. But there's still a lot of useful work to be done in terms of promoting it to the community, reaching out to folks who may find that of interest, talking to developers who have systems that may be compatible or should be compatible with triple AF AV materials. So that prompted the evolution from TSG to a community group. So that's the background here. And the goals of the community group are similar to what I just said, providing, you know, a venue for dissemination and discussion of best practices around AV content in a triple AF universe, particularly developing cookbook recipes for common use cases. And also related to that, very specific kind of assistance and technical input into how that sort of thing might work. Developing recommendations for if there are sort of needed evolutions or use cases that come up that haven't been covered yet. And a really useful element to this too is promoting the possibilities of AV to kind of other communities. So we're under no illusion that, you know, everybody already knows about triple AF and already, you know, has this in mind. So a lot of that work is the work that a lot of us do is trying to spread the word and point out how the triple AF specifications can really help shape things and make things doable and not just doable, but doable in the context of open web standards and browser standards that are usable by anyone with a modern web browser. So the current work, as I said, that's the transition I was talking about. They've been really focusing on the recipe work. And the co-chairs there are John Dunn, Tanya Clements, and Andrea Sagaach, who have done, yeah, great work spreading the word. And that's sort of the plan for the next word is focusing on continued outreach, if we ever get, not if, I shouldn't say that, when we inevitably get to a world where we start returning to conferences and doing some of the work of in-person presentations. I think they have a lot of interesting plans about some AV-specific domains where they can help promote that. And yeah, just talking, I think they're doing sort of a nice series in their community group meetings of inviting software developers and tool creators to their meetings to talk about integration with the major tool. So we've seen really great presentations from Aviary, from AVP, from the Avalon system folks, from Audianitate, from a bunch of different places and institutions that are at the stage of integrating AV capabilities into their work. Okay. And the discovery for humans group. So this is another relatively new community group. And the name maybe sounds a little funny if it's the first time you're encountering it. The reason it's called Discovery for Humans is that it is the counterpart group to a discovery technical specification group that Glenn will talk about a little bit later. And because the Discovery TSG is really focused on system to system or computer to computer interactions and APIs that are passing data from one to another, this is really meant to point out that much of the animating need for those discovery specifications is rooted in human interaction, right? User interaction, user experience. And so that was the impetus for creating the Discovery for Humans group. Their goals are, you know, at a very high level to understand how people find triple AF items, how also there's a nuance there, how people work with triple AF items in the context of, you know, given the fact that people don't necessarily only want to work with triple AF items or they can't only work with triple AF items. So I think that's a big piece of the work that they're doing. Researching and talking about and hopefully disseminating best practices about usability of triple AF discovery interfaces, all of this related to that kind of research level and understanding the motivations and experience of people working with triple AF at a variety of different levels. And then at last point, they're really to catalyze the development of interfaces and iterations of discovery solutions across the triple AF community. So they are currently doing, you know, a lot of work that is related to user experience interviews as well as features and feature reviews. So one example is the way that the triple AF logo is presented in a lot of different sites. There are very kind of subtly different interactions that happen when you click on the triple AF logo on, say a university discovery tool. And so they're kind of reviewing that and documenting it in order to present some best practices. One thing that's not listed here, but I will also mention is that in that feature review and user experience review, a lot of the research went into some really compelling presentation of personas that actually were featured at the keynote on Tuesday from Amy Dashain, who was speaking on behalf of many of her collaborators in the D4H group, also working on the guides.tripleaf.io site, which presents documentation for how to discover triple AF materials at dozens of different institutions. And I think the last one that I will cover here is the manuscripts community group. So a little bit like the archive community group that we talked about earlier at a little bit of a crossroads. So the manuscripts group, oops, here we go. So the manuscripts group I think is one of the oldest groups in the triple AF community. And closely connected to that is the manuscripts domain is I think one of the areas where the core utility of triple AF was the first place where it was really obvious and a lot of the interesting initial functionality came out of solving manuscripts related use cases. So their goals and guiding themes have been to kind of presents the latest and greatest work that's happening in the manuscript community to provide feedback on how those developments are happening and also to make sure that use cases there are captured in all the different API specifications and then to organize and gather sessions and make sure that any showcase of new implementations and new work is done at conferences like this or in other contexts. As with the archives community group, the chairs I think are finding themselves having new duties and have been doing this for a while. So this group is also kind of looking at how it might evolve or change how it's working. One prospect is potentially moving it to an emeritus status where there would still be a lot of expertise in the community but they would stop holding regular meetings either quarterly or bimonthly. But there's also some other possibility if you're a really enthused manuscripts community person and you'd love to help host meetings every so often. I think there's a way that we could talk to you about taking that on and working with us to evolve the manuscript community in that way. So if that's of interest do get in touch with us otherwise we'll be talking in kind of the coming weeks and months about future plans for the rhythm of manuscript community meetings. But I think that is it for my piece. I think I'm going to stop sharing unless Meg you want me to keep advancing slides. I can't hear you yet. How does Zoom work? I can share. Okay great. Let me turn this off then. There we go. Okay. Can you see my slides? Yes. That's great. So I should briefly introduce myself for anyone who I haven't had the opportunity to meet yet on a meeting. I'm Meg O'Hern. I'm the community and events coordinator for the TripLayup Consortium. So moving on with the community updates the maps group has been doing a lot of interesting work. Maps is a really interesting group. They are both a community group and a TSG and they alternate meetings for each form of the group. So they've been doing a lot of work to gather a lot of use cases for maps in IIIF and have been doing a lot of work on the cookbook. There was a lightning talk and a longer session yesterday that if you weren't able to attend those and learn about the cookbook work that's being done those recordings will be shared. So they're looking at creating different recipes for working with maps in the IIIF context. And they're also inviting folks for a number of demos for related projects so that folks can learn from their work and create a community and really benefit from kind of like the group's mind. So over the next year they're going to be working with the TSG or technical specification group. They are working on creating an extension to the IIIF presentation API that allows for the expression of more complex geospatial assertions. And they're going to just continue with the community demos. So if you check out the IIIF community calendar you can see when those sessions are and join them if you're interested. Next up is the museums group. So the museums group includes staff from museums around the world and from other BLAM institution. They meet monthly on the first Tuesday of the month and they do a lot of work similar to what maps is doing with demoing new IIIF launches or tools APIs and different IIIF related website features. They also talk about collaborations between institutions. We've seen some lightning talks about that sort of thing during the conference this week and some of the challenges that they face. And they also just support institutions or other GLAM institutions that are new to IIIF and want to learn from peers. So you can see more information about them at the link there. Maybe someone could post that in the chat if they have a moment. And I also wanted to just direct you to their Slack channel. If you're a member of the IIIF Slack they have a great group going on there. And they've been also working on really promoting the work of their fellow institutions. So here's just a list of some recent museum or GLAM related launches. So and this is stuff that I think we've also covered in the IIIF newsletter and that you might have seen in some other sessions during the event this week. So the Art Institute of Chicago is now offering manifests for artworks via their API. And they recently implemented Mirador 3. And there's a link to view an example of one of their manifests there. University of St. Andrews is using the exhibit.so site and tool to submit student coursework using the museum collections at the institution. I hope that many of you were able to attend the exhibit session that took place on Tuesday morning. If not it's really worth a look. It's a really robust tool for creating storytelling exhibitions with IIIF materials that is actually very similar to some kind of complex work that the New York Times has done with storytelling and images. It's really worth checking out. So historic maps of Rome were just launched in a collaboration between CASVA and the National Gallery of Art using Mirador. The British Museum recently revamped their online collections and made a number of new works available via IIIF and there's a link to check that out. And also there's been a lot of really great work for the Getty from the Getty recently including creating a IIIF generator for including their images in animal crossing and also some information about how other institutions can do that with their materials. And of course the 12 Sunsets project which is a really wonderful way of viewing photo archive from Ed Rusche of Los Angeles which actually recently won a Webby award. The Newspapers Community Group. They've been doing some recent work to showcase IIIF newspaper implementations and producing newspaper recipes for the cookbook. They now need to update the newspaper recipe to make it compatible with the recent AV recipes. And over the next year they'll be working on having more demos and holding more meetings and ensuring that newspapers are represented in the search TSG. The Outreach Group has been up to a lot this year. Their highlights for the 2020-21 year have been helping to shape the IIIF ambassadors program. We have about five ambassadors currently working in different areas to promote IIIF within their own communities. They also did a lot of work compiling and reviewing the IIIF implementation survey. And this last survey that they worked on in collaboration with the IIIF staff had I think actually a record number of responses. And we got a lot of really great information on the status of IIIF implementations in the wild currently. And they're also working on setting up the IIIF implementation checklist set of best practices that will lead to interoperability in IIIF implementations. And they've also been collaborating with us on the virtual conferences and leading sessions, which is we're very, very grateful for. So their calls are on the last Tuesday of the month. They're another group that's looking for new chairs to help shape the future of the group. They're really looking to move towards a model where they're working on spreading the word about IIIF in underrepresented communities to kind of diversify the base of the folks attending the calls and implementing IIIF and getting involved with the conferences. So now I'm going to hand things over to Glenn, I believe, to talk about the technical specification groups. Thank you. So hopefully you can see the slides. Yep. So I'm going to be talking about their technical specification groups or TSGs. These are groups that are looking at extending the specifications. All of these groups are open and we welcome technical expertise, but I think almost more importantly is hearing how people want to use these features so that we can make sure that the future specifications reflect what people want to do. And I don't know if it's pandemic related, but this year has been incredibly productive year for TSGs, as you'll see in the update. So the first one is the authentication technical specification group chaired by Tom Crane and Stefano. And this is looking at updating the authentication technology that we came up with for earlier versions of IIIF to make it compatible with version three and also to extend it to support non-image resources authentication. And there are also some developments in the browser technology, which means that we have to adjust the authentication specification to make it continue working. There was a great presentation on Tuesday by Tom and Stefano, if you want to hear more details about what they're looking at. This group meets every Tuesday, every second Tuesday, and alternates with the search group, which we're going to talk about next. So this one is chaired by Maria, Mike, and Tom Crane. And hopefully Maria has provided a video. Here we go. Hello, I'm Maria Whitaker with Indiana University, and I am one of the co-chairs of the Content Search Technical Specification Group. The other co-chairs are Mike Bennett from the University of Edinburgh and Tom Crane from DiGerardi. I'm here to give you an update on the work of our TSG, which is the most recently formed TSG. Our goals are first to bring the Content Search API in line with Prezi three. And to that end, we need to align the syntax of the Content Search API with the syntax of Presentation API Version 3. That work will be released as Content Search 2.0, and it is currently under review. We expect to have it ready very, very soon. We also need to add support for time-based annotation searching, given that Prezi three added support for time-based media. We also want to address issues that have come up since the publication of 1.0. Another goal is to evaluate user stories and issues for the inclusion of new features and integrations into the next version of the API. We also need to coordinate our work with that of the authentication TSG to ensure compatibility of authenticated searches. We are currently engaging with the community to collect and select use cases to be included in the next version of the Content Search API. We meet on Tuesdays at 12 noon Eastern time every other week, and we also have a search-dedicated Slack channel. Please join us both by coming to our meetings and on Slack to ensure that we address the needs of the community with respect to search. We need to hear from you, and we need to know your use cases. We will also be writing cookbook recipes for the use cases related to search. Eventually, we will start writing the specs for the next version of the API. And as we go, we will be implementing POC to validate our solutions and make sure that they are workable. Thank you very much. Great. Thank you, Maria. The next one is the Discovery Technical Specification Group. So this is the kind of technical version of the one that Joshua mentioned earlier, the D4H, and this chaired by Antoine, Matt and Rob. Again, you've seen this announced on the session on Tuesday, but it's great to announce that the change discovery version 1 was approved by the TRC last week and has been published live now. And 1.0 means it's ready to use, and so we're really excited to see lots of implementations of the change discovery. And this is all about synchronizing between different people, so sending things to European and DPLA, that kind of aggregation of AAAF content. The content state specification, which is designed so that the view of a AAAF resource can be passed between viewers, this is a more formal way of specifying the AAAF drag and drop icon functionality and also adds other ways of starting a viewer in a certain state, such as the URL parameter to preload a viewer with a particular manifest. This has also seen really good uptake as you saw in the session on Tuesday. And again, this is released to version 0.9, so it's very close to being a full 1.0 release, but we're just looking for further implementations. And then finally, work has begun to aggregate change discovery endpoints in the form of a registry of activity streams, and this will provide a centralized source to automate accessing a large amount of AAAF resources. And so if you are looking at implementing the change discovery API, we'd love to add your change discovery endpoint to the AAAF registry so others can see it. And the next steps, updating to change discovery API 1.1, and this is to begin working on notification patterns so people can be updated if there are changes on your resources, especially if you're annotating other people's resources if you can push notifications. And then content state API, again encouraging implementation of content state, particularly in major viewers. So we saw lots of demonstrations of plugins in Mirador on Tuesday. We hope to see more of that with the universal viewer and also other AAAF viewers to implement content state. And then further development of the registry of activity streams and encouraging people to submit those. And then the final TSG, which was mentioned earlier as well as the maps TSG. This is chaired by Mike, Brian, Elliot and Bert. And their main use goals are to understand how to integrate maps and AAAF. And looking at their particular recent work, they've done a cookbook recipe which is looking at how you can represent a fragment of an image on a fragment of a AAAF image on a map. And that's been approved and released. They're now working on a extension to the API version three to add a nav place. And they're hoping to release that in July 2021. So that's very close. And they've also produced a couple of cookbook recipes to go along with that nav place extension exploring how we can relate a AAAF object to a geographical place. And they've also been working with other different groups looking at the standards probably working with maps to make sure it's compatible. And in the future, once they've moved away from nav place, they're going to focus on georeferencing and how we can georeference maps in a standard way and be able to publish that along with the AAAF manifest to be able to use that in different tools and working with the all maps tool we saw on Tuesday again to see if we can make that data standard and shareable between viewers. They also want to look at adding geographical plugins to existing viewers like Mirador 3. And also during discussions through the map group and the 3D group, there's obviously a lot of synergy between the two groups. And so they'll be exploring different ways. They can work together to help both groups in this area. So as I mentioned, all of these groups are open to anyone to join. And if you have a look at the AAAF calendar, you can see when the different groups are meeting. The first three meet every two weeks, the discovery on Wednesdays and the search and authentication on Tuesday. And they alternate and the maps groups meet monthly. But it interlinks with the maps community group. And with that, I will pass over back to Josh. Great. Thank you, Glen. I think we can just stop sharing the slides here. The last one basically just says questions. And we do just as we planned. We nailed it, guys. We have about 15 minutes for questions or conversation. What I will say is that we, you know, like the three of us can absolutely talk about and answer questions as best we can. Some questions may be better suited to some of the chairs of the community groups. But we'll do the best we can. So I had some questions in the Huba chat as they occur to you. The last thing I will say before we dive into the questions is just a little bit about process and to say that that's an overview of the existing community groups and technical specification groups. But those all came to fruition because there was interest and kind of a, you know, a set of folks who were interested in sharing and fostering those conversations. And that is possible. It's not a fixed number. We can create new community groups. If you're interested in that, we have some process documents we can show you. And that's kind of part of what we're here to do. Glen, Meg and myself are happy to help you think through and talk through what it means to have a community group or to foster those discussions. Just by way of example, I think I'm trying to think of other, if there are groups that are sort of being talked about, they're probably not yet to the, you know, to the level of forming a full community group. But for example, in the domain of projects related to machine learning and artificial intelligence, you know, as you can imagine over the last couple of years or so, there's been a lot of interest in how tribes intersects with that area. And it may, as I said, it may not be a community group, but there probably will be some kind of at least group of interested folks meeting, at least, to talk about maybe, you know, just sharing best practices in terms of how machine learning outputs are stored as AAAF annotations, examples like that. So that's, there are some conversations happening around that. AAAF, there's been some talk about AAAF for researchers. Glen, can I put you on the spot and maybe just briefly mention like what the genesis is there and where it might be going? Yeah, so the AAAF research comes out from funding from the UK and its collaboration between, as I'm going to get this wrong, so I'm not going to say, but based in Glasgow, among with other institutions. And it's a really interesting discussion place to really hear the voice of researchers. And if it continues, it would be a great thing that we can maybe mould into a future community group. And as Josh says, the community groups are really fluid and all depends on interest. And so it's great to support any others that might fit and people are interested in supporting. Thanks, Glen. And I think that's the last time I will catch you unawares and put you on the spot, but no promises. So I think that that's the comment I wanted to make that, yeah, that this, you know, the community evolves as, you know, as there is desire to help make it evolve. With that, I see some good links to other projects in the chat here. And thank you. Neil Fitzgerald has just kind of put a link to a document that does a little bit better job of describing the connection between machine learning and machine learning, artificial intelligence and AAAF. I forgot to mention this, but I will say that that idea very specifically came as maybe a co-effort with another group or community called AI for Lam, which is very specifically looking at machine learning and artificial intelligence projects. And so that may be a joint venture in the future. Let's see, are there questions? I see. Let's see. What's the first one here? How was it being a AAAF coordinator during the surge of interest caused by everything going online hybrid? That's a great question. Who, Meg, do you want to give thoughts on? And I will say, sorry, but I will mention that Meg came on board as a AAAF staffer in late February. So like literally days before the world kind of went indoors. And so I'm really curious to hear Meg's response to that. Yeah. I mean, I'll just start off by saying that it was super interesting to deal with a global pandemic in terms of like my professional life and personal life. I think everyone was in this crazy place together where we had to hold it together while the world was upended. I thought I was so like just blown away by how quickly people adjusted and like the commitment that everyone had to learning new things and working online. And everyone in the community kind of came together to put together a document on how to work with the currently available AAAF materials. And I thought it was just so great to see everyone, you know, do what they could so quickly. You know, we saw a really great turnout at our conference that we had to quickly switch to an online format from in-person format. And yeah, I mean, it was crazy, but you know, I think we got a lot done. And I definitely feel like, you know, we were able to respond quickly because it's a community that's already online and, you know, used to not meeting in person all the time, although it's sad that we have not been able to. So yeah, I mean, I think people really came together. There's a lot of work that was, you know, really ultimately, I think did a lot of good. I just want to plus one that and say that I don't want to call it a silver lining because that really makes light of a pen. But I guess what I will say is that it activated some thinking that we were already doing about the best way to connect with a broader segment of the AAAF community, which is to say that the vibrancy of the in-person meetings is just incredible and something we want to continue. But there's very much an inequitable aspect. If we only do the work of the community at in-person meetings, that just leaves out like a majority of the world, folks who just aren't going to be able to travel internationally to participate in the conferences. So we were already talking about the fact that we need to be a hybrid institution, just as Meg said, you know, we're already very much used to that in community meetings. So I think it's just given us, it gave us a crash course, I guess is what I'll say in trying to do this coherently and competently, finding the best way to juggle in-person meetings, the best of in-person meetings with the sort of more equitable toolkits we can put together in terms of online meetings. Glenn, is there anything you want to add or should we keep moving? No, I quickly echo what you said. I think the biggest impact I felt is the training and that was all in person until I had to switch online. And actually, I think that's been really helpful. We've been able to do it much more regularly than we would do normally. And it's great doing it online and that you get people from all different places. You know, sometimes we get people joining at one o'clock in the morning, which is just absolutely amazed. But it's been great to be able to reach out to people that, as you say, we probably wouldn't be able to connect in person. Yeah, no, that's great. That's absolutely right. The training has been a real highlight also. There's another question here. This gets it relatively specific. And Glenn, it's something you mentioned, but you may want to kick this to the maps chairs. I'll give you the option. There's a question about you mentioned geo-referencing fragments. Is that with regard to ancient maps or does that include artifacts? It can include artifacts if it's an image of an artifact. But yes, as Josh says, I'll put into the maps group and they will be more than happy to talk to you about it. Oh, great. There's another question here. Is there any discussion of a community group for educational pedagogical uses of AAAF? I think the answer there is that that has come up a number of times over the years and, in fact, also related to some of what Meg said at the beginning of the pandemic when the timeline was just really unclear and we just had no idea what was going to happen. There was a lot of interest and a lot of work put into gathering tools and resources and documents, particularly for educators doing remote learning. And in terms of a community group, this has come up a couple of times. I think there are a lot of folks who are interested who would participate in something like that. I think not to put too fine a point on it, I think part of maybe the main thing it lacks is really somebody or a set of somebodies who would be interested in leading that work and putting together meetings and setting up a rhythm and an agenda for that. I think there is a lot of potential there. And I think it actually relates to a lot of the work, some of the work related to what Glenn was talking about with AAAF for researchers. There's some amount of intersection there. The short answer is yes, there's been discussion. It hasn't hit the threshold yet of tumbling into a formalized group, but it could happen at any moment. And if that is of interest to you, we'd be happy to talk with you after the conference or after the session today. Are there other questions? Is there anything in the chat that I'm missing? There's one question quite early on. Maybe I'll ask it and you two can answer it. There's a question about if you don't have an IT background, is it possible to contribute to the 3D community group that you've described in your presentation? Yeah, that's a great question. And I'll answer that specific question then I'll actually, because I think it applies to a huge number of groups. Yeah, I think the 3D group is absolutely the community group as it exists now is a great place to participate. I think you would find, you know, I think you would find a lot of interest. I think you would find a lot of people. That group particularly has a wide variety of some folks who are literally developing 3D viewers and doing really hard math in their heads and typing that into code. But then, you know, there's also a lot of folks who are more on the curatorial side or the digital object side. And so it's not just for IT folks or developers. And in particular, the stage that they're at is making sure that use cases are covered and workflows. So if that's a piece, you know, if that's something that you work with, they'd really love your experience and input there. So the answer is absolutely yes on the 3D group. I will say also like that is very much as a large scale comment. I think that's a point of maturity that we're seeing in the AAAF community. So it started, you know, it is itself a technology. It's a set of open specifications. It's similar to the things that make the web and the internet work. So that at root is, you know, what AAAF is. But the community has evolved enough that we're seeing, you know, that it's not just open to people without software and developer backgrounds. It's essential that we get that set of people involved so that we have kind of the full range of web experience represented. So really all of these groups would, you know, benefit from people who, you know, are working with the technologies who are working with students who are working with, you know, museum visitors. That's the only way that, you know, we can create the most robust set of technologies and get that experience incorporated into the AAAF specs and software tools and all of that. Yeah, I hope that was a good answer. Is it another question from Joe? Would Slack be the recommended place to initiate a new community groups? Just a general question. So I get my suggestion. So I think Slack is a great place to, yeah, to find fellow travelers or folks who are interested. But I think, you know, basically I would say like anywhere you think that community of interest or, you know, that domain would, has folks involved. So I'm trying to think of examples. You know, like the Archives Community Group, you know, has archivists in the US, UK, Europe all over the place. You know, that's kind of where their community is. You know, others have existing communities kind of on our Slack and other Slack. I would say, yeah, the Slack and the AAAF Discuss List for kind of announcing or seeking interest would be a place to start. But Meg, anything that I'm not thinking of? Yeah, no, I think that it's Slack and the AAAF Discuss List in terms of looking for fellow interested people, maybe the general channel, as well as the Discuss, would probably be good. And, well, also potentially Twitter, if you're a Twitter person. Yeah, it's interesting to see. Yeah, I think a number of conversations have sprung up on Twitter. And I think that has been kind of the genesis of a couple of different connections. Is there any last questions? I'm scrolling. I'm not seeing a lot. I think we have time for one more if there's something on people's minds. Someone just suggested at the top of the questions, how about using the Hoopa topics in the Community tab for following up? That's a great question. The answer is yes. I think we should do that. So I think that's, I mean, that's probably a great note to end on. So I think that's a great suggestion. I think, you know, I think I'm a broken record on this, but I just am really grateful to the folks who came today, like the AAAF community just is a pretty special thing in terms of the interest and the output of people who are just pursuing things that are of interest to them in a way that, you know, makes it useful to other people. So yeah, I want to thank folks for joining us here today. We'll send out the recording of this when it's done. I want to thank Glenn and Meg for handling bits of this today and also for all the work they've done this week. Yeah. And with that, I think we'll end the recording and we'll see you folks at the few remaining sessions of this conference. Thanks all. Thanks everyone. Bye.