Maintenance Templates

Maintenance Templates

Draft for discussion and revision by the DCAT Interagency Maintenance Team and the Data.gov team.

This page provides reusable templates for operating the DCAT-US v3.0 maintenance process.

Templates may be used or adapted for:

• GitHub issue triage
• Pull request review
• Security considerations notes
• DCAT Interagency Maintenance Team issue review
• Agency feedback summaries
• Release readiness checks
• Release notes
• Changelog entries
• Deprecation notices
• Grace period language
• Post-release outreach
• Annual retrospective summaries
• Annual compliance support summaries
• Meeting notes and action tracking

The DCAT Interagency Maintenance Team governs schema maintenance decisions. The Data.gov team at GSA maintains the DCAT-US repository and coordinates the maintenance cycle.

---

Template Index

Template	Purpose
GitHub Issue Template	Submit a bug, enhancement, or question related to DCAT-US v3.0
Issue Triage Checklist	Support Data.gov triage of new GitHub issues
Maintenance Team Issue Review Template	Support DCAT Interagency Maintenance Team review and disposition
Pull Request Checklist	Review schema or documentation pull requests
Security Considerations Note Template	Document security considerations for changes touching restriction fields
Agency Feedback Summary Template	Summarize feedback from selected agency participants
Release Readiness Checklist	Confirm release readiness before tagging a release
Release Notes Template	Prepare GitHub release notes and outreach summaries
Changelog Entry Template	Document release changes in the changelog
Deprecation Notice Template	Notify agencies of planned breaking changes
Grace Period Language Template	Standard language for 90-day grace periods
Release Announcement Template	Announce a maintenance release
Grace Period Reminder Template	Remind agencies of an active grace period
Post-Release Follow-Up Template	Follow up after release outreach
Meeting Notes Template	Capture meeting notes, decisions, and action items
Action Item Tracker Template	Track follow-up actions
Annual Retrospective Agenda Template	Structure the annual retrospective meeting
Annual Compliance Support Summary Template	Summarize implementation support findings
Documentation Audit Checklist	Review resources.data.gov and related documentation
Example Validation Checklist	Validate example records against the current schema

---

GitHub Issue Template

Use this template for issues submitted to the DCAT-US GitHub repository.

DCAT-US GitHub Issues:
https://github.com/GSA/dcat-us/issues

# Issue Title

Briefly summarize the issue, question, or proposed change.

## Issue Type

Select one:

- [ ] Bug
- [ ] Enhancement
- [ ] Question

## Summary

Briefly describe the issue, proposed change, or question.

## Affected Field or Schema Area

List the affected field, object, enum, or schema area, if applicable.

Examples:

- `accessRestriction`
- `useRestriction`
- `cuiRestriction`
- Dataset-level metadata
- Distribution-level metadata
- Controlled values
- Required fields
- Validation behavior
- Documentation or examples

## Description

Provide details about the issue or proposed change.

Include relevant context such as:

- What behavior is expected
- What behavior is occurring
- Why the issue matters
- Whether this affects implementation
- Whether this affects validation
- Whether this affects existing `data.json` files

## Example

Include example metadata, validation output, screenshots, or implementation behavior, if available.

```json
{
  "example": "Add example metadata here, if applicable"
}

Expected Behavior

Describe what you expected to happen.

Actual Behavior

If this is a bug, describe what happened instead.

Implementation Impact

Describe how this affects agency implementation, validation, harvesting, documentation, or existing data.json files.

Is This Time-Sensitive?

• Yes
• No

If yes, explain the timing need.

Suggested Resolution

Optional: describe a proposed resolution, clarification, or change.

Related Links

Add links to related issues, pull requests, documentation, validation output, or meeting notes.

Additional Context

Add any other context that may help reviewers.

---

# Issue Triage Checklist

Use this checklist when the Data.gov team reviews a new GitHub issue.

```markdown
# Issue Triage Checklist

## Issue Information

**Issue link:**  
**Date submitted:**  
**Date triaged:**  
**Triaged by:**  

## Classification Label

Apply one:

