Is this related to T1021?

IMO this URI is fine (and we are already using it afaik), we just need to redirect it to a different page to be "self-documenting"

Oops, sorry, I missed your comment.

The last suggested adaptations are D4403 D4405.

add also an example for Core SWHID:

<swh:deposit>
      <swh:reference>
        object swhid="swh:1:dir:31b5c8cc985d190b5a7ef4878128ebfdc2358f49"
      </swh:reference>
    </swh:deposit>

Here is a first draft for the FAIRsFAIR event:
https://docs.google.com/document/d/1MnGaAyXSUziRQv7MqM8H2ix0McGa5Jw6ox6ZSviqf3E/edit?usp=sharing

• FAIRsFAIR in a nutshell presentation https://docs.google.com/presentation/d/1x6L29gZkJviHxgGSGnJnOXz2Sbt-XKXETFCPdDUs2Rk/edit?usp=sharing

@vlorentz can you take this task ?
It is not a high priority, but you have a good eye with xml and metadata.

More details for this task is here T2537

@vlorentz some comments on: https://docs.softwareheritage.org/devel/swh-deposit/specs/spec-meta-deposit.html

Deployed as well.

The [1] part has landed within the deposit (server side).
So it's now possible to update the associated metadata to a deposit which is done.

The access to the glossary from the main docs page is hard find.
It's under Indices and tables which is not exactly the evident as a glossary related category.
Also there is no access from the left menu.

Here is the document on which we based this summary

I have made a survey of the existing code to ensure what I think happens in the
deposit is correct. TL; DR, it is!

In T2312#47921, @moranegg wrote:

After this morning's meeting with @vlorentz and @ardumont:
We will keep the metadata-only deposit specs with the idea of a separate namespace swh for which we need to write the schema (not sure we have that).

This way, the xml with metadata has a section where the identified artifact is mentioned:

Reference a snapshot, revision or release:

With ${type} in {snp (snapshot), rev (revision), rel (release) }:
<swh:deposit>
  <swh:reference>
    <swh:object id="swh:1:${type}:aaaaaaaaaaaaaa..."/>
  </swh:reference>
</swh:deposit>

We need to add to the list of types: directory and content

The possibility to deposit metadata on an origin should be implemented as well, but is not suited for institutional repositories (e.g HAL).
Reference an origin:

<swh:deposit>
  <swh:reference>
    <swh:origin url="https://github.com/user/repo"/>
  </swh:reference>
</swh:deposit>

This specs fits the POST of a new deposit in SWORD and is described in the SWORD v2 documentation (6.3.3. Creating a Resource with an Atom Entry)

That's true if you consider the graph sub-dag to be the Resource. I assumed at Resource to be the deposit itself; but re-reading the SWORDv2 spec, it's not obvious which one is the right interpretation.

After a talk with Bruno and Yannick on HAL, they say that depositing metadata is: 6.5.2. Replacing the Metadata of a Resource
because the resource already exists on SWH and this should be a PUT of new (maybe new from scratch) metadata on an existing identifier (SWHID).

Although, it might be challenging to do so, since the metadata deposit requires a SWHID and the process that follows is quite different from the deposit.