MétaCan
Menu
Back to cohort
Record W2074683931 · doi:10.1109/35.815459

JAIN protocol APIs

2000· article· en· W2074683931 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

VenueIEEE Communications Magazine · 2000
Typearticle
Languageen
FieldComputer Science
TopicMobile Agent-Based Network Management
Canadian institutionsTrillium Therapeutics (Canada)
Fundersnot available
KeywordsComputer scienceJavaProtocol (science)Computer networkInternet ProtocolNext-generation networkImplementationThe InternetFocus (optics)Operating systemSoftware engineering

Abstract

fetched live from OpenAlex

JAIN envisions the creation of a number of Java APIs that abstract the details of networks and protocol implementations, and allow for the development of portable applications. The JAIN Protocol Experts Group (PEG) will focus on developing Java APIs for protocols used in telephony, INs, wireless networks, and the Internet. The PEG is organized into an SS7 subgroup and an IP subgroup. The article provides an introduction to PEG. It next describes the JAIN SS7 APIs. It then describes the JAIN IP APIs. The article also explains how JAIN SS7 and IP APIs can be leveraged for the converged SS7-IP networks of the future and describes the JAIN PEG roadmap.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.718
Threshold uncertainty score0.997

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0050.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.004

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.032
GPT teacher head0.296
Teacher spread0.264 · 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