light (examples: resolver config, which seems typical (RFC6690 CoRE, RFC6415 host metadata, RFC8414 OAuth metadata, Keybase, W3C DID config, W3C Tabular data for web),
register under W3C DID (Decentralized ID)?
all: no objection to URN namespace registration tc: the heavy use of .well-known seems unnecessary given the precedent, eg, how everyone uses it for OAuth config jk: I think we need to understand whether we would have to support resolution of every ARK from /.well-known/ark:... It might work if each resolver could continue to support ARKs from its own chosen URL path prefix all: the lightweight use of /.well-known is ok dw: i like the idea of using .well-known to opt into ARKs tc: yes, ok to move in this direction kh: yes, this is good and straightforward jk: does anyone have time to pursue W3 DID registration? dw: I brought it up, but don't really have time
Can we come up with strawperson times T0, T1, T2, ...?
tc: accepting noslash ARKs needs to come before producing them tc: I recommend we get the task list (a) complete and (b) dependency-ordered before trying to assign times tc: ACTION I will review with this in mind kh: recommend we prioritize clearing the plan with the major ARK producers
Action items
Tom Creighton will review the transition plan with an eye toward completeness and dependency ordering
