MétaCan
Menu
Back to cohort
Record W2036461393 · doi:10.1145/2060329.2060356

Domain-specific engineering of domain-specific languages

2010· article· en· W2036461393 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 institutionsMcGill University
Fundersnot available
KeywordsComputer scienceDigital subscriber lineDomain-specific languageProgramming languageUnified Modeling LanguageModel-driven architectureRotation formalisms in three dimensionsDomain (mathematical analysis)Semantics (computer science)Software engineeringMetamodelingDomain analysisCode generationContext (archaeology)Software developmentKey (lock)Software

Abstract

fetched live from OpenAlex

Domain-specific modelling (DSM) enables experts of arbitrary domains to perform modelling tasks using familiar constructs. This contrasts with common code-centric development approaches where programmers deal with object-oriented approximations of higher level concepts. Domain-specific concepts and their relationships are captured by domain-specific languages (DSLs). Unfortunately, it is common practice for DSLs to be specified within the object-oriented mindsets of classes and associations. This approach not only contradicts the model-driven engineering (MDE) philosophy of development using domain-specific concepts -- in this case, the domain and concepts of DSLs --, it is also faced with the same obstacle as past UML-to-code generation efforts; namely, that UML models are too generic to enable complete program synthesis. In the context of DSL engineering, this obstacle translates to the necessity for DSL designers to explicitly define DSL semantics manually (e.g., via coded generators and/or model transformations). In this work, we propose a novel approach to DSL design where low level modelling formalisms are seamlessly woven together to form new DSLs whose semantics are fully automatically generated.

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: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.935
Threshold uncertainty score0.865

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.007
GPT teacher head0.211
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