DCAT US 3 Technical Implementation FAQ

DCAT-US 3.0

Is the DCAT-US 3.0 harvester stable enough to test against, or should we wait for production?

Core DCAT-US 3.0 support in the harvester has landed and has no open known defects as of this writing. We appreciate agencies testing against it, and it's likely we'll need to make some fixes as this is new. Testing against a test harvest source is reasonable, and the ingested output should be a fair preview of production behavior.

A couple of caveats before relying on it for anything final:

• Guidance on some edge cases is still being finalized, including how to represent theme: geospatial and how to link ISO/CSDGM records as distributions.
• A standardized "dev/test report" process, so agencies can get a clear before-you-go-live confirmation, is still in development. Until it's ready, the harvest source's own validation output is the best signal available.

Bring any edge cases you hit to DCAT Interagency Q&A Office Hours.

DA, last edited 2026-08-31

What's the difference between accessRestriction, useRestriction, and accessRights, and what values go in them?

These go on the Distribution inside the Dataset. accessRestriction and useRestriction describe a specific file or distribution inside a dataset.

Here are the descriptions of each field. The examples are pulled from other datasets, they're non-exhaustive and are an assumption of common usage.

• accessRestriction = who's allowed to access it
  • restrictionStatus: Restricted - Fully, Restricted - Partly, Restricted - Possibly, Undetermined, Unrestricted
  • specificRestriction: FOIA (b)(4) Trade Secrets and Commercial or Financial Information, FOIA (b)(6) Personal Information, FOIA (b)(8) Regulation or Supervision of Financial Institutions, Executive Privilege (full NARA list)
• useRestriction = what they're allowed to do with it once they have it
  • restrictionStatus: same five options as above
  • specificRestriction: Copyright, Donor Restrictions, Trademark, Service Mark, Other (full NARA list)

Both accessRestriction and useRestriction are optional (Recommended). If your data doesn't need this level of detail, just use accessRights instead.

• accessRights = a plain-text alternative when you don't need structured restriction data
  • example values: "Public", "Restricted", "Non-public"

Why the examples in the guide look different: restrictionStatus is typed as a Concept, which accepts three valid shapes, and the guide shows all three:

• "restrictionStatus": "Restricted"
• "restrictionStatus": "https://example.gov/concepts/restricted"
• "restrictionStatus": { "@type": "Concept", "prefLabel": "Restricted - Commercial Use" }

All three are valid. They represent different levels of detail for the same field. Unless you have an actual shared vocabulary you're linking to, use the plain string.

Example for a supervisory dataset with financial institution restrictions:

"accessRestriction": [
  {
    "restrictionStatus": "Restricted - Fully",
    "specificRestriction": "FOIA (b)(8) Regulation or Supervision of Financial Institutions"
  }
]

DA, last edited 2026-08-31