...
| Time | Item | Who | Notes |
|---|---|---|---|
| remove #, add ~ | |||
| ark:/ becomes ark:[/] | (in many places) / now optional Do we need some sort of guidance/advice on "accepting" / while transitioning; Tom raises general question of content negotiation: should we indicate version of arks we are transmitting in syntax, rather than depend on content negotiationnegotiation Greg: should we call this deprecated, or indicate old form transitional and indicate how to transition - John we have to make explicit support for older form, look for correct language on this Minters SHOULD not use slash; Resolvers MUST handle / | ||
| "resolvers to check for inflections before normalizing" | |||
| more flexible NAAN | |||
| '?' inflection explicitly includes possibility of HTML with embedded metadata | |||
| Max length restriction removed | |||
| Extra: new co-author and IETF boilerplate changes | |||
| Extra: new anatomical definitions -- Resolver Service, Base Object Name, Core Immutable Identity | |||
| Extra: mention arks.org as Maintenance Agency (not AITO) | |||
| New proposed change: "http:" to become "https:" | Reflects change in boilerplate; but also think good idea for arks: AGREED | ||
| New proposed change: NMAH to be renamed NMA (simpler to teach about while still allowing a port designation) | |||
| Discuss: what about making '?' the same as '??' for easier implementation | Possibly related to issue of resolving version | ||
...