About
Standards Crosswalks connect state mathematics standards to their closest matching Common Core State Standards (CCSSM) based on measurable overlap of Learning Components. Crosswalks provide developers and content providers with a scalable way to extend mappings from CCSSM to state-specific frameworks without having to independently replicate matching logic. By leveraging the LC superset, crosswalks show where state and CCSSM standards converge in content coverage. This data can be used to more easily adapt content aligned to CCSSM for use in specific jurisdictionsKey characteristics
- Evidence-based mapping: Crosswalks are built only when standards share at least one LC.
- Similarity measurement: Each relationship includes a jaccard similarity score and supporting counts of LCs.
- Directionality: Crosswalks always connect from a state standard → CCSSM standard and not between states.
- Scope: Limited to math standards in states where LC alignment exists.
Data relationship diagram
Diagram description
Diagram description
The diagram shows the Standards Crosswalks dataset only: state mathematics standards mapped to Common Core State Standards. Both endpoints are
StandardsFrameworkItem (defined in Academic Standards). Direction is always state → CCSS, not between states. Edge properties include jaccard and LC counts; see Relationship properties below.Example (New York → CCSS): A state standard is a StandardsFrameworkItem from a state framework—e.g. NY 3.NF.1 (Understand a fraction 1/b as the quantity formed by 1 part when a whole is partitioned into b equal parts). A CCSS standard is a StandardsFrameworkItem from Common Core Math—e.g. 3.NF.A.1. A hasStandardAlignment edge connects them when they share at least one Learning Component; the edge has properties such as jaccard (e.g. 0.85), stateLCCount, ccssLCCount, sharedLCCount. So: NY 3.NF.1 -[:hasStandardAlignment]-> 3.NF.A.1. Crosswalks are only state → CCSS (never state → state).Edge list (source → relationship → target):StandardsFrameworkItem(state) →hasStandardAlignment→StandardsFrameworkItem(CCSS) (e.g. NY 3.NF.1 → 3.NF.A.1)
Relationships
Each crosswalk is represented as a directional relationship:(State standard) -[:hasStandardAlignment]-> (CCSS standard).
Relationship properties
The relationship includes quantitative measures of similarity:| Property | Description |
|---|---|
jaccard | Proportion of shared LCs between state and CCSS standards (0 < jaccard ≤ 1). |
stateLCCount | Number of Learning Components supporting the state standard. |
ccssLCCount | Number of Learning Components supporting the CCSS standard. |
sharedLCCount | Number of Learning Components shared by both standards. |
hasStandardAlignment edge represents an evidence-based connection.
The Jaccard index measures similarity between two sets — here, the sets of Learning Components that support each standard.Jaccard = Shared Learning Components ÷ (State Learning Components + CCSS Learning Components − Shared Learning Components)
- Score of 1.0 – Standards share all of their Learning Components
- Score of 0.0 – Standards share none of their Learning Components
-
Scores between 0 and 1 – Standards have partial overlap, with higher values representing stronger similarity.
Example: If a state standard has 5 Learning Components, a CCSSM standard has 6, and they share 4 of them, their Jaccard index would be calculated as follows:Jaccard = 4/(5+6−4) = 0.57i.e., about 57% of these standards’ underlying skills overlap
StandardsFrameworkItem entity is defined in Academic Standards.hasStandardAlignment
A hasStandardAlignment connects a State Standard StandardsFrameworkItem to a CCSS Standard StandardsFrameworkItem when the two share overlapping Learning Components.
(:StandardsFrameworkItem) -[:hasStandardAlignment]-> (:StandardsFrameworkItem)
example.json