Changed upward to backward compatibility

content/news/2021/oslc-core-os.md

@@ -12,7 +12,7 @@ banner = "img/news-default.jpg"
 
 We are happy to announce a publication of OSLC 3.0, the next generation of the core OSLC specification, as the OASIS Standard. The specification in full can be viewed freely [online](https://docs.oasis-open-projects.org/oslc-op/core/v3.0/os/oslc-core.html) and this post will serve as a guide for existing OSLC 2.0 users to learn what's new and navigate around the changes in the specifications.
 
-The OSLC Core 2.0 evolution from 1.0 strengthened its definition of the use of RESTful HTTP web services and adopted an existing standard-based approach to representing a data model that was flexible and had multiple representation formats, namely RDF. A primary goal of OSLC Core 3.0 was upwards compatibility with OSLC 2.0, preserving the investment in existing implementations. Most OSLC Core 3.0 changes are optional and OSLC 2.0 servers will not be mandated to adopt them to be compliant with 3.0. In most cases, existing OSLC 2.0 clients should be able to consume OSLC 3.0 servers with no changes. This should result in a less disruptive change from 2.0 to 3.0. This document provides a summary of the changes in OSLC Core 3.0 with respect to OSLC Core 2.0.
+The OSLC Core 2.0 evolution from 1.0 strengthened its definition of the use of RESTful HTTP web services and adopted an existing standard-based approach to representing a data model that was flexible and had multiple representation formats, namely RDF. A primary goal of OSLC Core 3.0 was backward compatibility with OSLC 2.0, preserving the investment in existing implementations. Most OSLC Core 3.0 changes are optional and OSLC 2.0 servers will not be mandated to adopt them to be compliant with 3.0. In most cases, existing OSLC 2.0 clients should be able to consume OSLC 3.0 servers with no changes. This should result in a less disruptive change from 2.0 to 3.0. This document provides a summary of the changes in OSLC Core 3.0 with respect to OSLC Core 2.0.
 
 From the standardization point of view, there have been two major changes in OSLC 3.0 that further the openness of OSLC and strengthen its integration value. First, the specification development was moved to OASIS, a vendor-neutral standardization body with a proven track record of assisting in the publication of standards that are widely adopted and further standardized by international bodies like ISO (e.g. [MQTT](https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html), [ODF (ISO/IEC 26300-1:2015)](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office)). Throughout the development of the specifications, our member section at OASIS featured as many as [16 members](https://web.archive.org/web/20170814105435/http://www.oasis-oslc.org:80/members) before executing a transition to an Open Project that has drastically lowered the bar to [entry](https://github.com/oslc-op/oslc-admin/blob/master/CONTRIBUTING.md). Second, the OSLC 3.0 specification is now aligned with the [Linked Data Platform 1.0](https://www.w3.org/TR/ldp/), a W3C Recommendation, that was adopted by projects such as [Solid](https://solidproject.org/), focused on decentralizing data storage and spearheaded by Sir Tim Berners-Lee, the founding father of the Web.