Should public meeting fields be replaced by/use the openconsult standard? #13
Description
We plan to develop a standard for the publishing of past and future consultation events:
https://github.com/bcgov/openconsult
How to harmonize these projects?
Option 1: Follow the openconsult schema in defining fields within the LUCD standard.
Option 2: Move public meeting information out of the scope of the LUCD standard, and recommend that users also publish that information separately to the openconsult standard. Include an "ApplicationId" field that can map from openconsult entries to LUCD entries.
The second option would effectively make openconsult data another optional dataset (like documents or status changes) while still keeping it usable in non-application contexts.