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.
publisher: ["Office of Citizen Services and Innovative Technologies", "General Services Administration", "U.S. Government"]
This is much easier to parse than the current schema. You will appreciate my concerns, If you have tried to model a parent-child relationship in a relational database table.
The text was updated successfully, but these errors were encountered:
There doesn't seem to be anything hierarchical about that and I'm not sure I understand what's challenging about parsing hierarchical relationships in JSON.
The current proposal in v1.1 (see #296) is intended to be more explicit about these relationships and to align with the DCAT definition which recommends foaf:Agent which means we can use org:subOrganizationOf to describe the hierarchical relationship.
Specifying a hierarchical relationship is totally optional though.
If you have additional feedback related to the updates to the publisher field, would you mind adding it to #296 instead?
publisher: ["Office of Citizen Services and Innovative Technologies", "General Services Administration", "U.S. Government"]
This is much easier to parse than the current schema. You will appreciate my concerns, If you have tried to model a parent-child relationship in a relational database table.
The text was updated successfully, but these errors were encountered: