MétaCan
Menu
Back to cohort
Record W2502638135 · doi:10.1016/j.procs.2016.08.023

Using Provenance and CoAP to track Requests/Responses in IoT

2016· article· en· W2502638135 on OpenAlexaff
Emmanuel Kaku, Richard K. Lomotey, Ralph Deters

Bibliographic record

VenueProcedia Computer Science · 2016
Typearticle
Languageen
FieldDecision Sciences
TopicScientific Computing and Data Management
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsComputer scienceTracingTransparency (behavior)Key (lock)InferenceFocus (optics)ProvenanceThe InternetInternet of ThingsReliability (semiconductor)Component (thermodynamics)World Wide WebComputer securityData scienceArtificial intelligenceOperating system

Abstract

fetched live from OpenAlex

Until recently, not much attention has been drawn to the need to provide documentary evidence for ensuring reliability, transparency and, most importantly, tracing the source of requests/responses in the Internet of Things. The knowledge of provenance is considered as a key component in establishing the above-mentioned issues. Most research, to a large extent, focus on requesting data, which is based on user inference and decision making, by utilising provenance information. However, little or nothing has been done regarding requests and responses and, most importantly, from the machine perspective. Consequently, this paper proposes a light-weight prototype system for tracing the source of requests/responses using provenance information over CoAP in the Internet of Things. We also provide performance evaluation of the prototypic system using metrics such as response time (ms) and throughput (KB/s). Finally, findings from our experiment are presented and discussed.

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 imitation

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

metaresearch head score (Codex)0.006
metaresearch head score (Gemma)0.018
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.011
Threshold uncertainty score0.034

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.018
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0030.003
Science and technology studies0.0020.001
Scholarly communication0.0030.005
Open science0.0010.003
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0010.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.218
GPT teacher head0.422
Teacher spread0.204 · 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 source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
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

Citations9
Published2016
Admission routes1
Has abstractyes

Explore more

Same venueProcedia Computer ScienceSame topicScientific Computing and Data ManagementFrench-language works237,207