q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
THE JOURNEY THROUGH TIME

Explore Black History

Explore the people, places, events, achievements, struggles and stories that shaped our journey.

✊🏾

Civil Rights

Movements, leaders, victories and the continuing fight for equality.

⚙️

Black Inventors

Innovation, patents, science, technology and world-changing contributions.

🏆

Sports

Pioneers, champions, Negro Leagues, records, activism and excellence.

♟️

People

Meet the people whose lives, choices and achievements shaped the journey.

📍

Places

Black towns, communities, institutions and places where history happened.

📜

Events

Moments that changed communities, movements, institutions and the nation.

Enter a person, place, event, or topic.
MY'STORY

The MOVE Fire

This is a personal recollection on the Move fire on May 13, 1985 Philadelphia police fired thousands of rounds at the MOVE house, city officials approved dropping an explosive device on the roof, the resulting fire was allowed to burn, 11 people—including five children—died, and 61 homes were destroyed. Philadelphia City Council later called it a “brutal attack carried out by the City of Philadelphia on its own citizens” and acknowledged that no individual faced criminal consequences for the bombing. One timeline correction worth preserving for the BHP record: the major previous MOVE-police confrontation was August 8, 1978, about seven years before the bombing, not a year or two earlier. Officer James Ramp was killed, other police and firefighters were wounded, nine MOVE members were later convicted, and television cameras recorded police beating Delbert Africa during his arrest. The 1985 MOVE Commission later specifically criticized city planners for failing to adequately use lessons from that 1978 confrontation. And that actually strengthens the point you’re making: 1985 did not happen without precedent or institutional memory. There had already been a deadly confrontation with MOVE, years of conflict, negotiations and police involvement before Osage Avenue.

MORE →
BLACK FACTS
The Truths They Never Taught You...

Shirley Chisholm — Unbought and Unbossed

In 1968 Shirley Chisholm became the first Black woman elected to the United States Congress. In 1972 she launched a campaign for the Democratic presidential nomination, breaking another political barrier.

MORE →
BHP gathered finds from its connected research sources. Showing the 4 strongest Black History matches.
← BACK TO RESULTS
Wikipedia

Forward compatibility

Forward compatibility or upward compatibility is a design characteristic that allows a system to accept input intended for a later version of itself. The concept can be applied to entire systems, electrical interfaces, telecommunication signals, data communication protocols, file formats, and programming languages. A standard supports forward compatibility if a product that complies with earlier versions can "gracefully" process input designed for later versions of the standard, ignoring new parts which it does not understand.

The W3C's Technical Architecture Group (TAG) defines the concept more formally: "a change in the definition of a language is forward compatible if consumers of the original language can correctly process text written for the evolved version of the language".[1]

The objective for forward-compatible technology is for old devices to recognise when data has been generated for new devices.[2]

Forward compatibility for the older system usually means backward compatibility for the new system, i.e. the ability to process data from the old system; the new system usually has full compatibility with the older one, by being able to both process and generate data in the format of the older system.

Forward compatibility is not the same as extensibility. A forward compatible design can process at least some of the data from a future version of itself. An extensible design makes upgrading easy. An example of both design ideas can be found in web browsers. At any point in time, a current browser is forward-compatible if it gracefully accepts a newer version of HTML, whereas how easily the browser code can be upgraded to process the newer HTML determines how extensible it is.

Design principles

[edit]

The W3C Technical Architecture Group has documented a family of substitution rules that enable forward-compatible language design. Each rule specifies how a consumer should behave when it encounters constructs it does not recognize:

  • Must ignore unknowns — a consumer that encounters an unrecognized construct must continue processing, treating the construct as if it were not there.[3]
  • Must accept and discard unknowns — a consumer must accept unknown constructs at defined extension points and then discard them.[3]
  • Must accept and preserve unknowns — a consumer must accept unknown constructs and, when forwarding or transforming the content, preserve them for downstream consumers.[3]

These rules underlie forward compatibility in widely deployed languages and protocols. HTTP/1.1, for example, specifies that unrecognized header fields should be ignored by the recipient and must be forwarded by transparent proxies — a direct application of the "preserve unknowns" rule.[4]

Examples

[edit]

Telecommunication standards

[edit]

The introduction of FM stereo transmission, or color television, allowed forward compatibility, since monophonic FM radio receivers and black-and-white TV sets still could receive a signal from a new transmitter.[2] It also allowed backward compatibility since new receivers could receive monophonic or black-and-white signals generated by old transmitters.[citation needed]

