Draft Transition PlanOverall impact should be minimal. The fewer NAANs you deal with, the easier. Timings T1, T2, ..., T6 to be determined later.
1. If you produce ARKs, by time T1 you should produce ark:12345 instead of ark:/12345
2. If you produce ARKs but only ever produced new format (ark:/12345) ARKs, by time T1 T2 you should prepare to receive your own ARKs in the old format (because others may unwittingly reformat your ARKs)
3. If you receive or resolve ARKs, by time T2 T3 you should accept either ark:12345 or ark:/12345, and plan to do that in perpetuity.
4. If you receive or resolve ARKs, by time T2 T4 you should accept ARKs at least as long as 255 octets.
5. If you validate ARKs, you should by time T1 T5 make sure your validation is relaxed enough to not reject new format NAANs, ARKs with ~ or #, and Name and Qualifier parts longer than 128 octets.
6. If you receive or resolve ARKs, by time T6 you should recognize ?info and (a) not flag it as an error, (b) return metadata or return something other than 404 (eg, return the object as if no inflection).