- [ ] `bug` — the schema behaves incorrectly or inconsistently with the specification
- [ ] `enhancement` — a proposed addition or improvement to the schema
- [ ] `question` — a request for clarification on schema intent or behavior

## Scope Review

Is the issue in scope for DCAT-US v3.0 maintenance?

- [ ] Yes
- [ ] No
- [ ] Unsure

If not in scope, route to:

- [ ] Harvest Source Change Request Form
- [ ] Harvest Source Management Board
- [ ] Data.gov Team Board
- [ ] Inventory.data.gov Access Request Form
- [ ] Data.gov Help
- [ ] Other:

## Issue Category

Select all that apply:

- [ ] Schema
- [ ] Documentation
- [ ] Example
- [ ] Validation
- [ ] Implementation guidance
- [ ] FAQ
- [ ] Harvesting
- [ ] Data.gov product issue
- [ ] Standard-level question
- [ ] Potential breaking change
- [ ] Potential non-breaking change
- [ ] Security considerations may be needed

## Affected Field or Schema Area

List affected field, object, enum, or schema area.

## Time Sensitivity

- [ ] Time-sensitive
- [ ] Not time-sensitive
- [ ] Unknown

Notes:

## Initial Routing

- [ ] Assign to Cycle 1 milestone
- [ ] Assign to Cycle 2 milestone
- [ ] Assign to future milestone
- [ ] Leave in backlog
- [ ] Needs DCAT Interagency Maintenance Team review
- [ ] Needs agency feedback
- [ ] Needs documentation review
- [ ] Needs more information
- [ ] Close as out of scope
- [ ] Route elsewhere

## Follow-Up Actions

| Action | Owner | Due Date | Status |
|---|---|---|---|

## Notes

Add triage notes here.

---

Maintenance Team Issue Review Template

Use this template to prepare issues for DCAT Interagency Maintenance Team review.

# Maintenance Team Issue Review

## Issue

**Issue title:**  
**Issue link:**  
**Issue type:** Bug / Enhancement / Question  
**Milestone:** Cycle 1 / Cycle 2 / Future / Backlog  

## Affected Field or Schema Area

List affected field, object, enum, or schema area.

## Summary

Briefly summarize the issue and why it is being reviewed.

## Background

Provide relevant context, including:

- Related GitHub issues
- Related pull requests
- Related documentation
- Agency feedback
- Validation trends
- Prior decisions

## Proposed Resolution

Describe the proposed resolution, if any.

## Change Type

Select one:

- [ ] Non-breaking addition
- [ ] Non-breaking clarification
- [ ] Breaking change
- [ ] Documentation update only
- [ ] FAQ update only
- [ ] Needs more information
- [ ] Other:

## Implementation Impact

Describe likely impact on:

- Agency metadata workflows
- Existing `data.json` files
- Validation behavior
- Data.gov harvesting
- Data.gov display or discoverability
- Documentation or examples

## Security Considerations

Does this issue touch any of the following fields?

- [ ] `accessRestriction`
- [ ] `useRestriction`
- [ ] `cuiRestriction`
- [ ] None of the above

If yes, a security considerations note is required in the pull request.

## Agency Feedback Needed?

- [ ] Yes
- [ ] No
- [ ] Unsure

If yes, describe what feedback is needed.

## Recommended Disposition

Select one:

- [ ] Approved for PR
- [ ] Deferred
- [ ] Closed as won’t fix
- [ ] Needs more information
- [ ] Documentation update only
- [ ] FAQ update only
- [ ] Other:

## Decision

Document the final decision.

## Follow-Up Actions

| Action | Owner | Due Date | Status |
|---|---|---|---|

## Notes

Add discussion notes here.

---

Pull Request Checklist

Use this checklist for schema-related or documentation-related pull requests.

# Pull Request Checklist

## Pull Request Information

**PR link:**  
**Related issue:**  
**Release cycle:** Cycle 1 / Cycle 2 / Other  
**Prepared by:**  

## General Review

