Important: Candidate for Approved Specification, Review Period starts

2 views
Skip to first unread message

Roberto Di Cosmo

unread,
May 30, 2023, 6:09:46 AM5/30/23
to swhid-...@googlegroups.com
Dear all,
   all the blocker issues have been resolved, thanks to all of you that contributed to make this possible!

As a consequence, the current status of the specification is now officially a Candidate for Approved Specification.

According to the governance document, we now call all of you to review the current document that will last for a two-week period, and if no major issues arise, we will then be able to announce our first “Approved Specification”.

Here is the planned timeline:
  • May 30tt 2023 (today): start of the review period, triggered by this email
  • Tuesday June 13th : end of the review period, last call for comments
  • Friday June 16h : if no blockers, formal announcement of the Approved Specification 1.0 
Looking forward to your help!

--
Roberto (on behalf or the SWHID specification core team)

Robbie Morrison

unread,
May 30, 2023, 6:27:08 AM5/30/23
to swhid-...@googlegroups.com

Hi Roberto, all

Looks good on a very brief scan.  I want to traverse the issue of public licensing.  As I understand it, the specification is CC‑BY‑4.0 and the current document is silent on the legal status of the identifiers themselves.  Please correct me if I am wrong.

Of course, an SWHID alone will not attract copyright (even under United Kingdom law), but the server may well attract sui generis (96/9/EC) database rights if located (or less so, controlled or owned) in Europe or the UK (under present UK statues).  I would therefore like to see the identifiers explicitly placed under CC0‑1.0 waivers.  That instrument also aligns with good practice for metadata from most commentators.  And would allow users to download a substantial proportion (a notion yet to be subject to case law) of a SWHID database without running into copyright and allied law compliance issues.

Any lawyers present might like to comment?

with best wishes, Robbie

--
You received this message because you are subscribed to the Google Groups "SWHID (Software Heritage Identifiers) discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swhid-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/swhid-discuss/CAJBwKuWY-7-r5kXX5xf1ZeTOW_AjAB8nEm01aOXDGu5wbqvcRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
-- 
Robbie Morrison
Address: Schillerstrasse 85, 10627 Berlin, Germany
Phone: +49.30.612-87617

Zavras, Alexios

unread,
May 30, 2023, 9:18:46 AM5/30/23
to Robbie Morrison, swhid-...@googlegroups.com

Hi Robbie,

 

The specification itself is under Community Specification License 1.0, as can be seen in https://github.com/swhid/specification/blob/main/LICENSE.md (not CC-BY-4.0)

 

The specification describes how to compute algorithmically the SWHID for various items (files, directories, commits, etc.). Therefore each SWHID does not contain any human creativity and it would be hard for someone to claim copyright.

 

Whether a collection (automatic or curated) of a number of SWHIDs may be protected by other rights, as you mention, is outside the scope of the specification of the format of a single SWHID. Keep in mind, this specification is about a standard format for referencing digital artifacts. There is nowhere any reference to a “server” that you mention.

 

Hope this helps,

 

-- zvr


For more options, visit https://groups.google.com/d/optout.

Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

Robbie Morrison

unread,
May 30, 2023, 10:57:25 AM5/30/23
to swhid-...@googlegroups.com

Thanks Alexios

My one remaining question is therefore: why is the text of CC‑BY‑4.0 appended to the specification?  Should this section be removed therefore?  Or replaced with the text of the Community‑Spec‑1.0?

Robbie


For more options, visit https://groups.google.com/d/optout.

Zavras, Alexios

unread,
Jun 1, 2023, 3:53:31 AM6/1/23
to Robbie Morrison, swhid-...@googlegroups.com

Thanks for pointing me to this, Robbie.

It was a remnant of the initial tool setup – should be fixed now.


For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages