A formal specification strategy for electronic commerce
Bibliographic record
Abstract
Most current Web applications perform operations that are basically read-only (retrieval of data/documents), so conflicts between transactions do not arise. However as Web applications increasingly become more sophisticated, permitting both concurrent data retrieval and update operations to remote databases, the potentials for conflicts between transactions becomes very high. Therefore, we must ensure correct transaction operation and the correct synchronization of concurrent transactions to avoid deadlock and ensure correctness. The paper presents a formal specification methodology based on the concept of concurrent execution that provides automatic communication and synchronization mechanisms between concurrent processes. The paper explores the issues of correctness, reliability, and recovery of data distributed across the enterprise, describes techniques for guaranteeing and enhancing correctness and procedures for recovering transactions and data in case of any transaction failures to guarantee a high degree of system dependability. Formal methods simplify the writing of concurrent programs by taking most of the burden of synchronization away from the programmer. Further specifying transaction systems formally, enhances application quality and reliability by verifying the functionalities of applications and the correctness of data.
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.004 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.002 | 0.005 |
| Scholarly communication | 0.005 | 0.008 |
| Open science | 0.003 | 0.003 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.013 | 0.005 |
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".