-
Notifications
You must be signed in to change notification settings - Fork 35
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
Use Case: represent a portal of RO-Crates #283
Comments
Note: this may be out of the scope of the RO definition, feel free to relocate the issue if appropriate |
Related API standards for iteration of (changed) resources: SWORD, OAI-PMH, TRS |
@marc-portier had some ideas on this as well as @ptsefton have done listing of RO-Crates |
I implemented a very simple approach to this in ro-crate-html-js -- there's a script included with that, |
Peter has tool for iterating RO-Crates in a folder and then makes an outer collection crate that embeds parts of their metadata (?) |
As a content RO-Crate provider, I would like to set up a portal/landing page for my ROs in a machine-readable manner.
If I want to expose a landing page with only a few ROs without using existing registries, but still make the landing page machine-readable, it would be great to provide a mechanism/suggestion for doing it so. For example, implementing a DCAT approach, or which properties of schema.org should we use (since RO-Crates are sdo:Datasets).
The text was updated successfully, but these errors were encountered: