-
Notifications
You must be signed in to change notification settings - Fork 8
2024 04 09 Technical WG Agenda and Notes
John Kunze edited this page Aug 5, 2024
·
1 revision
---
confluence-id: 328958169
confluence-space: %%CONFLUENCE-SPACE%%
---
Created by John Kunze, last modified on Apr 11, 2024
09 Apr 2024
- Dave Vieglais, Donny Winston, Tom Creighton, Curtis Mirci, Greg Janee
Resolver and static site changes
| Item | Who | Notes |
| Announcements | dw: will be moving to Copenhagen to start up new company that will support ARKs and other infrastructure tc: ACTION: will try to coax a Familysearch rep to join this group |
|
| Any news items we should blog about? Any calls for papers, submission deadlines, upcoming meetings we should note? Please add to Calendar of events. | dw: didn't make the USRSE deadline and won't be attending PIDFest; should we try for the Force11 conference? | |
| N2T resolver status (current target upgrade date April 10) | dv: resolver upgrade planned for 8am PT; mostly just domain name change and certificate swapping, so rollback (if needed) will be easy tc: what technical changes will there be to n2t? dv: some not widely advertized internal stuff; n2t api changes, and the ?info inflection will return JSON dw: ark requests with inflections get passed to arks.org though, right? What inflections will n2t.net handle natively? dv: all handled by end resolver dv: new n2t code will be available on GH dv: new public naan registry will work on a JSON version, but for now the naan_registry.txt file will remain dw: what license? we should tell people up front dv: action: will look into open source licensing; probably MIT |
|
| NAAN request processing status | dv: expect upgrade in early summer for naan processing changes | |
| static site pages, and working group pages | ||
| ARK spec (v38) to be renewed before May 9 * opportunity to change recommendation of V18 spec to v39 spec? |
dv: an alternative is to make : or :/ a config option jk: would like to route to a newer spec dw, dv: yes, newer is better dw: in fact I've assumed newer is better and implemented it jk: so did BnL dw: The issue of “what should arks.org do for convenience?” (via naan config) and “what resource should we direct implementers to?” seem separate. I am in favor of linking to v39 as the “current draft recommendation”. The ARK recommendation should be to mint without, to respect what you're given, and in perpetuity to use dw: will be doing a complete ARK implementation soon and will return with feedback |