[0.6.0] - 2025-07-06

Security

This release does not contain security updates.

Added

• ⚡️ TextOutputFormatter/TextInputFormatter implementations for OSLC RDF, enabling the use of OSLC4Net in ASP.NET Core API servers
  • 👉 see sample server under OSLC4Net_SDK/Examples/OSLC4NetExamples.Server.NetCoreApi
• ⚡️ JSON-LD 1.1 support
• Initial support for RDFS inference during deserialization was added.
• 👉 Docs are now published to https://oslc4net.github.io/

Changed

• ❗️ Major changes to exceptions from Core and Client packages.
  • Getters were replaced with read-only properties
  • I18n resource strings were removed along with the corresponding
    constructors.
  • Error codes OSLC001..OSLC014 from Core were renamed to
    OSLC1001..OSLC1014, while
    codes OSLCC001..OSLCC004 from Client were renamed into
    OSLC2001..OSLC2014. All OSLC4Net error codes now have 4 digits for
    consistency.
• ❗️ DotNetRdfHelper is no longer static

Deprecated

• 👉 OSLC4Net.Client.Oslc.Resources.ChangeRequest.GetRdfTypes and all similar
  methods. Use OSLC4Net.Core.Model.IExtendedResource.GetTypes instead or,
  better yet, OSLC4Net.Core.Model.AbstractResourceRecord.Types.

Removed

• ❗️ Legacy OSLC JSON support was removed to reduce maintenance overhead now that
  the JSON-LD support is added.
• I18n resource strings were removed along with the corresponding
  constructors on exceptions. Also, MessageExtractor helpers were removed.
• log4net dependency - all logging is now done via standard ILogger
  abstraction.
• ServiceProviderRegistryURIs - oslc4net will no longer try to guess/compute the
  SP catalog URI.

Fixed

• OSLC4Net.Core.Model.IExtendedResource.GetTypes is now annotated properly and
  should be populated correctly on deserialization.

[0.6.0-preview.1] - 2025-05-25

Security

This release does not contain security updates.

Added

• ⚡️ JSON-LD 1.1 support
• Initial support for RDFS inference during deserialization was added.
• Docs are now published to https://oslc4net.github.io/

Changed

This release does not contain other significant changes.

Deprecated

• 👉 OSLC4Net.Client.Oslc.Resources.ChangeRequest.GetRdfTypes and all similar
  methods. Use OSLC4Net.Core.Model.IExtendedResource.GetTypes instead or,
  better yet, OSLC4Net.Core.Model.AbstractResourceRecord.Types.

Removed

• ❗️Legacy OSLC JSON support was removed to reduce maintenance overhead now that
  the JSON-LD support is added.

Fixed

• OSLC4Net.Core.Model.IExtendedResource.GetTypes is now annotated properly and
  should be populated correctly on deserialization.

[0.5.0] - 2025-04-13

Security

This release does not contain security updates.

Added

• ⚡️ CI integration tests against OSLC RefImpl CM/RM based on NET Aspire
• ⚡️ Ability to define OSLC resource POCOs using C# properties instead of
  Java-style getters/setters.
• ⚡️ Support for the OSLC Requirements Management 2.1 domain with property-based code.
• Added full vocabulary definitions for FOAF, DC Terms, DC Elements, LDP, PROV-O, QUDT, SKOS.
• Redirect loop protection for OslcClient (max 20 redirects as in
  Firefox/Blink/WebKit)
• Follow redirects on more responses statuses (was: 301, became: 301, 302, 307,
  308, and in case of GET requests, 303 too)
• ❗️ OslcResponse can now expose multiple response resources, the Graph and,
  in case of error, the oslc:Error resource.

Changed

• dotNetRDF dependency was updated to v3.3.1
• ❗️ OslcClient was updated to support async operations consistently

Deprecated

• Most non-async methods in client classes.
• Further OSLC JSON deprecations. Clients should rely on RDF instead (RDF/XML,
  Turtle)
• Old OSLC Requirements Management classes that were hand-rolled and used Java code style.

Removed

• ❗️ Multiple non-async methods in OslcClient
• ❗️ A property exposing OslcRestClient in ServiceProviderRegistryClient

Fixed

• Minor bug fixes to pass acceptance tests against OSLC RefImpl Change
  Management server.

[0.5.0-preview.1] - 2025-04-13

Security

This release does not contain security updates.

Added

• ⚡️ CI integration tests against OSLC RefImpl based on NET Aspire
• Redirect loop protection for OslcClient (max 20 redirects as in Firefox/Blink/WebKit)
• Follow redirects on more responses statuses (was: 301, became: 301, 302, 307, 308, and in case of GET requests, 303 too)
• ❗️ OslcResponse can now expose multiple response resources, the Graph and, in case of error, the oslc:Error resource.

Changed

• dotNetRDF dependency was updated to v3.3.1
• ❗️ OslcClient was updated to consistently support async operations

Deprecated

• Most non-async methods in client classes.
• Further OSLC JSON deprecations. Clients should rely on RDF instead (RDF/XML, Turtle)

Removed

• ❗️ Multiple non-async methods in OslcClient
• ❗️ A property exposing OslcRestClient in ServiceProviderRegistryClient

Fixed

• Minor bug fixes to pass acceptance tests against OSLC RefImpl Change Management server.

[0.4.7-preview.4] - 2024-12-07

Notable changes:

• deterministic paths and builds

[0.4.7-preview.3] - 2024-12-07

Notable changes:

• Ensure .snupkg symbols are published as well

[0.4.7-preview.2] - 2024-12-06

Notable changes:

• include debug symbols in the build

[0.4.7-preview.1] - 2024-12-06

Notable changes:

• harden the build/release following the "Ultralitics-gate" using hints from zizmor
• update deps

[0.4.6] - 2024-11-15

Security

This release does not contain security updates.

Added

This release does not contain new features.

Changed

• Dependency updates in connection with .NET 9 release.

Deprecated

This release does not introduce deprecations.

Removed

This release does not remove any features.

Fixed

• Requirement.SetDecomposes() cleared affectedBy by mistake.

[0.4.5] - 2024-10-19

Security

• 🔒️ Transitive dependency System.Net.Http was set to version 4.3.4 to avoid failing the build when NU1903 is treated as error.
• 🔒️ Transitive dependency System.Text.RegularExpressions was set to version 4.3.1 to avoid failing the build when NU1903 is treated as error.

Added

This release does not contain new features.

Changed

• Significant build changes to manage package versions centrally.
• NuGet/assembly versions are now set based on the git tag name.
• 👉 "snapshot" builds how have the version similar to 999.9.9-ts.202410192025, where 202410192025 is a timestamp; please note that such snapshot builds are only available via Github Packages.

Deprecated

This release does not introduce deprecations.

Removed

• Dependencies on "bridge" packages added during the migration from .NET Framework to .NET 6:
  • System.Configuration.ConfigurationManager
  • System.Data.DataSetExtensions
  • Microsoft.CSharp

Fixed

• Example and test projects had <IsPackable>false</IsPackable> property set to prevent pushing their packages to NuGet.