-
Notifications
You must be signed in to change notification settings - Fork 1
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 PotenitialAction to describe arrow dataset access #27
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
question
Further information is requested
Comments
valentinedwv
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
question
Further information is requested
labels
Sep 26, 2024
close as #12 is the same issue |
Partially, #12 makes it available. Seems some parts of the croissant spec are missing, and @fils do you think we should follow it? And noticing the first one also has a code snippet. Does the facet search also make that snippet accessible? snippet from jsonld:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
question
Further information is requested
Stac catalog has a database access element on the page. We need to find a way to replicate/communicate the same information.
Also, Collections may have assets, if so, then we render as a dataset with a potential action.
Datasets can have s3 links that are really better described with code, add a potenital action
So, for the s3 link, we might think about using potential actions rather than data distributions
Not sure if this is a createAction, or an consumeAction... and not really sure if that matters. we pick one.
The text was updated successfully, but these errors were encountered: