[Verse 1] In OSCAL's world there are three ways to write XML came first and it shines so bright Full schema validation keeps your data clean The most mature format you've ever seen Curly braces mark the JSON way Modern tooling loves it every day APIs speak this language well JSON Schema helps you tell [Chorus] Three formats, one information model XML, JSON, YAML - they're all compatible Convert between them without losing a bit Lossless transformation, that's the trick Three formats, same data underneath Choose your style but keep the same belief The content stays true no matter which you pick [Verse 2] YAML enters through the JSON door Conversion makes it work for sure It's a superset so the schema fits JSON Schema validates every bit Indentation makes it clean to read Hierarchical structure meets your need No matter which format you decide to choose The information model never lose [Chorus] Three formats, one information model XML, JSON, YAML - they're all compatible Convert between them without losing a bit Lossless transformation, that's the trick Three formats, same data underneath Choose your style but keep the same belief The content stays true no matter which you pick [Bridge] From XML tags to JSON objects YAML lists that interconnect Same security controls expressed three ways Pick the format for your days Tooling changes, preferences shift But the model gives you this gift Flexibility without sacrifice One information model, that's precise [Chorus] Three formats, one information model XML, JSON, YAML - they're all compatible Convert between them without losing a bit Lossless transformation, that's the trick Three formats, same data underneath Choose your style but keep the same belief The content stays true no matter which you pick [Outro] Three formats singing in harmony One model for security OSCAL gives you the choice to make Same information, whatever format you take
← 1 The Three-Layer Architecture | 3 Working with OSCAL Data →