Skip to content

Schema: Create generic code.json metadata schema#16

Closed
natalialuzuriaga wants to merge 7 commits intomainfrom
nat/generic-schema
Closed

Schema: Create generic code.json metadata schema#16
natalialuzuriaga wants to merge 7 commits intomainfrom
nat/generic-schema

Conversation

@natalialuzuriaga
Copy link
Copy Markdown
Contributor

Problem

We would like to create a generic code.json metadata standard and schema including only mandatory fields for SHARE IT and M-16-21 compliance.

Solution

  • Created schema-1.0.0.json which serves as the generic code.json schema that can be used across any federal agency.
    • Includes fields required for M-16-21, SHARE IT Act, and publiccode.yml
    • Generic schema will live in root directory of schemas
  • Moved CMS schemas to a cms directory

Signed-off-by: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
Signed-off-by: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
Signed-off-by: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
@decause-gov
Copy link
Copy Markdown
Contributor

@sachin-panayil we'll have to update the metadata links on https://dsacms.github.io/share-it-act-lp for new schema location.

Copy link
Copy Markdown
Contributor

@decause-gov decause-gov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM +1 🚢

@natalialuzuriaga
Copy link
Copy Markdown
Contributor Author

TODO: Add docs explaining generic schema and agency-specific schema

@decause-gov
Copy link
Copy Markdown
Contributor

@sachin-panayil disregard, we don't link directly to the metadata in the LP, we link to the docs here: https://github.com/DSACMS/gov-codejson/blob/main/docs/metadata.md and Nat is going to update those :)

Signed-off-by: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
Signed-off-by: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
Signed-off-by: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
Comment thread docs/faq.md

### Is code.json mandatory for all repositories?

Yes. As per M-16-21 and the SHARE IT Act, agencies are required to publish metadata on all custom-developed code after August 8th 2016, which is not subject to exemptions (see: Sec 6 of [M-16-21](https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2016/m_16_21.pdf) and <a target="_blank" href="https://www.congress.gov/bill/118th-congress/house-bill/9566/text/ih#HB45699B7E8734166BE2F6DA2A80F7909">SHARE IT ACT exemptions</a>)
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. As per M-16-21, agencies are required to publish metadata on all custom-developed code after August 8th 2016, which is not subject to exemptions (see: Sec 6 of M-16-21 and

As per the SHARE IT Act, agencies are required to publish metadata on all custom-developed code after July 22, 2025, , which is not subject to exemptions SHARE IT ACT exemptions)

(point to landing page, right to legislation https://www.congress.gov/118/plaws/publ187/PLAW-118publ187.pdf)

Copy link
Copy Markdown
Contributor

@decause-gov decause-gov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After discussing at 1x1 and comments reconciled, LGTM +1 🚢

@natalialuzuriaga
Copy link
Copy Markdown
Contributor Author

Closing due to merge conflict

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants