Opened this issue to inform Dirk Roorda:
https://github.com/annotation/text-fabric/issues/54

This is now done

review template with:

• @software for the software concept/project
• @softwareversion for a specific release
• @insoftware for a specific artifact in the software (e.g revision, directory, file)

review template with @software and @softwareversion entries

thanks @twitu for finding this location, if you see any other places dates are documented, feel free to comment here.

https://docs.softwareheritage.org/devel/apidoc/swh.model.html#module-swh.model.identifiers
This explains some of the fields associated with dates, timestamps and offset.

I too, two noticed the two glossaries. They have varying levels of explanations and merging them is one of the tasks I have considered for my GSoD application. I will be glad to assist in the process, in any way I can.

@zack: Good idea to have only one glossary.

I second the need of properly defining terms related to push archival.

Draft is done and was sent to Inria GT for feedback.

Duplicate of T1657

References to investigate:

• Zotero and the following issues:
  • https://github.com/citation-style-language/zotero-bits/issues/69
  • https://github.com/zotero/zotero/issues/1438
  • https://github.com/zotero/translators/pull/1578
  • https://github.com/zotero/translators/pull/1552
  • https://github.com/zotero/bib-web/issues/106
• https://code4ref.github.io/pure.html

I created a seperate branch moranegg on which I'm working and to which I'm pushing.
You can have a look, but I will ask for a merge only next week.
Seems I can't push to master, but it's better this way :-)

Sorry, I was in the midst of just adding quotes for readability and left it open.

Is this committed?

I have talked to Bruno about it for deposits on HAL.
It can't be implemented on HAL's form without an "high level" decision.
I think this will be the same for the actors roles.