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.

Sign up for GitHub

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

Jump to bottom

Data refs input: could it be a URI? #30

Open

agstephens opened this issue Jul 17, 2020 · 2 comments

Contributor

agstephens commented Jul 17, 2020 •

edited

Loading

Could all data refs components be provided as URIs:

I.e. they all have a namespace identifier.

E.g.: esgf:/sdfsd/fsd/fsd/f/sdf/sdf/

Need to think about it.

Could also have pointer to an external resource that resolves to one or more URIs.

Contributor Author

agstephens commented Jul 29, 2020 •

edited

Loading

URIs can include * character in it - see: https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#Definition

Contributor Author

agstephens commented Jul 29, 2020

And this approach could deduce types of URI:

http(s):////*.nc - remote file
esgf://cmip6.something.*.v20020202 - ESGF dataset (assumed local)
something.nc - NC file (local)
file:///something.nc - NC file (local)

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