...
| Item | Who | Notes |
|---|---|---|
| Announcements | ||
Calls for papers, submission deadlines, upcoming meetings: Calendar of events 2023 Code4Lib pre-conference CNI pre-recorded briefings | From Hardy Pottinger We are now accepting pre-conference proposals for the 2023 Code4Lib conference at Princeton University in Princeton, New Jersey. These pre-conferences can either be a 1-day (six hour) or a 1/2-day session (three hour) and will occur on Tuesday, March 14th. These workshops are required to be In-Person ONLY. Code4Lib 2023 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4Lib community, please visit https://code4lib.org/about/. The pre-conference sessions give folks a space to share and build knowledge, as well as to teach attendees new skills relevant to library technology. Pre-conference sessions can range from workshops to working sessions. To propose a session, please go to the 2023 submission form. If you're looking for inspiration, there are many great examples of pre-conferences from recent years: https://2022.code4lib.org/workshops/, We are taking proposals until November 30, 2022, 5 PM PST / 8 PM EST. After a period of public voting on workshops, we hope to confirm sessions with the facilitators shortly after. If you have any questions, please do not hesitate to email us - by responding to this email or by contacting Code4Lib.Workshops@gmail.com. Best, Code4Lib 2023 Pre-conference Committee | |
blog posts? draft new ARKs-Service | ||
| New markdown format for ARK spec | ||
IIIF connection made While the spec recommends opacity in the base identifier, over time the spec has become more relaxed about semantics in extensions. In that vein, the IIIF API specifies certain characters (eg, ! and ^) in extensions in order to request variants of the base image object. OTOH, like the ARK spec, the IIIF spec uses characters that should be encoded in URIs. Interest in working with IIIF on this issue, or on PIDs in general? | ||
Code of Conduct draft – please review by Nov 18 | ||
Persistence statements status subgroup? Rob Lyon, Roxana Maurer, Kirsta Stapelfeldt, ...? | ||
docker-arknoid status | ||
| POSI alignment for ARKA/N2T.net? (https://openscholarlyinfrastructure.org/) | Donny |