Exercise 3: Why OO, Free-Format, and XML/JSON Are Separate Real Additions, Not One Redesign — Possible Solution ==================================================================== WHAT THIS CHAPTER'S OWN MATERIAL ESTABLISHES ABOUT TIMING This chapter's own real material is specific about when each of these three genuinely arrived. Object orientation and free-format source both arrived together in the real 2002 revision - this chapter states directly that COBOL 2002 "added object-oriented syntax and free-format source together, in the same single revision." XML processing, by contrast, is described as being "addressed through Technical Reports published between 2003 and 2009" - genuinely years after the 2002 revision that introduced OO and free-format. JSON handling is described as "a later addition still." WHY THESE WERE ADDED FOR DIFFERENT REAL REASONS This chapter's own material ties each addition to its own distinct real motivation. Object orientation and free-format arrived together specifically because of "a genuine, practical need: real interoperability with newer platforms like .NET and Java" - a real concern about how COBOL programs would work alongside other systems written in newer, object-oriented languages. XML and JSON, described separately as data-interchange extensions, exist "letting a COBOL program genuinely produce and consume the data formats modern web-facing systems actually expect" - a different, later real concern about exchanging data with web-facing systems, not about object-oriented interoperability specifically. WHY DIFFERENT TIMING AND DIFFERENT MOTIVATIONS MEAN SEPARATE ADDITIONS Because these three capabilities arrived at genuinely different real points (2002 for OO/free-format, 2003-2009 for XML, later still for JSON) and were driven by genuinely different real practical needs (language interoperability vs. data-format interchange), they represent separate, independently-motivated real additions layered onto the language over time - not features designed together as part of one single, unified redesign effort. A single coordinated redesign would typically be conceived and delivered together, addressing a shared set of goals at one point in time; these three instead solved different real problems as they arose, years apart from each other. ANSWER: Object orientation and free-format source arrived together in the real 2002 revision, driven by a genuine need for interoperability with newer platforms like .NET and Java, while XML processing was addressed separately through Technical Reports published years later, between 2003 and 2009, and JSON support arrived later still - both motivated by a different real concern, letting COBOL exchange data with modern web-facing systems rather than interoperate with object-oriented platforms specifically. Because these capabilities arrived at genuinely different real points in time and were driven by different practical motivations, they represent separate additions layered onto the language as distinct real needs arose, rather than features conceived together as part of one single, unified redesign. WHY THIS WORKS AS AN ANSWER ------------------------------ This correctly cites the specific real timing and distinct motivations this chapter attaches to each addition, using both facts together to explain why they're genuinely separate layers rather than one coordinated effort.