MétaCan
Menu
Back to cohort
Record W2148428941 · doi:10.1109/edoc.2007.18

Business Process Integration by Using General Rule Markup Language

2007· article· en· W2148428941 on OpenAlexaff
Milan R. Мilanović, Nima Kaviani, Dragan Gašević, Adrian Giurca, Gerd Wagner, Vladan Devedžić, and Marek Hatala

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBusiness Process Modeling and Analysis
Canadian institutionsAthabasca UniversitySimon Fraser University
Fundersnot available
KeywordsBusiness ruleRuleMLComputer scienceMarkup languageArtifact-centric business process modelBusiness process modelingSemantics of Business Vocabulary and Business RulesBusiness domainBusiness processProcess managementBusiness Process Model and NotationBusiness process discoveryLeverage (statistics)Software engineeringXMLWorld Wide WebBusinessArtificial intelligenceXHTMLWork in processMarketing

Abstract

fetched live from OpenAlex

A business process usually includes multiple busi- ness partners that use systems with their business log- ics represented in different rule (or policy) languages. The integration of business processes is a major goal followed by business enterprises and involves the in- terchange of business rules and policies between part- ners. However, the variety of business rules employed by the partners presents a significant burden to the integration of collaborating business systems. In this paper, we propose a solution that enables translating rules and policies defined in different rule languages into a single general rule language (REWERSE I1 Rule Markup Language - R2ML) and processing them in a uniform manner. This provides a unified view of different partners' business rules in an integration process, while permitting the partners to continue to leverage their own business rules without changing their technologies. We show how the concepts of the KAoS policy language can be transformed to R2ML and then from R2ML to the other rule (or policy) lan- guages.

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.006
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.006
Threshold uncertainty score0.032

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.006
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.003
Bibliometrics0.0020.002
Science and technology studies0.0010.002
Scholarly communication0.0050.007
Open science0.0030.003
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0020.002

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.013
GPT teacher head0.260
Teacher spread0.246 · 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 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

Citations7
Published2007
Admission routes1
Has abstractyes

Explore more

Same topicBusiness Process Modeling and AnalysisFrench-language works237,207