- [ ] Pull request is linked to a GitHub issue.
- [ ] Issue disposition is documented.
- [ ] Pull request scope is clear.
- [ ] Change has been reviewed for consistency with DCAT-US v3.0.
- [ ] Change has been reviewed for implementation impact.
- [ ] Change has been reviewed for validation impact.
- [ ] Change has been reviewed for documentation impact.

## Change Type

Select one:

- [ ] Non-breaking addition
- [ ] Non-breaking clarification
- [ ] Breaking change
- [ ] Documentation update only
- [ ] Example update only
- [ ] Other:

## Breaking Change Review

If this is a breaking change:

- [ ] Deprecation notice was issued in a prior cycle.
- [ ] Minimum 90-day agency implementation window has been considered.
- [ ] Agency impacts are documented.
- [ ] Migration guidance is included or planned.
- [ ] Release notes clearly identify the breaking change.

## Security Considerations

Does this PR touch any of the following fields?

- [ ] `accessRestriction`
- [ ] `useRestriction`
- [ ] `cuiRestriction`
- [ ] None of the above

If yes:

- [ ] Security considerations note is included.
- [ ] Security considerations note has been reviewed.

## Documentation

- [ ] Documentation updates are included.
- [ ] Documentation updates are linked.
- [ ] Documentation updates are not needed.
- [ ] FAQ update is needed.
- [ ] Migration guidance is needed.
- [ ] Example update is needed.

## Validation

- [ ] Example records have been validated, if applicable.
- [ ] Validation behavior has been reviewed.
- [ ] Any expected validation changes are documented.

## Release Preparation

- [ ] Changelog entry is included or drafted.
- [ ] Release notes text is included or drafted.
- [ ] `conformsTo` URI impact has been considered.
- [ ] Agency outreach impacts have been considered.

## Reviewer Notes

Add reviewer notes here.

---

Security Considerations Note Template

Schema changes touching accessRestriction, useRestriction, or cuiRestriction must include a security considerations note in the pull request.

# Security Considerations Note

## Affected Field or Schema Area

Select all that apply:

- [ ] `accessRestriction`
- [ ] `useRestriction`
- [ ] `cuiRestriction`
- [ ] Other:

## Summary of Change

Describe the proposed change.

## Reason for Change

Explain why the change is being made.

## Impact on Metadata Representation

Describe whether the change affects how agencies represent:

- Access restrictions
- Use restrictions
- CUI-related restrictions
- Public or non-public data
- Sensitive or controlled data descriptions

## Impact on Validation

Describe whether the change affects validation behavior.

## Impact on Existing Implementations

Describe whether existing `data.json` implementations may need to change.

## Agency Review Considerations

Describe what agencies should review or consider before implementing this change.

## Related Documentation

List any related documentation or guidance updates.

## Notes

Add any additional considerations here.

---

Agency Feedback Summary Template

Use this template to summarize feedback received from selected agencies.

# Agency Feedback Summary

## Meeting Date

YYYY-MM-DD

## Release Cycle

Select one:

- [ ] Cycle 1 Spring Release
- [ ] Cycle 2 Summer Release
- [ ] Annual Retrospective
- [ ] Other:

## Issue or Topic

GitHub issue link, field name, schema area, documentation topic, or release topic.

## Participating Agencies

List participating agencies and roles, if appropriate.

## Purpose of Feedback

Describe what feedback was requested.

## Summary of Proposed Change or Discussion Topic

Briefly summarize the issue, proposed change, clarification, or documentation topic.

## Agency Feedback

Summarize feedback received from agencies.

## Implementation Impacts

Describe potential impacts to:

- Agency metadata workflows
- Existing `data.json` files
- Validation
- Harvesting
- Data.gov display or discoverability
- Internal agency processes

## Documentation or Guidance Needs

List any needed:

- Documentation updates
- Examples
- FAQs
- Migration guidance
- Office hours topics
- Info sharing session topics

## Risks or Blockers

List known risks, blockers, or timing concerns.

## Recommended Next Steps

List recommended follow-up actions.

## Related Links

- GitHub issue:
- Pull request:
- Documentation:
- Meeting notes:
- Release notes:

---

Release Readiness Checklist

Use this checklist before tagging a maintenance release.

# Release Readiness Checklist

## Release Information

