Replies: 7 comments 10 replies
-
Beta Was this translation helpful? Give feedback.
-
Would it be worth exploring a generic property that takes BCP 47 as the value? I guess it would still be helpful to standardise what sort of objects specific countries would expect, that could be figured out case by case. |
Beta Was this translation helpful? Give feedback.
-
Any feelings on using URL/URI/URN? |
Beta Was this translation helpful? Give feedback.
-
I am looking forward to see this in the spec! |
Beta Was this translation helpful? Give feedback.
-
This does make a lot of sense. From the italian experience: IIUC, this is similar to it.riuso.codiceIPA, which is a code identifying an Italian public administration, to link the software and its PA. The concept can and should be general of course (@hidde you are suggesting this right? A global, non country-specific field for the organization?), and it's under It would be nice to have a general one, with URIs. One thing to be consider though: in Italy we've learned that sometimes people might declare an organization in For the NL organizationURL (or the general field, but still, the NL version of the crawler), I think there should be a similar validation, otherwise it becomes too easy for someone to claim a repo belongs to a public body when it shouldn't. So, I guess another question is: would it even better to have an |
Beta Was this translation helpful? Give feedback.
-
@tomootes let's move this forward, I think a top level key will benefit everyone. |
Beta Was this translation helpful? Give feedback.
-
In Switzerland, we are also considering creating a country-specific extension. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In this discussion i would like to propse two things.
Add NL Extension
Adding a NL extension to the standard like the Italian setup. This should like this in its most simple presence:
An example of a record in our catalogue:
We would like the publiccode.yml standard to look like this:
The URL displayed here was sourced from the API Overheidorganisaties serviced by KOOP. Documentation of this API: https://redocly.github.io/redoc/?url=https://api.standaarden.overheid.nl/v1/openapi.json.
This url SHOULD look like:
https://identifier.overheid.nl/tooi/id/oorg/oorg${id}
This way we can fetch organization information for every repo seperately. This means Github accounts can also contain repositories which belong to different organizations. Which gives cooperation-networks flexibility.
Beta Was this translation helpful? Give feedback.
All reactions