MétaCan
Menu
Back to cohort
Record W2754828358 · doi:10.1109/ieee.iciot.2017.35

SmartHomeML: Towards a Domain-Specific Modeling Language for Creating Smart Home Applications

2017· article· en· W2754828358 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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsConcordia University
Fundersnot available
KeywordsHome automationComputer scienceDomain (mathematical analysis)Service providerEmbedded systemWindow (computing)Domain-specific languageService (business)Human–computer interactionSoftware engineeringWorld Wide WebTelecommunications

Abstract

fetched live from OpenAlex

There is an increasing demand for smart home connectivity from controlling the home temperature, to switching light bulbs, controlling the window shades and pet feeders. Smart home control systems such as Amazon Alexa and Google Home provide user interfaces to coordinate the operation of several home appliances. While this facilitate integrating the operations of several appliances, system integrators still need to specify and define the integration and communication logic. This logic depends on both the appliance and the control system providers. This paper introduces SmartHomeML, a domain specific modelling language for smart home applications, that allows users to define new skills (functionalities). SmartHomeML consists of a model designer that supports modelling smart home applications and a model generator that uses template-based transformation to automatically generate smart home device adapters and connectors that conform to the specification of a selected target home control system. We show through an example how to use SmartHomeML to model a smart home service independently from the target smart home provider and then generate Amazon Alexa Skill Adapters and SmartThings SmartApps automatically.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.845
Threshold uncertainty score0.681

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.0010.000
Scholarly communication0.0010.001
Open science0.0020.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.028
GPT teacher head0.283
Teacher spread0.255 · 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