**Release version:**  
**Target release date:**  
**Release cycle:** Cycle 1 / Cycle 2 / Other  
**Prepared by:**  

## Issue Review

- [ ] Issues assigned to the cycle milestone have been reviewed.
- [ ] Issue dispositions have been documented.
- [ ] Approved pull requests are identified.
- [ ] Deferred issues are documented.
- [ ] Closed issues are documented.
- [ ] Documentation-only issues are documented.
- [ ] Issues needing more information are documented.

## Pull Requests

- [ ] Approved pull requests are ready to merge.
- [ ] Pull requests are linked to issues.
- [ ] Pull requests have been reviewed.
- [ ] Change type is identified for each pull request.
- [ ] Breaking changes have prior deprecation notice, if applicable.
- [ ] Minimum 90-day agency implementation window has been considered, if applicable.

## Security Considerations

Security considerations notes are included for changes touching:

- [ ] `accessRestriction`
- [ ] `useRestriction`
- [ ] `cuiRestriction`
- [ ] Not applicable

## Documentation

- [ ] Documentation updates are complete or tracked.
- [ ] P1 documentation issues are resolved, if Cycle 1.
- [ ] P1 and P2 documentation issues are resolved, if Cycle 2.
- [ ] Example records have been validated against the current schema.
- [ ] resources.data.gov pages have been reviewed, if applicable.
- [ ] Migration guidance is complete or scheduled, if needed.
- [ ] FAQ updates are complete or tracked, if needed.

## Changelog and Release Notes

- [ ] Changelog entry is drafted.
- [ ] GitHub release notes are drafted.
- [ ] Release notes identify schema changes.
- [ ] Release notes identify documentation changes.
- [ ] Release notes identify breaking changes, if applicable.
- [ ] Release notes include deprecation notices, if applicable.
- [ ] Release notes include grace period language, if applicable.
- [ ] Release notes include agency action items.
- [ ] Release notes include contact information.

## Versioning

- [ ] Release tag follows semantic versioning.
- [ ] `conformsTo` URI update decision has been confirmed.
- [ ] Major version impacts have been considered, if relevant.

## Outreach

- [ ] CDO Council channel announcement is drafted.
- [ ] Data.gov mailing list announcement is drafted.
- [ ] GitHub release notes are ready.
- [ ] Info Sharing Session topic is planned, if needed.
- [ ] Office hours are prepared for follow-up questions.

## Final Decision

- [ ] Ready to release.
- [ ] Not ready to release.

## Notes

Add notes here.

---

Release Notes Template

Use this template for GitHub release notes and agency-facing summaries.

# DCAT-US v3.0 Maintenance Release [Version Number]

**Release date:** YYYY-MM-DD  
**Release cycle:** Cycle 1 Spring Release / Cycle 2 Summer Release  
**Release tag:** [Link to GitHub release tag]  

## Summary

Briefly summarize the purpose of this release.

## Changes in This Release

### Schema Changes

- Change 1
- Change 2
- Change 3

### Documentation Changes

- Documentation update 1
- Documentation update 2

### Bug Fixes

- Bug fix 1
- Bug fix 2

### Enhancements

- Enhancement 1
- Enhancement 2

### Clarifications

- Clarification 1
- Clarification 2

## Breaking Changes

- [ ] This release includes breaking changes.
- [ ] This release does not include breaking changes.

If breaking changes are included, describe them here.

## Deprecation Notices

Include any deprecation notices here.

## Grace Period

Agencies will have a 90-day grace period before any new requirements introduced in this release are enforced.

Grace period start date:  
Grace period end date:  

## Agency Action Items

Agencies should:

- Review this release note.
- Review updated documentation.
- Assess whether metadata generation workflows are affected.
- Validate updated metadata files, if applicable.
- Bring implementation questions to DCAT Interagency Q&A Office Hours, if needed.

## Migration Guidance

Include link to migration guidance, if applicable.

## Changelog

Include link to changelog.

## Related Issues and Pull Requests

- Issue:
- Pull request:

## Documentation

- DCAT-US 3 Implementation Guide:
- Technical FAQs:
- Other documentation:

