MétaCan
Menu
Back to cohort
Record W2150673328 · doi:10.1109/ccece.2005.1557017

Distributed ontology management system

2006· article· en· W2150673328 on OpenAlexaff
Ruth Harrison, Christine W. Chan

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicService-Oriented Architecture and Web Services
Canadian institutionsUniversity of Regina
Fundersnot available
KeywordsComputer scienceOntologyDatabaseRelational databaseWorld Wide Web

Abstract

fetched live from OpenAlex

This paper presents development of the distributed ontology management system (DOMS). The objective of DOMS was to provide a framework for handling the sharing, storage, versioning, and security of ontologies in a repository. The ontologies are represented by a generic object-oriented class hierarchy, which can be translated into an XML (extensible markup language) representation. To share ontologies, DOMS uses a distributed client-server architecture using TCP (transmission control protocol). A relational database is used for storing the ontologies in DOMS. A mapping from relational to the generic representation, which is object-oriented, can transfer data in and out of the database. Ontology versioning is performed by using the ontology's versioning information that is modeled in the database. To enhance system security, communication between the client and server is encrypted with SSL (secure socket layer). Additionally, DOMS uses an individual-based model to control access to the ontologies. An ontology editor has also been integrated with DOMS. This paper shows that DOMS provides some improvements upon existing ontology management systems, and discusses ways for further extension of the system

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 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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.955
Threshold uncertainty score0.340

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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
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.003
GPT teacher head0.185
Teacher spread0.182 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreEmpirical

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

Quick stats

Citations15
Published2006
Admission routes1
Has abstractyes

Explore more

Same topicService-Oriented Architecture and Web ServicesFrench-language works237,207