-
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
Extension template #2
Comments
@rob-metalinkage many thanks! When can we expect to see the new PROV-O extension here? I'm trying to map what you've defined towards our requirements in FAIRiCUBE, but am struggling a bit with just the JSON Schema view on things. I've identified the following for use in FAIRiCUBE:
In addition, we'd like to be able to provide
|
@rob-metalinkage @avillar any outlook on updates here? |
Proposal for the extensions:
|
This work on a template is parallel to using the building blocks pattern to define a specific STAC extension for Prov. It was pushed down the priority queue by work on STA / Sosa mapping. Let's convene next week to review progress and priorities |
is there any progress reagrding the 2 proposed extensions : (preprocessing & documentation) ? |
@baloola I havent yet had a free moment to go back to STAC profiles - however there is a workshop planned to look at "ObservableProperties" in February, and if we visit STAC profiles for this we can also apply the same approach to these issues. Technical progress is dependent on stakeholders providing specific examples I could model, test and document with. Progress overall is dependent on this being taken on officially under the auspices of a OGC Working Group. |
https://github.com/ogcincubator/stac-extension-template is a fork of the official STAC extension.
It has building blocks configured that draw on the core STAC building blocks.
It needs to compile the target json-schema/schema.json
Please consider options for refining design - the templates are still very complex, and the #definitions part it repetitive (and doesnt use the default $defs pattern.
What can be done to simplify?
The text was updated successfully, but these errors were encountered: