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

Last episode needs more discussion about what to include #71

Open
allegravia opened this issue Oct 26, 2018 · 3 comments
Open

Last episode needs more discussion about what to include #71

allegravia opened this issue Oct 26, 2018 · 3 comments

Comments

@allegravia
Copy link
Contributor

Mateusz and I think we should discuss if we are full happy with the current content of this episode. - - Can documentation be sort of metadata? More explanation is needed about the difference between documentation and metadata (e.g., by providing examples).

  • Should we add a description on how to add metadata "manually" (i.e. not using a platform/registry)? Should we describe the different ways to add metadata and tell that registries are one of those?
  • We think we should provide more examples of metadata (e.g., HTML metadata tags, Package Metadata in R, CodeMeta json-ld) and explain how metadata make software more discoverable (in these examples, e.g. HTML pages by Google).
  • Some concepts in the episode should be made clearer (e.g. the paragraph on controlled vocabularies).
@orchid00
Copy link
Contributor

I would like to add these links to collaborate with the metadata-episode and continue this discussion

@orchid00
Copy link
Contributor

About this topic "Can documentation be sort of metadata? More explanation is needed about the difference between documentation and metadata (e.g., by providing examples)."
The team working on contributions had also this discussion is Documentation part of the guidelines for contribution?
We have defined that documentation is all about how the software works focusing on the user.
We also discussed that documentation is the "whole package" the point of reference for all, and as such it should contain at least links to all the recommendations.
A link to the public repo, a link to the licence, a link to the contributions guide, and a link to metadata, either a file or a public metadata repository where the metadata has been registered.

@orchid00
Copy link
Contributor

there is also a clear visual about documentation and metadata here, page 7: https://drive.google.com/file/d/1LEYLkTmPvUfamYDzMfQfX1SsHFl99ZPa/view

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

No branches or pull requests

2 participants