We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I take it the extension is modelled after output from the OS-Climate hazard models.
Is it still meant to be potentially applicable to other climate hazard datasets?
The practical implication - should the field name prefix be osc-hazard: like
osc-hazard:
hazard-extension/json-schema/schema.json
Lines 29 to 33 in 77bb29e
or perhaps something not implementation-specific, like clim-hazard:?
clim-hazard:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I take it the extension is modelled after output from the OS-Climate hazard models.
Is it still meant to be potentially applicable to other climate hazard datasets?
The practical implication - should the field name prefix be
osc-hazard:
likehazard-extension/json-schema/schema.json
Lines 29 to 33 in 77bb29e
or perhaps something not implementation-specific, like
clim-hazard:
?The text was updated successfully, but these errors were encountered: