The 3 rd Workshop on Automatic Service Composition
Bibliographic record
Abstract
Service-oriented architecture (SOA) is an architectural style for building software applications that uses services available in a network such as the web. An architectural style defines a vocabulary comprised of component and connector types as well as constraints on how they can be combined. SOA promotes loose coupling between software components so that they are able to be reused. Applications in SOA are built based on services, which means it is build on an implementation of well-defined business functionality. Such services can then be consumed by clients in different applications or business processes. SOA solutions have been created to satisfy business goals such as integration with legacy systems, reduced costs, and the ability to provide innovative services to customers. Web services are able to be used to realize SOA. Web services are defined as self-contained, self-describing, modular applications that can be published, located, and invoked across the Web. Web services range from comprehensive services such as storage management and customer relationship management to more specific services such as travel reservation, book purchasing, weather forecasts, financial data summaries, and news gathering. These fine grained services can be combined to solve a specific task such as locating cheaper airline tickes from a number of service providers. In short, services are everywhere in today's Internet.
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.008 | 0.013 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.004 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.002 | 0.003 |
| Scholarly communication | 0.008 | 0.009 |
| Open science | 0.004 | 0.004 |
| Research integrity | 0.004 | 0.006 |
| Insufficient payload (model declined to judge) | 0.049 | 0.020 |
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".