MétaCan
Menu
Back to cohort
Record W1510356539

A service-oriented monitoring registry

2003· article· en· W1510356539 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueConference of the Centre for Advanced Studies on Collaborative Research · 2003
Typearticle
Languageen
FieldComputer Science
TopicService-Oriented Architecture and Web Services
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsWeb serviceComputer scienceWS-PolicyService providerWorld Wide WebService (business)Web modelingWS-AddressingWeb developmentWS-I Basic ProfileService designWeb application securityBusiness
DOInot available

Abstract

fetched live from OpenAlex

Web services are software modules that expose their functionality over the Internet via well-defined interfaces. Although Web services are promising technologies in that they facilitate application-to-application communication over the Internet, they still rely on traditional distributed computing communication models such as the remote procedure call, in which a Web service requestor needs to have complete knowledge of a Web service provider interface. If a Web service requestor did not use the latest version of a Web service provider interface to generate a proxy service, then static binding to the Web service provider's services fails. In this paper, we provide functional requirements for a Service-Oriented Monitoring Registry (SOMR) that provides notification to service requestors when a version of an interface changes or a service becomes disabled. In order to present a more complete picture of SOMR we include four architectural views covering (i) the over-all system, (ii) its four tiers and their interconnection, (iii) details of the service tier and (iv) its deployment onto executable environments. SOMR provides public Web service registries that can be used by Web service providers, developers, and consumers to register their profiles so that whenever any change happens to Web service interfaces they are notified about these changes and can respond accordingly. In contrast with current static solutions, the proposed system provide a significant step toward achieving solutions that are consistent with the dynamic nature and evolution of Web services.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.872
Threshold uncertainty score0.755

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.003
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.092
GPT teacher head0.386
Teacher spread0.294 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it