## Questions

Questions about Data.gov harvesting or resources.data.gov documentation can be directed to:

datagovhelp@gsa.gov

Requests or issues related to the DCAT-US metadata standard may be submitted through GitHub Issues:

https://github.com/GSA/dcat-us/issues

---

Changelog Entry Template

Use this template for changelog entries.

# Changelog Entry: DCAT-US v3.0 [Version Number]

**Release date:** YYYY-MM-DD  
**Release tag:** [Link]  

## Summary

Briefly summarize this release.

## Added

- Added item 1
- Added item 2

## Changed

- Changed item 1
- Changed item 2

## Fixed

- Fixed item 1
- Fixed item 2

## Deprecated

- Deprecated item 1
- Deprecated item 2

## Removed

- Removed item 1
- Removed item 2

## Documentation

- Documentation update 1
- Documentation update 2

## Migration Guidance

Include migration guidance link or note if not applicable.

## Related Issues

- Issue 1
- Issue 2

## Related Pull Requests

- PR 1
- PR 2

---

Deprecation Notice Template

Use this template when a breaking change is planned for a future release.

# Deprecation Notice

## Affected Field or Schema Area

Describe the field, enum, object, or schema area affected by the planned change.

## Planned Change

Describe the planned change.

## Reason for Change

Explain why the change is being proposed.

## Expected Release Timing

Identify the release cycle when the change may be included.

## Change Type

- [ ] Breaking change
- [ ] Potential breaking change
- [ ] Other:

## Impact

Describe how this may affect:

- Agency metadata
- Existing `data.json` files
- Validation
- Harvesting
- Data.gov display or discoverability
- Metadata generation workflows

## Agency Action

Describe what agencies should do to prepare.

## Implementation Window

Agencies will have a minimum 90-day implementation window before enforcement.

## Documentation or Migration Guidance

List related documentation or migration guidance.

## Questions and Feedback

Agencies may ask questions through DCAT Interagency Q&A Office Hours or submit standard-level feedback through DCAT-US GitHub Issues:

https://github.com/GSA/dcat-us/issues

---

Grace Period Language Template

Use this standard language in release notes and agency communications when a grace period applies.

Agencies will have a 90-day grace period before any new requirements introduced in this release are enforced. During this period, agencies should review the release notes, assess any implementation impacts, update metadata generation workflows as needed, and validate updated metadata files.

Agencies may bring implementation questions to DCAT Interagency Q&A Office Hours or contact Data.gov Help at datagovhelp@gsa.gov for questions related to Data.gov harvesting or resources.data.gov documentation.

---

Release Announcement Template

Use this template to announce a maintenance release.

Subject: DCAT-US v3.0 Maintenance Release [Version Number]

The Data.gov team has published DCAT-US v3.0 maintenance release [Version Number].

Release notes are available here:

[GitHub release notes link]

Summary of changes:

- [Change 1]
- [Change 2]
- [Change 3]

Documentation updates are available here:

[Documentation link]

Agencies will have a 90-day grace period before any new requirements introduced in this release are enforced.

Agencies should review the release notes and updated documentation to determine whether any metadata, validation, or harvesting updates are needed.

Questions about DCAT-US implementation may be brought to DCAT Interagency Q&A Office Hours. Questions about Data.gov harvesting or resources.data.gov documentation may be sent to datagovhelp@gsa.gov.

Requests or issues related to the DCAT-US metadata standard may be submitted through GitHub Issues:

https://github.com/GSA/dcat-us/issues

---

Grace Period Reminder Template

Use this template to remind agencies that a grace period is active.

Subject: Reminder: DCAT-US v3.0 Release [Version Number] Grace Period

This is a reminder that DCAT-US v3.0 release [Version Number] included a 90-day grace period before any new requirements are enforced.

Grace period start date: [Date]  
Grace period end date: [Date]

Agencies should review the release notes and updated documentation and make any needed metadata or validation updates before the grace period ends.

Release notes:

[GitHub release notes link]

Updated documentation:

[Documentation link]

