The same way we are not trying to reinvent the wheel when it comes to the objects & fields, we are not trying to do it when it comes to the “sub schemas” either. Think of it like this: a public notice is an announcement about some ‘thing', e.g. a court decision, a procurement, a public hearing etc. Many of these therefore have their own separate schemas. For instance, for procurement, we plan to implement the open-contracting format (http://ocds.open-contracting.org/standard/r/1__0__RC/en/schema/release/ ). The challenge will be to connect these individual objects to the notice skeleton, as well as making sure that our notice attributes (addresses, items, organizations, etc.) are standardized across the board. That way users will be able to pull an individual notice and get all the related details needed to recreate something like the “original” notice, but the user can also pull the procurement (or other) object directly, as a standalone object. - Mikael
The same way we are not trying to reinvent the wheel when it comes to the objects & fields, we are not trying to do it when it comes to the “sub schemas” either. Think of it like this: a public notice is an announcement about some ‘thing', e.g. a court decision, a procurement, a public hearing etc. Many of these therefore have their own separate schemas. For instance, for procurement, we plan to implement the open-contracting format (http://ocds.open-contracting.org/standard/r/1__0__RC/en/schema/release/ ). The challenge will be to connect these individual objects to the notice skeleton, as well as making sure that our notice attributes (addresses, items, organizations, etc.) are standardized across the board. That way users will be able to pull an individual notice and get all the related details needed to recreate something like the “original” notice, but the user can also pull the procurement (or other) object directly, as a standalone object. - Mikael