The original plan was to limit OpenGovLD to application/ld+json serializations and to allow OParl to cover application/json. This was intended to simplify coexistence.
But "OParl 1.0" is now overdue half a year without any visible activity to finalize the specification in the last five months. Repeated requests to update the overdue milestone have not even been answered (https://github.com/OParl/specs/issues/261). It therefore makes sense for OpenGovLD to stop waiting for "OParl 1.0" and to become a complete replacement for the OParl specification.
The original plan was to limit OpenGovLD to
application/ld+jsonserializations and to allow OParl to coverapplication/json. This was intended to simplify coexistence.But "OParl 1.0" is now overdue half a year without any visible activity to finalize the specification in the last five months. Repeated requests to update the overdue milestone have not even been answered (https://github.com/OParl/specs/issues/261). It therefore makes sense for OpenGovLD to stop waiting for "OParl 1.0" and to become a complete replacement for the OParl specification.
Work done by Popolo and/or OParl will be reused.