Questions may be brought to DCAT Interagency Q&A Office Hours or sent to datagovhelp@gsa.gov for Data.gov harvesting or resources.data.gov documentation questions.

---

Post-Release Follow-Up Template

Use this template after release outreach.

Subject: Follow-Up: DCAT-US v3.0 Release [Version Number]

Thank you to agencies that reviewed DCAT-US v3.0 release [Version Number] and participated in recent discussions.

Common questions and follow-up items are being tracked and may be added to the DCAT-US technical implementation FAQs:

https://github.com/GSA/dcat-us/wiki/DCAT-US-3-Technical-Implementation-FAQ

If your agency identifies a possible issue or requested change to the DCAT-US metadata standard, please submit a GitHub issue:

https://github.com/GSA/dcat-us/issues

For questions about Data.gov harvesting or resources.data.gov documentation, contact:

datagovhelp@gsa.gov

---

Meeting Notes Template

Use this template for maintenance-related meetings.

# Meeting Notes

## Meeting Name

## Date

YYYY-MM-DD

## Participants

List participants.

## Purpose

Briefly describe the purpose of the meeting.

## Agenda

1. Agenda item
2. Agenda item
3. Agenda item

## Issues or Topics Reviewed

List issues or topics reviewed.

## Decisions

Document decisions made.

## Follow-Up Actions

| Action | Owner | Due Date | Status |
|---|---|---|---|

## Risks or Blockers

List risks or blockers identified.

## Related Links

- GitHub issues:
- Pull requests:
- Documentation:
- Release notes:
- Meeting materials:

---

Action Item Tracker Template

Use this template to track follow-up actions.

# Action Item Tracker

| Action ID | Action | Owner | Due Date | Status | Related Link |
|---|---|---|---|---|---|
| 001 |  |  |  | Not started / In progress / Complete / Blocked |  |
| 002 |  |  |  | Not started / In progress / Complete / Blocked |  |
| 003 |  |  |  | Not started / In progress / Complete / Blocked |  |

---

Annual Retrospective Agenda Template

Use this template for the annual retrospective meeting.

# Annual Retrospective Agenda

## Meeting Date

YYYY-MM-DD

## Purpose

Review DCAT-US v3.0 implementation experience, validation trends, documentation gaps, agency blockers, release process lessons learned, and priorities for the next annual maintenance cycle.

## Agenda

### 1. Welcome and Objectives

- Confirm purpose of the retrospective
- Review desired outputs
- Confirm agenda

### 2. Review of Maintenance Year

- Review Cycle 1 activities
- Review Cycle 2 activities
- Review release outcomes
- Review major schema or documentation updates

### 3. Validation Trend Review

- Review harvest validation error trends
- Review New Relic data
- Identify recurring field-level patterns

### 4. Agency Feedback Review

- Summarize agency feedback
- Identify recurring blockers or questions

### 5. Documentation and Guidance Review

- Identify documentation gaps
- Identify needed examples, FAQs, or migration guidance

### 6. Issue and Release Process Review

- Review GitHub issue workflow
- Review triage timing
- Review milestone use
- Review release communications

### 7. Compliance Support Summary

- Discuss agency cohorts that may benefit from targeted implementation assistance
- Confirm summary findings

### 8. Lessons Learned

- Discuss what worked well
- Discuss what should be improved

### 9. Next-Cycle Priorities

- Identify priorities for the next annual maintenance cycle
- Assign follow-up actions

### 10. Wrap-Up

- Confirm action items
- Confirm owners
- Confirm timeline for retrospective outputs

---

Annual Compliance Support Summary Template

Use this template to summarize implementation support findings from the annual retrospective.

# Annual Compliance Support Summary

## Review Period

Start date:  
End date:

## Purpose

This summary identifies implementation support needs related to DCAT-US v3.0. It is intended as an implementation support tool and is not an enforcement document.

## Data Sources Reviewed

- Harvest validation trends
- New Relic data
- GitHub issues
- Office hours questions
- Info sharing session topics
- Agency feedback
- Documentation issues
- Data.gov Help questions

## Summary of Key Findings

Summarize the most important findings from the review period.

## Validation Trends

