DID Method Registration Resolution #2 on 2021-03-16

[OR13]

Update the registration table to include, status, first registered date, last reviewed date

https://www.w3.org/2019/did-wg/Meetings/Minutes/2021-03-16-did-topic#resolution2

[OR13]

I think the dates are a terrible idea, and we should close this issue and not implement this resolution... github tracks dates for us.

[OR13]

we should resolve not to do this, and close the issue.

[iherman]

The issue was discussed in a meeting on 2021-08-17

List of resolutions:

• Resolution No. 4: We are not going to add dates in a table to the DID Registry

View the transcript

6.5. DID Method Registration Resolution #2 on 2021-03-16 (issue did-spec-registries#271)

See github issue did-spec-registries#271.

Orie Steele: Similar scenario, this was about status and dates
… We can do status with labels, not sure what to do about dates
… Either we need new proposals for handling dates, or decide that we will not implement the resolution

Manu Sporny: We have a resolution for first registered date, and last reviewed date

Brent Zundel: Seemed like a good idea at that time

Manu Sporny: Not sure if this is very useful

Drummond Reed: I still think "first registered" is a good idea, but "last reviewed" doesn't seem to make sense

Markus Sabadello: This can be reconstructed from Git history?

Ted Thibodeau Jr.: This is also overtaken by events.
… We registered DID methods before we had even finalized the requirements for DID methods.

Orie Steele: We should just use Git, and resolve to not implement this resolution

Joe Andrieu: The link that people click on may not be the one that was reviewed (unless we use hashlinks)

Brent Zundel: There was a lot of conversation on liveness, and how up-to-date DID methods are.

Proposed resolution: We are not going to add dates in a table to the DID Registry (Brent Zundel)

Ivan Herman: +1

Manu Sporny: +1

Brent Zundel: +1

Drummond Reed: +1

Orie Steele: +1

Charles Lehner: +1

Dave Longley: +1

Shigeya Suzuki: +1

Markus Sabadello: +1

Ted Thibodeau Jr.: +1

Resolution #4: We are not going to add dates in a table to the DID Registry

Drummond Reed: Thanks Brent. Big high five to Joe and Daniel and also Orie.

Brent Zundel: Thanks everyone, we got through a lot of items. Cu next time.

---

[wip-abramson]

This is interesting. It contradicts one of our recent resolutions.

Add a "lastUpdated" date to the DID Method registration to enable the ability to convey whether a DID Method is actively maintained in the list of DID Methods. https://www.w3.org/2024/11/14-did-minutes.html#abd8

Wondering if we should in fact just be fetching this date from github and the resolution should have been something like:

display a lastUpdated date for DID method entries in the registry.

cc @decentralgabe @msporny @pchampin

[msporny]

It's fine for resolutions to contradict previous resolutions (the group takes in information, updates its mental model, and makes new decisions that might contradict old decisions).

That said, to implement lastUpdated, I was just going to check what the last Github modification date was for a particular entry and set the value based on that. It could be a fairly automated process that runs once a month or two. The only thing someone needs to do is touch the file w/ a new date (via a commit/PR) if they want to keep it alive. Fairly easy to implement.

[wip-abramson]

Great, that makes sense to me. Avoid people submitting and having to check a date entry in any PRs that submit/update DID method entries.

I suggest this can be closed?