Conformance with API-Features

[cmheazel]

In a perfect world API-Moving Features would be an extension of API-Features. However, this may be an unacceptable constraint on the API-Moving Features standard. Is there a balance we can strike between conformance with API-Features and going our own way?

[ghobona]

Cc: @pvretano @cportele

[cportele]

I had a look at the repo, but this seems to be empty. Since I was cc'ed: Is there a rough design of the API somewhere and/or a list or requirements that it should support? What are the issues with the current OGC API Features specs from a moving features perspective?