Video gaming

[edit]

HTML

[edit]

HTML is designed to treat all tags in the same way (as inert, unstyled inline elements) unless their appearance or behavior is overridden; either by the browser's default settings, or by scripts or styles included in the page.[14] This makes most new features degrade gracefully in older browsers. One case where this did not work as intended was script and style blocks, whose contents are meant to be interpreted by the browser instead of being part of the page. Such cases were dealt with by enclosing the contents within comment blocks.[15] More generally, HTML's forward compatibility follows a "must ignore" design: early HTML specifications required that unrecognized start and end tags be mapped to nothing during tokenization, which is what allowed later elements such as <img> to be introduced without breaking existing browsers.[3]

As there is no mandatory upgrade of computers or web browsers, many web developers use a graceful degradation or progressive enhancement approach, attempting to make newly created websites that are compatible with older computers and web browsers, usable when JavaScript is disabled or on a slower connection, while still taking advantage of faster hardware and better JavaScript support in more modern web browsers, when available.[16]

Optical media

[edit]

Each of the three most common 12 cm optical media formats (CD, DVD, and Blu-ray) was first released in read-only form years before writable forms were available. Within each format, there is both forward and backward compatibility, in that most older read-only drives and players can read (but not write) writable media in the same format, while read/write drives can read (but not write) old read-only media. There is no forward compatibility between formats; a CD player, for instance, can't read a DVD (a newer format), not even the audio tracks. There may be backward compatibility for better marketability (such as a DVD player playing an audio CD), but it is not intrinsic to the standards.[17]

Relation to the robustness principle

[edit]

Forward-compatible design is closely related to the robustness principle articulated by Jon Postel in RFC 761 (January 1980): "be conservative in what you do, be liberal in what you accept from others".[18] The "liberal in what you accept" half of the principle describes the stance that a forward-compatible system takes toward unrecognized input; the "must ignore unknowns" rule can be read as a specific implementation of it.

Formally defining forward compatibility has nonetheless proven difficult. Members of the W3C Technical Architecture Group treated the definition of forward and backward compatibility as an open problem in 2007, in part because the concept describes a relationship to future versions of a language that do not yet exist.[19]

Not upwardly compatible

[edit]

Some products are not designed to be forward compatible, which has been referred to as NUC (not upwardly compatible). In some cases this might be intentional by the designers as a form of vendor lock-in or software regression.

For example, a cubicle producer considers changing their cubicle design. One designer promotes changing the footprint from 4-foot (1.22 m) square to 1.2-meter square. Immediately, the sales manager calls "NUC" and the problem is understood: if the footprint changes and existing customers are considering buying more from the producer, they will have to fit a different sized unit in an office designed for the 4-foot square cubicle.

Planned obsolescence is a type of upward compatibility, but rather than adopting a policy of backwards compatibility, companies adopt a commercial policy of backwards incompatibility so that newer apps require newer devices.

See also

[edit]

References

