Using contract and ontology for privacy protection in Service-Oriented Architecture
Bibliographic record
Abstract
Privacy protection in Service-Oriented Architecture (SOA) is an open problem. As privacy protection can be considered as a contractual issue, the solution for the problem of privacy protection in SOA requires the use of electronic contracts. This is important, as the service consumer's confidence of the protection of their privacy is a factor for the success of electronic services (e-services). This confidence may increase if the service consumer and provider can establish a contract, which states how the provider deals with information collected from the consumer. The service consumer can sign the contract if the privacy protection practices described in it meet what the consumer defines as appropriate practices. The goal of this paper is to use contract and ontology for privacy protection in SOA. Privacy contracts follow an approach based on feature modeling. In addition, they use a base ontology that provides a common privacy vocabulary.
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.019 | 0.019 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.004 | 0.012 |
| Scholarly communication | 0.008 | 0.019 |
| Open science | 0.002 | 0.006 |
| Research integrity | 0.005 | 0.005 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
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".