You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 18, 2024. It is now read-only.
Because data.json is being used widely, including on all Socrata portals, that spread across municipal and state governments, does it make sense to require bureauCode and programCode as Always required in the documentation? Should it be changed to If-Applicable?
The impact is trivial, but semantically useful. In the case of Chicago, there will never be a bureauCode or programCode since it doesn't apply, breaking the recommendations of the format.
The text was updated successfully, but these errors were encountered:
I think changing the distinction to 'If-Applicable' might confuse federal implementers, but please share any ideas about how to make this more conspicuous.
Because data.json is being used widely, including on all Socrata portals, that spread across municipal and state governments, does it make sense to require bureauCode and programCode as Always required in the documentation? Should it be changed to If-Applicable?
The impact is trivial, but semantically useful. In the case of Chicago, there will never be a bureauCode or programCode since it doesn't apply, breaking the recommendations of the format.
The text was updated successfully, but these errors were encountered: