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

Data sheet module use case evaluation report #191

Open
4 tasks
evabl444 opened this issue Feb 28, 2024 · 1 comment
Open
4 tasks

Data sheet module use case evaluation report #191

evabl444 opened this issue Feb 28, 2024 · 1 comment

Comments

@evabl444
Copy link
Collaborator

evabl444 commented Feb 28, 2024

From textile case:

  • Is the term “Statement” standard label for describing information within datasheet? It appears somewhat confusing as a concept name.
  • Can an image be considered a data type? It appeared in some user stories
  • Currently, data is only described in terms of data type. What about other attributes such as data format, mandatory or optional fields, the nature of the statement (certified or not)?
  • What about sensitivity/access rights (needed for sharing data between actors), validity, etc.?
@evabl444
Copy link
Collaborator Author

Additional input from the meeting workshop:

Regarding what is actually to be considered a statement of the data sheet or merely attributes of some other concept retrieved for the sheet: Not entirely clear in all cases. Will be detailed by the use cases in the next version of he data deliverable, but we can make reasonable assumptions for now, e.g. address is an attribute of the actor, not a statement in the data sheet.

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