Towards change and verification support in collaborative business processes
Bibliographic record
Abstract
The automation of business processes raises several challenges for enterprises. One of those challenges relates to the maintenance and verification of business processes, more precisely how to facilitate changes within existing business processes even at the run-time. Furthermore, changing a collaborative business process can have an impact on the contract specified between the involved parties. Thus, a business process may need to adapt and meet reliably the new contract. In this paper, we discuss an approach to support change and verification for such collaborative processes. This approach consists of (1) a protocol, called Change Protocol for Collaboration (CPC), for managing the changes that can have an incidence on the contract; (2) an algorithm for supporting migration of running business process instances to their new schemas; and (3) a verification framework for supporting of the accuracy of changes before their adoption.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.028 | 0.072 |
| Meta-epidemiology (narrow) | 0.001 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.002 | 0.006 |
| Scholarly communication | 0.008 | 0.017 |
| Open science | 0.005 | 0.009 |
| Research integrity | 0.006 | 0.007 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".