Describe recurring validation errors or patterns.

## Field-Level Error Patterns

List fields or schema areas with recurring issues.

## Agency Implementation Blockers

Summarize common blockers identified by agencies.

## Documentation and Guidance Gaps

Identify needed documentation, FAQ, migration guidance, or example updates.

## Agency Cohorts for Targeted Support

Identify agency groups that may benefit from targeted assistance.

## Recommended Support Activities

Examples:

- Office hours topic
- Info sharing session topic
- Direct outreach
- Documentation update
- FAQ update
- Validation guidance
- Migration guidance

## Recommended GitHub Issues or Maintenance Actions

List issues to file or prioritize.

## Lessons Learned

Document process or implementation lessons learned.

## Priorities for Next Annual Cycle

List recommended priorities for the next annual maintenance cycle.

## Related Links

- GitHub issues:
- Documentation:
- Release notes:
- Meeting notes:

---

Documentation Audit Checklist

Use this checklist when reviewing resources.data.gov or related documentation against the live schema.

# Documentation Audit Checklist

## Documentation Page

**Page title:**  
**Page URL:**  
**Reviewed by:**  
**Review date:**  

## Schema Alignment

- [ ] Page aligns with current DCAT-US v3.0 schema.
- [ ] Field names are current.
- [ ] Field definitions are current.
- [ ] Required, recommended, and optional field guidance is current.
- [ ] Controlled values or enums are current.
- [ ] Examples align with current schema.
- [ ] Validation behavior described is current.
- [ ] Links are current.

## Issues Found

List any issues found.

## Follow-Up Needed

- [ ] Documentation update needed.
- [ ] Example update needed.
- [ ] FAQ update needed.
- [ ] GitHub issue needed.
- [ ] No action needed.

## Follow-Up Actions

| Action | Owner | Due Date | Status |
|---|---|---|---|

## Notes

Add notes here.

---

Example Validation Checklist

Use this checklist when validating example records in documentation.

# Example Validation Checklist

## Example Information

**Example name:**  
**Documentation page:**  
**Reviewed by:**  
**Review date:**  

## Validation

- [ ] Example was validated against the current schema.
- [ ] Example passed validation.
- [ ] Example failed validation.
- [ ] Validation warnings were reviewed.
- [ ] Validation errors were reviewed.

## Validation Results

Summarize validation results.

## Issues Found

List issues found in the example.

## Follow-Up Needed

- [ ] Example update needed.
- [ ] Documentation update needed.
- [ ] Schema issue identified.
- [ ] FAQ update needed.
- [ ] No action needed.

## Follow-Up Actions

| Action | Owner | Due Date | Status |
|---|---|---|---|

## Notes

Add notes here.

---

Related Resources

DCAT-US GitHub Issues

https://github.com/GSA/dcat-us/issues

Use this issue tracker to request or discuss changes to the DCAT-US metadata standard itself.

---

DCAT-US GitHub Repository

https://github.com/GSA/dcat-us

Repository for the DCAT-US metadata standard.

---

DCAT-US 3 Implementation Guide

https://resources.data.gov/resources/dcat-us-3-implementation/

Primary reference for agencies implementing the DCAT-US 3 metadata standard.

---

DCAT-US 3 Technical Implementation FAQs

https://github.com/GSA/dcat-us/wiki/DCAT-US-3-Technical-Implementation-FAQ

Frequently asked questions related to technical implementation of the DCAT-US 3 metadata standard are posted here as they are developed.

---

DCAT-US 3 Updates

https://resources.data.gov/resources/dcat-us-3-updates/

Use this page for meeting schedule updates and related DCAT-US 3 engagement information.

---

Data.gov Help

Questions about Data.gov harvesting or resources.data.gov documentation can be directed to:

datagovhelp@gsa.gov

---

Related Wiki Pages

• DCAT Interagency Maintenance Team
• Maintenance Process Overview
• Roles and Responsibilities
• Issue Triage and GitHub Workflow
• Semi-Annual Release Cycles
• Agency Feedback and Participation
• Release Communications and Outreach
• Annual Retrospective
• Maintenance Meeting Schedule