Service offerings for XML Web services and their management applications
Bibliographic record
Abstract
I show why the specification, monitoring, and dynamic (run-time) manipulation of classes of service are useful for XML (Extensible Markup Language) Web Services and how to achieve them. Classes of service are a mechanism for differentiation of service and quality of service (QoS) that incurs less overhead than custom-made Service Level Agreements (SLAs), user profiles, and other alternatives. A service offering is a formal description of one class of service of a Web Service. One Web Service can provide multiple service offerings. For formal specification of service offerings, I developed the Web Service Offerings Language (WSOL), compatible with the standard Web Services Description Language (WSDL). A WSOL service offering can contain descriptions of various categories of constraints, management statements, and reusability constructs. Dynamic relationships between service offerings are specified outside WSOL service offerings, in a special format. Describing a Web Service in WSOL enables monitoring, metering, and management of Web Services and their compositions. The main distinctive characteristics of WSOL, compared to related works, are its expressive capabilities, features with relatively low run-time overhead, and support for management applications. To achieve dynamic adaptation of a Web Service composition without breaking it, I developed algorithms and protocols for switching (consumer- and provider-initiated), deactivation, reactivation, deletion, and creation of service offerings. I analytically and experimentally compared these manipulation mechanisms with re-composition of Web Services and re-negotiation of SLAs and concluded that the proposed mechanisms are, in principle, simpler, faster, and with lower run-time overhead. The Web Service Offerings Infrastructure (WSOI) measures and calculates used QoS metrics, evaluates WSOL constraints, and performs accounting of executed operations and evaluated constraints. These monitoring activities can be performed by providers, consumers, or management third parties (SOAP intermediaries or probes). One of the main differences between WSOI and the other Web Service management, infrastructures are the modules, data structures, and specialized management operations implementing the mechanisms for manipulation of service offerings. The WSOI prototype extends the open-source Apache Axis SOAP engine. Its additional overhead is relatively low. The results of this research can be used in future Web Service standards and products.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.002 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".