Page History

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

dw: didn't make the USRSE deadline and won't be attending PIDFest; should we try for the Force11 conference?

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

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