Open gilleslandais opened 4 months ago
The classification is partially empirical -- these are the kinds of DOIs being created today, and partially and incompletely conceptual -- collection DOIs might have incredible power depending on how they are implemented.
I think that Knowledgebases section deserves more explanation, perhaps as examples.
Here is a list of my favorite knowledgebases and if/how DOIs are implemented in them:
Knowledgebase | DOI | Comments |
---|---|---|
Simbad | None | |
NEA12 | DOI for resource | Weekly releases; User access versioning |
NED | DOI for resource | Has releases; User access versioning |
VAMDC | DOI for workflow | Is it a knowledgebase or a collection? |
Section 2 defines a classifification with 4 type of resources.
What is the idea behind this classification? a best practices for each of them ?
I think that
Knowledgebases
section deserves more explanation, perhaps as examples. Is it true if I say that a knowledge databse is a service that provides/generate (possibly among other things) DOI for some (or all) of its resources?In that case , are there special DOI metadata expected ? relationships between resource and the service?