Closed pvretano closed 5 months ago
It would seem necessary to formalise optional FG JSON support as a named profile (conformance class). We could also define BP profiles including constraints implementing recommendations. I'll build some STAC building blocks based on such recommendations, allowing people to transparently declare the behaviour.
In STAC, the time member is optional so, in order to promote more alignment between the two standards (since we want STAC to be a profile of Records), I've made the changes to make the top-level
time
member optional. I did, however, add a recommendation that says that thetime
member shoud be included in the record.