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.

Sign up for GitHub

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

Jump to bottom

Consider making legal/repoOwner mandatory #60

Open
alranel opened this issue Apr 8, 2019 · 2 comments
Open

Consider making legal/repoOwner mandatory #60

alranel opened this issue Apr 8, 2019 · 2 comments
Labels
standard-breaking-change This change breaks backward compatibility vote-draft Change proposal to the Standard or to the governance procedures

Comments

@alranel
Copy link
Contributor

alranel commented Apr 8, 2019

As of now, it/riuso/codiceIPA is specified to be mandatory only if legal/repoOwner is a Public Administration. However legal/repoOwner is an optional key, so this creates ambiguity.

We should consider either making legal/repoOwner mandatory or changing the specification for it/riuso/codiceIPA so that it does not mention legal/repoOwner.
@alranel alranel added the meta Meta changes not related to the standard itself label Apr 8, 2019
@libremente libremente added the vote-draft Change proposal to the Standard or to the governance procedures label Jun 14, 2019
@libremente
Copy link
Member

libremente commented Aug 13, 2019 •
edited
Loading

I completely agree on this, I would like to see legal/repoOwner as a mandatory key.
Question: which is the case where the repoOwner is unknown? I find it difficult to clearly see it.
If we find no objections, I would try to merge this in 0.3. @alranel
Furthermore, this simplifies the rendering of the catalog, helping to avoid misunderstandings.

@bfabio bfabio added standard-breaking-change This change breaks backward compatibility and removed meta Meta changes not related to the standard itself labels Dec 5, 2021
@johanlinaker
Copy link

As highlighted by @libremente, what about cases when this is unknown or spread out over a community?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
standard-breaking-change This change breaks backward compatibility vote-draft Change proposal to the Standard or to the governance procedures
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@alranel @bfabio @johanlinaker @libremente