Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check how to do the copyright correctly in files #31

Open
BirgitBoss opened this issue Jul 18, 2024 · 1 comment
Open

Check how to do the copyright correctly in files #31

BirgitBoss opened this issue Jul 18, 2024 · 1 comment
Labels
process not about content
Milestone

Comments

@BirgitBoss
Copy link
Collaborator

see comment in https://github.com/admin-shell-io/aas-specs-iec61360/pull/30/files#r1681031851
Shouldn't it be "Copyright (c) 2024" ?

and my comment in https://github.com/admin-shell-io/aas-specs-iec61360/pull/30/files#r1682520291

probably

Copyright (c) 2023-2024 Industrial Digital Twin Association
Copyright (c) 2018-2022 Zentralverband der Elektro- und Digitalindustrie and Plattform Industrie 4.0

see e.g. https://opensource.stackexchange.com/questions/6389/how-do-the-years-specified-in-a-copyright-statement-work#:~:text=In%20the%20case%20of%20open%20source%20projects%2C%20the,commit%20to%20a%20publicly%20visible%20version%20control%20repository.

The year in the copyright notice refers to the year of first publication.
It is a common convention that the notice lists all years where new versions were published.

@BirgitBoss BirgitBoss added this to the V3.1 milestone Jul 18, 2024
@BirgitBoss BirgitBoss added the process not about content label Jul 19, 2024
@twebermartins
Copy link

Checking - probably we need also to add the first and last year of publication. Also, the legal entity must be written - e.g., Industrial Digital Twin Association e. V.
Also, we need also to check all other publications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
process not about content
Projects
None yet
Development

No branches or pull requests

2 participants