Prepare a draft of the OSLC Core changes summary

[berezovskyi]

No description provided.

[axelreichwein]

when you say: "primary goal of OSLC Core 3.0 was upwards compatibility with OSLC 2.0" -> you probably mean backwards compatibility with OSLC 2.0?

[berezovskyi]

@axelreichwein I agree this sounds wrong. As per https://en.wikipedia.org/wiki/Forward_compatibility, we don't expect OSLC 2 servers to accept LDP-rich input crafted for OSLC 3 servers.

@jamsden could you please check this and edit this PR as necessary? Web edits can be done via https://github.com/oslc-op/website/edit/b-oslc-core-os/content/news/2021/oslc-core-os.md?pr=%2Foslc-op%2Fwebsite%2Fpull%2F297

Thanks to both of you!

[jamsden]

Done

[berezovskyi]

@jamsden @axelreichwein do we still want to publish this as a blog post? I would like to publish it before the OSLCfest. Core PN will take us 2-3 weeks to get out.

[berezovskyi]

@jamsden strange we never published this. Should we go ahead?

[berezovskyi]

I now recall we were waiting for the PN publication.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Jim Amsden seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}