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

Add record_visibility slot #266

Open
mih opened this issue Feb 8, 2025 · 3 comments
Open

Add record_visibility slot #266

mih opened this issue Feb 8, 2025 · 3 comments

Comments

@mih
Copy link
Contributor

mih commented Feb 8, 2025

It should have the range Agent to indicate appropriate audiences.

Name and setup are tentative, just need to capture the need.

A dedicated The Public agent instance could function as a ok-to-publish flag.

@mih
Copy link
Contributor Author

mih commented Feb 8, 2025

Or it could all the way down in things, and is maybe record_audience with a uriorcurie range... related mapping to dcterms:audience

@mih
Copy link
Contributor Author

mih commented Feb 9, 2025

record_dissemination, and make it multivalued: true

@mih
Copy link
Contributor Author

mih commented Feb 9, 2025

Yet another approach: With #269 comes the ability to annotate metadata records.

Any given scenario can define a simple tag to approve a record for public dissemination, or whatever other scope.

Which means that this does not have to be solved at the schema level, but can be addressed by a convention established for a particular use case.

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

No branches or pull requests

1 participant