[edit]
  1. ^ W3C Technical Architecture Group. "Extending and Versioning Languages: Terminology". W3C. Retrieved 2026-04-18.{{cite web}}: CS1 maint: numeric names: authors list (link)
  2. ^ a b Tulach, Jaroslav (2008). Practical API Design: Confessions of a Java Framework Architect. Apress. p. 233. ISBN 978-1-4302-0973-7.
  3. ^ a b c d W3C Technical Architecture Group. "Extending and Versioning Languages: Compatibility Strategies". W3C. Retrieved 2026-04-18.{{cite web}}: CS1 maint: numeric names: authors list (link)
  4. ^ Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing. IETF. June 2014. doi:10.17487/RFC7230. RFC 7230.
  5. ^ Game Boy - Compatibility Chart. Nintendo of America. Retrieved 3 October 2017.
  6. ^ "Will the ps2 controller work on a ps1?". forum.digitpress.com. Retrieved 2017-12-27.
  7. ^ Newhouse, Alex (2014-07-01). "PlayStation 4 Controller Now Works Wirelessly With PlayStation 3". GameSpot. Retrieved 2017-12-27.
  8. ^ Santa Maria, Alex (2 November 2020). "PS5 DualSense Controller Works Perfectly On PS3 (But Not PS4)". ScreenRant. Retrieved 1 July 2021.
  9. ^ Williams, Demi (2 November 2020). "PS5 DualSense controller works on PS3". gamesradar.
  10. ^ "Can you use an Xbox Series X controller on Xbox One? Why, yes". Windows Central. 18 March 2021. Retrieved 24 March 2021.
  11. ^ "a deep dive of V.smile extended universe". youtube. Retrieved 23 October 2024.
  12. ^ "V.Smile emulators". Emulation General wiki. Retrieved 23 October 2024.
  13. ^ "Games Enhanced for Nintendo Switch 2 - Nintendo US". www.nintendo.com. Retrieved 2025-10-23.
  14. ^ Really undoing html.css by Eric A. Meyer.
  15. ^ HTML <!--...--> Tag at w3schools.com: 'You can also use the comment tag to "hide" scripts from browsers without support for scripts [...]'.
  16. ^ "Graceful degradation versus progressive enhancement".
  17. ^ "Can Blu-ray Disc products play DVD and CD?". Archived from the original on February 18, 2009. Retrieved January 25, 2009.
  18. ^ Jon Postel (January 1980). DoD Standard Transmission Control Protocol. IETF. doi:10.17487/RFC0761. RFC 761.
  19. ^ Marc de Graauw (12 September 2007). "RE: definition of forward compatible/backward compatible still an open problem [XMLVersioning-41 ISSUE-41]". W3C www-tag mailing list. Retrieved 2026-04-18.
[edit]

Source: Wikipedia. Article content is retrieved live through the MediaWiki API.

No preview image
Wikipedia

Forward compatibility

Forward compatibility or upward compatibility is a design characteristic that allows a system to accept input intended for a later version of itself. The concept can be applied to entire systems, electrical interfaces, telecommunication signals, data communication protocols, file formats, and programming languages. A standard supports forward compatibility if a product that complies with earlier versions can "gracefully" process input designed for later versions of the standard, ignoring new parts which it does not understand. The W3C's Technical Architecture Group (TAG) defines the concept more formally: "a change in the definition of a language is forward compatible if consumers of the original language can correctly process text written for the evolved version of the language". The objective for forward-compatible technology is for old devices to recognise when data has been generated for new devices. Forward compatibility for the older system usually means backward compatibility for the new system, i.e. the ability to process data from the old system; the new system usually has full compatibility with the older one, by being able to both process and generate data in the format of the older system. Forward compatibility is not the same as extensibility. A forward compatible design can process at least some of the data from a future version of itself. An extensible design makes upgrading easy. An example of both design ideas can be found in web browsers. At any point in time, a current browser is forward-compatible if it gracefully accepts a newer version of HTML, whereas how easily the browser code can be upgraded to process the newer HTML determines how extensible it is.

MORE →
Wikipedia

Backward compatibility

In telecommunications and computing, backward compatibility (or backwards compatibility) is a property of an operating system, software, real-world product, or technology that allows for interoperability with an older legacy system, or with input designed for such a system. Modifying a system in a way that does not allow backward compatibility is sometimes called "breaking" backward compatibility. Such breaking usually incurs various types of costs, such as switching cost. A complementary concept is forward compatibility; a design that is forward-compatible usually has a roadmap for compatibility with future standards and products.

MORE →
No preview image
Wikipedia

List of Xbox 360 games

This is a list of Xbox 360 games that were released via retail disc, digital download or as part of the Xbox Live Arcade (XBLA) program. There are 2155 games across both lists. Games with the Xbox One forward compatibility identifier are also compatible with Xbox Series X and Series S (though only digital games in the case of the Series S).

MORE →
No preview image
Wikipedia

Flag day (computing)

A flag day (or flag day cutover) in computing and system administration is a planned change that requires many systems to be upgraded or converted in a coordinated way because the old and new versions are not mutually compatible. Such changes are typically costly to carry out and, if problems arise, difficult to roll back. Flag days can occur when constraints on backward compatibility or forward compatibility prevent a gradual migration, requiring updates to be performed nearly simultaneously for the overall system to function. In contrast, phased deployments aim to preserve service continuity by allowing old and new versions to coexist during the transition.

MORE →
TOPIC OF THE DAY

Greenwood / Black Wall Street

Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.

MORE →
TRIVIA QUESTION OF THE DAY

Which heavyweight champion was known as the “Brown Bomber”?

Joe Louis.