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

Use Case: I want to indicate where Web-based Data Entities should be downloaded to #337

Open
fbacall opened this issue Jul 19, 2024 · 0 comments
Assignees
Labels
use-case A (potential) use-case for ROLite creation, consumption or integration

Comments

@fbacall
Copy link
Contributor

fbacall commented Jul 19, 2024

As a Workflow RO-Crate generator, I want to indicate a local path to where a Web-based Data Entity (e.g. some large input data) should be fetched to, so that the workflow can be executed on this data.

Something like this:

  {
    "@id": "https://example.com/files/large_file.zip",
    "@type": "File",
    "name": "Input dataset",
    "contentSize": "999999999",
    "encodingFormat": "application/zip",
    "localPath": "workflow/inputs/large_file.zip"
  }

The inverse is already possible, referencing a URL for a local file:

  {
    "@id": "workflow/inputs/large_file.zip",
    "@type": "File",
    "name": "Input dataset",
    "contentSize": "999999999",
    "encodingFormat": "application/zip",
    "contentUrl": "https://example.com/files/large_file.zip"
  }

...but the spec says:

... Attached resources where @id is a URI (path) relative to the RO-Crate Root which MUST resolve to file.

so I would have to get around this by having an empty file in the payload, which seems hacky.

@fbacall fbacall added the use-case A (potential) use-case for ROLite creation, consumption or integration label Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
use-case A (potential) use-case for ROLite creation, consumption or integration
Projects
None yet
Development

No branches or pull requests

1 participant