English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

To enhance the compatibility in the version control of Java Third-partyLibraries (TPLs), Maven adopts Semantic Versioning (SemVer) to standardize theunderlying meaning of versions, but users could still confront abnormalexecution and crash after upgrades even if compilation and linkage succeed. Itis caused by semantic breaking (SemB) issues, such that APIs directly used byusers have identical signatures but inconsistent semantics across upgrades. Tostrengthen compliance with SemVer rules, developers and users should be alertedof such issues. Unfortunately, it is challenging to detect them statically,because semantic changes in the internal methods of APIs are difficult tocapture. Dynamic testing can confirmingly uncover some, but it is limited byinadequate coverage.  To detect SemB issues over compatible upgrades (Patch and Minor) by SemVerrules, we conduct an empirical study on 180 SemB issues to understand the rootcauses, inspired by which, we propose Sembid (Semantic Breaking Issue Detector)to statically detect such issues of TPLs for developers and users. Since APIsare directly used by users, Sembid detects and reports SemB issues based onAPIs. For a pair of APIs, Sembid walks through the call chains originating fromthe API to locate breaking changes by measuring semantic diff. Then, Sembidchecks if the breaking changes can affect API's output along call chains. Theevaluation showed Sembid achieved 90.26% recall and 81.29% precision andoutperformed other API checkers on SemB API detection. We also revealed Sembiddetected over 3 times more SemB APIs with better coverage than unit tests, thecommonly used solution. Furthermore, we carried out an empirical study on1,629,589 APIs from 546 version pairs of top Java libraries and found therewere 2-4 times more SemB APIs than those with signature-based issues.

Has My Release Disobeyed Semantic Versioning? Static Detection Based on Semantic Differencing