In T362#17396, @fero wrote:

Hi all guys and many compliments for your work!

In T782#17393, @s wrote:

{
    ...
    "tool": [
        {
            "version": "3.1.0rc2-31-ga2cbb8c",
            "name": "nomos",
            "id": 1,
            "configuration": {
                "command_line": "nomossa <filepath>"
            }
        }
    ]
}

Right?

@anlambert can you deploy this, so that it's easier to review "practically"? :)

LGTM, with a single chance s/incomplete/partial/ (which seems more telling w.r.t. multi-part submissions).
So, to recap, the proposal here is:

• partial
• deposited
• rejected
• verified
• failed
• done

@moranegg's question is most likely for @anlambert, but FWIW it would in no way break the proposal here.
As per URI semantics, one can always add a trailing ?foo=bar to any URL, and it'd make sensible to do so here.

In T919#17164, @ardumont wrote:

As per the current tarball loader:

• zip
• tar (gzip, bz2 and lzma)

Closed in rDMODb61c6665661c823080192b351af4744dddb35f1e

yeah, i was thinking about it while running earlier on today :) i'm not yet sure if i'll specify the meaning of the sha1 of each object here, or just say that the sha1 is the primary key of the object and refer to swh-model, we'll see

@ardumont so, what is actually supported in terms of format?

In T335#16990, @zack wrote:

identifier = "swh" ":" scheme_version ":" obj_type ":" obj_id ;
scheme_version = "1" ;
obj_type =
    "snp"  # snapshot
  | "rel"  # release
  | "rev"  # revision
  | "dir"  # directory
  | "cnt"  # content
  ;
obj_id = object sha1, hex-encoded with (lowercase) ASCII characters ;

in the future, if we switch to blake2/256 (or equivalent length checksums), the examples would become something like:

concrete, tentative proposal (EBNF):

identifier = "swh" ":" scheme_version ":" obj_type ":" obj_id ;
scheme_version = "1" ;
obj_type =
    "snp"  # snapshot
  | "rel"  # release
  | "rev"  # revision
  | "dir"  # directory
  | "cnt"  # content
  ;
obj_id = object sha1, hex-encoded with (lowercase) ASCII characters ;

One relevant change requested (make max size configurable) + one nit.
LGTM otherwise.

LGTM. Just a couple of nits

In T917#16911, @olasd wrote:

Moving the documentation about the config to a top-level configuration document, in the docs directory, sounds like a very good plan. You assigned yourself the ticket, will you do it?