• WordIndex

This is an index of all words occuring in page titles.

See also:

• TitleIndex -- a shorter index

• SiteNavigation -- other indexing schemes

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Z
Include system pages

• AbSynt

• Abstract Syntax
• AbstractModel

• Policy-Based Transaction Authorization and Access Control
• Rule-Based Combined Access to XML and RDF Data
• UCR/Access to Business Rules of Supply Chain Partners
• UCR/Collaborative Policy Development for Dynamic Spectrum Access

• Automated Trust Establishment for Accessing Medical Records

• Discussion of UC1 - Negotiating eBusiness Contracts Across Rule Platforms
• UCR/Negotiating eBusiness Contracts Across Rule Platforms

• PRdialect/Action

• Situation Assessment and Adaptation

• How to Add a Use Case

• AdminGroup

• UCR/Critical Factors Analysis/Widescale Adoption

• AdrianGiurca
• AdrianGiurca/FLD-Review

• Interchange of Business Rules between Business People in Different Organizations (Units) When Making Agreements
• Rule-based Service Level Agreements (SLA) and Web Services

• HassanAitKaci

• Alternative Extensible Design
• Core/Horn Rules Alternative
• UCR/Candidate Use Cases for 2nd Draft/PublicationAlternative

• UCR/Critical Factors Analysis
• UCR/Critical Factors Analysis/Consistency with W3C specifications
• UCR/Critical Factors Analysis/Exchange of Rules
• UCR/Critical Factors Analysis/Open Issues
• UCR/Critical Factors Analysis/Widescale Adoption

• Fuzzy Reasoning with Brain Anatomical Structures
• Labeling Brain Anatomical Structures in Digital Images

• Method For Collecting And Organising Design Constraints
• UCR/What is a Rule Interchange Format And Why Create One

• BillAndersen

• DarkoAnicic

• REWERSE's Proposal: A Versatile, Declarative Format with Annotations

• F2F2/Approaches to OWL Compatibility

• Rules for a Credit Approval Service

• Arch
• Arch/Data Sets
• Arch/Equilty
• Arch/Extensibility
• Arch/Extensibility Design Choices
• Arch/Extensibility2
• Arch/Extensibility3
• Arch/Introduction
• Arch/Naming Conventions
• Arch/RDF-Data
• Arch/RIF Components
• Arch/RIF Components/RIF Dialect Structure
• Arch/RIF Components/RIF Expression Components
• Arch/RIF Components/Rules and Rule Sets
• Arch/Semantics
• Arch/Syntax
• Arch/Test Cases
• Arch/Using RIF
• Arch/XML Syntax
• Arch/XML Syntax Issues 1
• Arch/XML Syntax Issues 2
• Arch/XML Syntax Issues/Constants
• Arch/XML Syntax Issues/Identifying Rulesets
• Arch/XML Syntax Issues/Positional Arguments
• Arch/XML Syntax Issues/Root Element
• Arch/naf example
• WebArch Vol 1

• Arch/XML Syntax Issues/Positional Arguments

• Rulesystem Arrangement Framework

• Rule Based Service Level Management and SLAs for Service Oriented Computing

• Situation Assessment and Adaptation

• A. Assumptions

• Meeting Attendance

• Credit Card Transaction Authorization
• Policy-Based Transaction Authorization and Access Control

• Automated Trust Establishment for Accessing Medical Records
• Automated Trust Establishment for eCommerce

• Automatically generated rules

• AxelPolleres

• Higher Order and Frame Based Syntax
• Policy-Based Transaction Authorization and Access Control
• RIFUCR - Use cases - Policy-Based
• Rule Based Service Level Management and SLAs for Service Oriented Computing
• Rule-Based Combined Access to XML and RDF Data
• Rule-Based Email Manipulation
• Rule-Based Intelligent Guiding
• Rule-Based Reactive Organizer
• UCR/BPEL Orchestration of Rule-Based Web Services

• UCR/Basic RIF Processing Model

• A.1 Basis: Positive Conditions
• A.1.1 Basis: Positive Conditions over Bipartitioned Constants

• BenjaminGrosof

• BijanParsia

• BillAndersen

• A Library of Biomedical ontologies

• A.1.1 Basis: Positive Conditions over Bipartitioned Constants

• A.7 Mapping Rule Bodies of Other Languages to RIF Condition Language

• HaroldBoley

• BottomUpClassification

• Fuzzy Reasoning with Brain Anatomical Structures
• Labeling Brain Anatomical Structures in Digital Images

• F2F2/RequirementsBrainstorming

• F2F1 Breakout Session on OWL and RDF Compatibility

• JosDeBruijn
• JosDeBruijn/MyDict

• FrançoisBry

• The RIF Core must be able to accept OWL KBs as data
• Ways of using OWL KBs as data

• WikiBugs

• A.3 Extension: Builtins in Conditions

• Business Rule
• Discussion of UC1 - Negotiating eBusiness Contracts Across Rule Platforms
• Interchange of Business Rules between Business People in Different Organizations (Units) When Making Agreements
• Interchange of Business Rules between People Who Run Organizations and Internally/Externally Supplied IT Systems
• Interchange of Human-oriented Business Rules
• Rules Systems Supporting Business Communication of Rules
• UCR/Access to Business Rules of Supply Chain Partners
• UCR/Managing Inter-Organizational Business Policies and Practices
• UCR/Managing Inter-Organizational Business Policies and Practices - EX1
• UCR/Managing Inter-Organizational Business Policies and Practices - Original
• UCR/Negotiating eBusiness Contracts Across Rule Platforms

• UCR/Negotiating eCommerce Transactions Through Disclosure of Buyer and Seller Policies and Preferences

• Discussion of UC1 - Negotiating eBusiness Contracts Across Rule Platforms

• UC10 Worked Example

• UC2 Worked Example

• UC3 Worked Example

• UC6 Worked Example

• UC7 Worked Example

• UC8 Worked Example

• UC9 Worked Example

• Calendar

• UCR/Candidate Use Cases for 2nd Draft
• UCR/Candidate Use Cases for 2nd Draft/PublicationAlternative

• Capability to pass descriptive text through RIF

• Credit Card Transaction Authorization

• Decision making in Health Care
• SW rules for Health Care and Life Sciences

• General Use Case Categories
• How to Add a Use Case
• Multi-Dimensional Use Case Classification
• UCR/Use Case Support
• Use Case Support for RIF's Design Constraints
• Use Case Template
• UseCaseTemplate-updated

• Arch/Test Cases
• D. Evaluation: Use Cases
• RIF Use Cases and Requirements
• RIFUCR - List of Requirements (as Found in the Initial Use Cases)
• RIFUCR - Use Cases - Publication2
• UCR/Candidate Use Cases for 2nd Draft
• UCR/Candidate Use Cases for 2nd Draft/PublicationAlternative
• UCR/Use Cases
• Use Cases

• General Use Case Categories

• CategoryGlossaryEntry

• Supply Chain Ordering Lead Time
• UCR/Access to Business Rules of Supply Chain Partners

• XChange

• DonaldChapin

• Arch/Extensibility Design Choices

• ChrisWelty

• ChristianDeSainteMarie

• BottomUpClassification
• Classification of Rules
• Classification of Rules w.r.t. their role
• Multi-Dimensional Use Case Classification
• RifClassification

• RIFUCR - List of Classified Requirements (with Duplicate Elimination)

• UCR/Collaborative Policy Development for Dynamic Spectrum Access

• Method For Collecting And Organising Design Constraints

• ISWC Colocation Proposal

• Rule-Based Combined Access to XML and RDF Data

• Automated Trust Establishment for eCommerce
• Refund Policies in E-Commerce
• UCR/Negotiating eCommerce Transactions Through Disclosure of Buyer and Seller Policies and Preferences

• Common Logic

• Rules Systems Supporting Business Communication of Rules

• Core/Compatibility
• Core/RIF-OWL Compatibility
• Core/RIF-RDF Compatibility
• F2F1 Breakout Session on OWL and RDF Compatibility
• F2F2/Approaches to OWL Compatibility
• OWL Compatibility
• PRdialect/Compatibility
• Product Compatibility
• RDF Compatibility
• SWC/OWL-Compatibility
• SWC/RDF-Compatibility
• Semantic Web Compatibility

• RegulatoryCompliance

• Compliant applications must handle any valid RIF document in a predictable way

• Arch/RIF Components
• Arch/RIF Components/RIF Dialect Structure
• Arch/RIF Components/RIF Expression Components
• Arch/RIF Components/Rules and Rule Sets

• Policy - Preference Computing
• Rule Based Service Level Management and SLAs for Service Oriented Computing

• UCR/Conclusion

• Concrete examples given in Protune

• A. RIF Condition Language
• A.7 Mapping Rule Bodies of Other Languages to RIF Condition Language
• PRdialect/Condition

• A.1 Basis: Positive Conditions
• A.1.0 Nucleus: Positive Conditions
• A.1.1 Basis: Positive Conditions over Bipartitioned Constants
• A.2 Extension: Negative Conditions
• A.3 Extension: Builtins in Conditions
• A.4 Extension: Resource Conditions
• A.5 Extension: Ontology Conditions
• CORE/Conditions
• CORE/Conditions/Positive
• CORE/Positive Conditions
• Core/Conditions
• Core/Conditions 2007-6-28
• Core/Positive Conditions
• Core/Positive Conditions 2007-6-28
• Core/Slotted Conditions
• Core/Slotted Conditions 2007-6-28
• PositiveConditions.dtd

• wikitr demo/Cones

• Conflict Resolution Strategies

• DanConnolly

• Consistency with major market technologies
• UCR/Critical Factors Analysis/Consistency with W3C specifications

• A.1.1 Basis: Positive Conditions over Bipartitioned Constants
• Arch/XML Syntax Issues/Constants

• A.6 Semantics of Constraints
• Design Constraints
• Design Constraints/Terminology
• Method For Collecting And Organising Design Constraints
• Use Case Support for RIF's Design Constraints

• Core/List Constructor
• Core/List Constructor 2007-6-28
• Core/List Constructor-alt

• E-Procurement Contract Exchange, with Default-Inheritance Ontologies

• Discussion of UC1 - Negotiating eBusiness Contracts Across Rule Platforms
• E-Contracts with Exceptions, with OWL Process Ontologies
• UCR/Negotiating eBusiness Contracts Across Rule Platforms

• Design Contraints

• Policy-Based Transaction Authorization and Access Control

• Arch/Naming Conventions

• Core
• Core mapping to PR
• Core/Compatibility
• Core/Conditions
• Core/Conditions 2007-6-28
• Core/EndNotes
• Core/EndNotes 2007-6-28
• Core/Horn Rules
• Core/Horn Rules 2007-6-28
• Core/Horn Rules Alternative
• Core/List Constructor
• Core/List Constructor 2007-6-28
• Core/List Constructor-alt
• Core/Overview
• Core/Overview 2007-6-28
• Core/Positive Conditions
• Core/Positive Conditions 2007-6-28
• Core/RIF-OWL Compatibility
• Core/RIF-RDF Compatibility
• Core/References
• Core/Rules
• Core/Rules 2007-6-28
• Core/Slotted Conditions
• Core/Slotted Conditions 2007-6-28
• Core/Specification
• Core/Specification 2007-6-28
• Core/Validation
• RIF Core must cover pure Prolog
• RIF Core must support deduction rules
• The RIF Core must be able to accept OWL KBs as data
• The RIF Core must be able to accept RDF triples as data
• The RIF Core must be able to accept XML elements as data

• UCR/Coverage

• UCR/What is a Rule Interchange Format And Why Create One

• Credit Card Transaction Authorization
• Rules for a Credit Approval Service

• Goals, Critical Success Factors and Requirements
• Towards a Rule Interchange Format: Goals, Critical Success Factors, Requirements
• UCR/Critical Factors Analysis
• UCR/Critical Factors Analysis/Consistency with W3C specifications
• UCR/Critical Factors Analysis/Exchange of Rules
• UCR/Critical Factors Analysis/Open Issues
• UCR/Critical Factors Analysis/Widescale Adoption

• Cross-Platform Rule Development & Deployment

• DanConnolly

• DarkoAnicic

• Arch/Data Sets
• Arch/RDF-Data
• Rule-Based Combined Access to XML and RDF Data
• UCR/Vocabularly Mapping for Data Integration
• UCR/Vocabulary Mapping for Data Integration

• Functions and Operators on Dates and Times

• DaveReynolds

• DavidHirtle

• ChristianDeSainteMarie
• JosDeBruijn
• JosDeBruijn/MyDict
• JosDeRoo

• MikeDean

• DeborahNichols
• DeborahNichols/UCR saved draft

• Decision Support
• Decision making in Health Care
• UCR/Decision Support/JeffPan's proposed slight extension to the example
• UCR/Ruleset Integration for Medical Decision Support

• REWERSE's Proposal: A Versatile, Declarative Format with Annotations

• E-Procurement Contract Exchange, with Default-Inheritance Ontologies

• Cross-Platform Rule Development & Deployment

• Alternative Extensible Design
• Arch/Extensibility Design Choices
• Design Constraints
• Design Constraints/Terminology
• Design Contraints
• Design Principles
• Extensible Design
• F2F2/DesignGoals1
• Method For Collecting And Organising Design Constraints
• RIF Design
• UCR/Design Goals
• Use Case Support for RIF's Design Constraints

• Cross-Platform Rule Development & Deployment
• UCR/Collaborative Policy Development for Dynamic Spectrum Access

• StanDevitt

• Arch/RIF Components/RIF Dialect Structure

• RuleLanguageDialects

• JosDeBruijn/MyDict

• Interchange of Business Rules between Business People in Different Organizations (Units) When Making Agreements

• Labeling Brain Anatomical Structures in Digital Images

• Multi-Dimensional Use Case Classification

• UCR/Negotiating eCommerce Transactions Through Disclosure of Buyer and Seller Policies and Preferences

• Price Discounting

• OriginalRIFRAFDiscriminators

• Discussion of UC1 - Negotiating eBusiness Contracts Across Rule Platforms

• Distributed e-Learning

• UCR/Document issues

• DonaldChapin

• Draft - Requirements on RIF
• UCR/Candidate Use Cases for 2nd Draft
• UCR/Candidate Use Cases for 2nd Draft/PublicationAlternative

• Rule Interchange Through Test-Driven Verification and Validation

• RIFUCR - List of Classified Requirements (with Duplicate Elimination)

• UCR/Collaborative Policy Development for Dynamic Spectrum Access

• Arch/XML Syntax Issues/Root Element

• RIFUCR - List of Classified Requirements (with Duplicate Elimination)

• Rule-Based Email Manipulation

• SWC/Embeddings

• Scoped negation, Encapsulation

• Core/EndNotes
• Core/EndNotes 2007-6-28
• SWC/EndNotes

• EnricoFranconi

• Enterprise Information Integration

• CategoryGlossaryEntry

• Arch/Equilty

• Operationally Equivalent Translations

• MichaelErdmann

• Automated Trust Establishment for Accessing Medical Records
• Automated Trust Establishment for eCommerce

• TeleconEtiquette

• D. Evaluation: Use Cases
• E. Evaluation: Interoperation/Interchange

• UC10 Worked Example
• UC2 Worked Example
• UC3 Worked Example
• UC6 Worked Example
• UC7 Worked Example
• UC8 Worked Example
• UC9 Worked Example

• E-Contracts with Exceptions, with OWL Process Ontologies

• E-Procurement Contract Exchange, with Default-Inheritance Ontologies
• UCR/Critical Factors Analysis/Exchange of Rules

• Arch/RIF Components/RIF Expression Components

• Extended RIF must cover FOL
• Extended RIF must support production rules

• Arch/Extensibility
• Arch/Extensibility Design Choices
• Semantics Extensibility Point

• Arch/Extensibility2

• Arch/Extensibility3

• Alternative Extensible Design
• Extensible Design

• A.2 Extension: Negative Conditions
• A.3 Extension: Builtins in Conditions
• A.4 Extension: Resource Conditions
• A.5 Extension: Ontology Conditions
• B. Extension: RIF Horn Rule Language
• B. Extension: RIF Rule Language
• B.2 Extension: General Rule Sets
• C. Extension: RIF Production and Reaction Rule Languages

• UCR/Interchanging Rule Extensions to OWL

• Interchange of Business Rules between People Who Run Organizations and Internally/Externally Supplied IT Systems

• F2F1
• F2F1 Breakout Session on OWL and RDF Compatibility

• F2F10

• F2F1
• F2F1 Breakout Session on OWL and RDF Compatibility
• F2F10
• F2F2
• F2F2/Approaches to OWL Compatibility
• F2F2/DesignGoals1
• F2F2/RequirementsBrainstorming
• F2F3
• F2F4
• F2F4 MITRE Proposal
• F2F4/UCR
• F2F5
• F2F6
• F2F7
• F2F8
• F2F9

• F2F3

• F2F4
• F2F4 MITRE Proposal
• F2F4/UCR

• F2F5

• F2F6

• F2F7

• F2F8

• F2F9

• Face-to-Face Meetings

• Goals, Critical Success Factors and Requirements
• Towards a Rule Interchange Format: Goals, Critical Success Factors, Requirements
• UCR/Critical Factors Analysis
• UCR/Critical Factors Analysis/Consistency with W3C specifications
• UCR/Critical Factors Analysis/Exchange of Rules
• UCR/Critical Factors Analysis/Open Issues
• UCR/Critical Factors Analysis/Widescale Adoption

• Filling the holes of OWL

• First-Order Logic

• Method For Collecting And Organising Design Constraints

• REWERSE's Proposal: A Versatile, Declarative Format with Annotations
• Towards a Rule Interchange Format: Goals, Critical Success Factors, Requirements
• UCR/Motivation for a Rule Interchange Format
• UCR/What is a Rule Interchange Format And Why Create One

• B.1.1 CLP Formulation

• RIFUCR - List of Requirements (as Found in the Initial Use Cases)

• Four Modal Operators

• Frame-based representation, Inheritance of defaults, Reification
• Higher Order and Frame Based Syntax

• Rulesystem Arrangement Framework

• EnricoFranconi

• FrançoisBry

• Organizing a Vacation with Friends

• Functions and Operators on Dates and Times
• Functions and Operators on Numerics
• Functions on Strings
• XPathFunctions

• Fuzzy Reasoning with Brain Anatomical Structures

• GaryHallmark

• B.2 Extension: General Rule Sets
• General Use Case Categories

• GerdWagner

• GiorgosStamou
• GiorgosStoilos

• AdrianGiurca
• AdrianGiurca/FLD-Review

• CategoryGlossaryEntry
• Glossary
• PRdialect/Glossary

• Goals, Critical Success Factors and Requirements
• Towards a Rule Interchange Format: Goals, Critical Success Factors, Requirements
• UCR/Design Goals
• UCR/Goals

• F2F2/DesignGoals1

• BenjaminGrosof

• AdminGroup
• SystemPagesGroup
• WorkingGroup

• SW Guide

• Rule-Based Intelligent Guiding

• JohnHall

• GaryHallmark

• HaroldBoley

• HassanAitKaci

• SandroHawke

• Decision making in Health Care
• SW rules for Health Care and Life Sciences

• JamesHendler

• HiLog

• Higher Order and Frame Based Syntax
• Higher-Orderness

• DavidHirtle

• PascalHitzler

• B. Extension: RIF Horn Rule Language
• B.1 Horn Rules
• CORE/Horn Rules
• CORE/Rules/Horn
• Core/Horn Rules
• Core/Horn Rules 2007-6-28
• Core/Horn Rules Alternative
• Horn Logic
• Horn Rules Semantics

• IanHorrocks

• How to Add a Use Case

• Interchange of Human-oriented Business Rules

• IanHorrocks

• Arch/XML Syntax Issues/Identifying Rulesets

• IgorMozetic

• Labeling Brain Anatomical Structures in Digital Images

• Implementation plans

• Implementations/SWRL

• Importing rules to check data compliance

• Enterprise Information Integration
• Information Integration
• Information Integration with Rules and Taxonomies

• E-Procurement Contract Exchange, with Default-Inheritance Ontologies
• Frame-based representation, Inheritance of defaults, Reification

• RIFUCR - List of Requirements (as Found in the Initial Use Cases)

• Enterprise Information Integration
• Information Integration
• Information Integration with Rules and Taxonomies
• UCR/Ruleset Integration for Medical Decision Support
• UCR/Vocabularly Mapping for Data Integration
• UCR/Vocabulary Mapping for Data Integration

• Rule-Based Intelligent Guiding

• UCR/Publication of Intensional, Interlinked Metadata

• UCR/Managing Inter-Organizational Business Policies and Practices
• UCR/Managing Inter-Organizational Business Policies and Practices - EX1
• UCR/Managing Inter-Organizational Business Policies and Practices - Original

• E. Evaluation: Interoperation/Interchange
• Interchange of Business Rules between Business People in Different Organizations (Units) When Making Agreements
• Interchange of Business Rules between People Who Run Organizations and Internally/Externally Supplied IT Systems
• Interchange of Human-oriented Business Rules
• Interpretation and Interchange of Regulations
• Rule Interchange Through Test-Driven Verification and Validation
• Third Party Rule-Interchange Services
• Towards a Rule Interchange Format: Goals, Critical Success Factors, Requirements
• UCR/Motivation for a Rule Interchange Format
• UCR/What is a Rule Interchange Format And Why Create One

• UCR/Interchanging Rule Extensions to OWL

• UCR/Publication of Intensional, Interlinked Metadata
• UCR/Publishing Rules for Interlinked Metadata

• Interchange of Business Rules between People Who Run Organizations and Internally/Externally Supplied IT Systems

• Internet search: combining query language, rule languages and scoped negation

• RIFUCR - Use cases - Interoperability

• E. Evaluation: Interoperation/Interchange

• Interpretation and Interchange of Regulations

• Arch/Introduction
• UCR/Introduction
• wikitr demo/Introduction

• Issue-31

• Arch/XML Syntax Issues 1
• Arch/XML Syntax Issues 2
• Arch/XML Syntax Issues/Constants
• Arch/XML Syntax Issues/Identifying Rulesets
• Arch/XML Syntax Issues/Positional Arguments
• Arch/XML Syntax Issues/Root Element
• BLD Name Issues
• UCR/Critical Factors Analysis/Open Issues

• JamesHendler

• MinsuJang

• JeffPan
• UCR/Decision Support/JeffPan's proposed slight extension to the example

• JingMei

• JohnHall

• JosDeBruijn
• JosDeBruijn/MyDict
• JosDeRoo

• HassanAitKaci

• RifRafKickoffScribeNotes

• MichaelKifer

• Rich Knowledge Representation

• StasinosKonstantopoulos

• MarkusKrötzsch

• Labeling Brain Anatomical Structures in Digital Images

• A. RIF Condition Language
• A.7 Mapping Rule Bodies of Other Languages to RIF Condition Language
• B. Extension: RIF Horn Rule Language
• B. Extension: RIF Rule Language
• RuleLanguageDialects
• WebRuleLanguage

• A.7 Mapping Rule Bodies of Other Languages to RIF Condition Language
• C. Extension: RIF Production and Reaction Rule Languages
• F. Mappings to Other Languages

• OraLassila

• PaulaLaviniaPatranjan

• Supply Chain Ordering Lead Time

• Distributed e-Learning

• LeoraMorgenstern

• Rule Based Service Level Management and SLAs for Service Oriented Computing
• Rule-based Service Level Agreements (SLA) and Web Services

• A Library of Biomedical ontologies

• SW rules for Health Care and Life Sciences

• Core/List Constructor
• Core/List Constructor 2007-6-28
• Core/List Constructor-alt
• List of BLD built-ins
• List of Rule Systems
• List of functions and operators
• RIFUCR - List of Classified Requirements (with Duplicate Elimination)
• RIFUCR - List of Requirements (as Found in the Initial Use Cases)
• ScribesList

• UCR/Requirements Lists

• HiLog

• Common Logic
• First-Order Logic
• Horn Logic
• Transaction Logic

• Interchange of Business Rules between Business People in Different Organizations (Units) When Making Agreements

• Rule Based Service Level Management and SLAs for Service Oriented Computing

• Managing incomplete information
• RIFUCR - Use cases - Managing Rule
• UCR/Managing Inter-Organizational Business Policies and Practices
• UCR/Managing Inter-Organizational Business Policies and Practices - EX1
• UCR/Managing Inter-Organizational Business Policies and Practices - Original

• Rule-Based Email Manipulation

• Map

• A.7 Mapping Rule Bodies of Other Languages to RIF Condition Language
• Ontology Mapping with OWL and Rules
• UCR/Vocabularly Mapping for Data Integration
• UCR/Vocabulary Mapping for Data Integration

• F. Mappings to Other Languages

• ChristianDeSainteMarie

• MarkusKrötzsch

• MathML

• Automated Trust Establishment for Accessing Medical Records
• UCR/Ruleset Integration for Medical Decision Support

• 2005-12-20 Meeting
• 2006-01-03 Meeting
• 2006-01-10 Meeting
• 2006-01-17 Meeting
• 2006-01-24 Meeting
• 2006-01-31 Meeting
• 2006-02-07 Meeting
• 2006-02-14 Meeting
• 2006-02-21 Meeting
• 2006-03-07 Meeting
• 2006-03-14 Meeting
• 2006-03-21 Meeting
• 2006-03-27 Meeting
• 2006-03-28 Meeting
• 2006-04-04 Meeting
• 2006-04-11 Meeting
• 2006-04-18 Meeting
• 2006-04-25 Meeting
• 2006-05-02 Meeting
• 2006-05-09 Meeting
• 2006-05-16 Meeting
• 2006-05-23 Meeting
• 2006-05-30 Meeting
• 2006-06-20 Meeting
• 2006-06-27 Meeting
• 2006-07-04 Meeting
• 2006-07-18 Meeting
• 2006-07-25 Meeting
• 2006-08-01 Meeting
• 2006-08-08 Meeting
• 2006-08-15 Meeting
• 2006-08-22 Meeting
• 2006-08-29 Meeting
• 2006-09-05 Meeting
• 2006-09-12 Meeting
• 2006-09-19 Meeting
• 2006-09-26 Meeting
• 2006-10 10 Meeting
• 2006-10-03 Meeting
• 2006-10-10 Meeting
• 2006-10-14 Meeting
• 2006-10-17 Meeting
• 2006-10-24 Meeting
• 2006-10-31 Meeting
• 2006-11-14 Meeting
• 2006-11-21 Meeting
• 2006-12-05 Meeting
• 2006-12-12 Meeting
• 2006-12-19 Meeting
• 2007-01-02 Meeting
• 2007-01-09 Meeting
• 2007-01-16 Meeting
• 2007-01-23 Meeting
• 2007-01-30 Meeting
• 2007-02-06 Meeting
• 2007-02-13 Meeting
• 2007-02-20 Meeting
• 2007-03-06 Meeting
• 2007-03-20 Meeting
• 2007-03-27 Meeting
• 2007-04-03 Meeting
• 2007-04-10 Meeting
• 2007-04-17 Meeting
• 2007-04-24 Meeting
• 2007-05-01 Meeting
• 2007-05-08 Meeting
• 2007-05-15 Meeting
• 2007-05-22 Meeting
• 2007-05-29 Meeting
• 2007-06-12 Meeting
• 2007-06-19 Meeting
• 2007-06-26 Meeting
• 2007-07-03 Meeting
• 2007-07-10 Meeting
• 2007-07-17 Meeting
• 2007-07-24 Meeting
• 2007-07-31 Meeting
• 2007-08-07 Meeting
• 2007-08-14 Meeting
• 2007-08-21 Meeting
• 2007-08-28 Meeting
• 2007-09-04 Meeting
• 2007-09-11 Meeting
• 2007-09-18 Meeting
• 2007-10-01 Meeting
• 2007-10-02 Meeting
• 2007-10-09 Meeting
• 2007-10-16 Meeting
• 2007-10-23 Meeting
• 2007-10-30 Meeting
• 2007-11-13 Meeting
• 2007-11-27 Meeting
• 2007-12-11 Meeting
• 2007-12-18 Meeting
• 2008-01-29 Meeting
• Meeting Attendance

• Face-to-Face Meetings
• Meetings

• JingMei

• Message Transformation

• Meta-data for currency of rules
• Meta-data indicating executability of rules
• Meta-model

• UCR/Publication of Intensional, Interlinked Metadata
• UCR/Publishing Rules for Interlinked Metadata

• Method For Collecting And Organising Design Constraints

• UCR/Methodology

• MichaelErdmann
• MichaelKifer
• MichaelSintek

• MikeDean

• Mini PR

• MinsuJang

• Four Modal Operators

• AbstractModel
• UCR/Basic RIF Processing Model

• LeoraMorgenstern

• UCR/Motivation for a Rule Interchange Format

• IgorMozetic

• Multi-Dimensional Use Case Classification

• JosDeBruijn/MyDict

• N3

• BLD Name Issues

• Arch/Naming Conventions

• A.2 Extension: Negative Conditions

• Discussion of UC1 - Negotiating eBusiness Contracts Across Rule Platforms
• UCR/Negotiating eBusiness Contracts Across Rule Platforms
• UCR/Negotiating eCommerce Transactions Through Disclosure of Buyer and Seller Policies and Preferences

• DeborahNichols
• DeborahNichols/UCR saved draft

• bNode Semantics

• UCR/Requirements (Not in This Version)

• Core/EndNotes
• Core/EndNotes 2007-6-28
• RifRafKickoffScribeNotes
• SWC/EndNotes

• Rule-based User Notification (RUN) framework

• A.1.0 Nucleus: Positive Conditions

• Functions and Operators on Numerics

• Offer module construct for scoped positive and negation as failure queries

• UCR/What is a Rule Interchange Format And Why Create One

• E-Contracts with Exceptions, with OWL Process Ontologies
• E-Procurement Contract Exchange, with Default-Inheritance Ontologies

• A.5 Extension: Ontology Conditions
• Ontology Mapping with OWL and Rules

• UCR/Critical Factors Analysis/Open Issues

• Operationally Equivalent Translations

• Four Modal Operators
• Functions and Operators on Dates and Times
• Functions and Operators on Numerics

• OraLassila

• UCR/BPEL Orchestration of Rule-Based Web Services

• First-Order Logic
• Higher Order and Frame Based Syntax

• Supply Chain Ordering Lead Time

• Higher-Orderness

• Method For Collecting And Organising Design Constraints

• UCR/Managing Inter-Organizational Business Policies and Practices
• UCR/Managing Inter-Organizational Business Policies and Practices - EX1
• UCR/Managing Inter-Organizational Business Policies and Practices - Original

• Interchange of Business Rules between Business People in Different Organizations (Units) When Making Agreements
• Interchange of Business Rules between People Who Run Organizations and Internally/Externally Supplied IT Systems

• Rule-Based Reactive Organizer

• Organizing a Vacation with Friends

• Rule Based Service Level Management and SLAs for Service Oriented Computing

• OriginalRIFRAFDiscriminators
• UCR/Managing Inter-Organizational Business Policies and Practices - Original

• A.7 Mapping Rule Bodies of Other Languages to RIF Condition Language
• F. Mappings to Other Languages

• Outreach

• BLD/Overview
• Core/Overview
• Core/Overview 2007-6-28
• FLD/Overview
• PRdialect/Overview
• SWC/Overview

• PageTest

• SystemPagesGroup

• JeffPan
• UCR/Decision Support/JeffPan's proposed slight extension to the example

• BijanParsia

• UCR/Access to Business Rules of Supply Chain Partners

• RIFUCR - Use cases - Third Party
• Third Party Rule-Interchange Services

• PascalHitzler

• PeterPatelSchneider

• XPathFunctions

• PaulaLaviniaPatranjan

• PRdialect/Pattern

• PaulVincent

• PaulaLaviniaPatranjan

• PeerTrust

• Interchange of Business Rules between Business People in Different Organizations (Units) When Making Agreements
• Interchange of Business Rules between People Who Run Organizations and Internally/Externally Supplied IT Systems

• Permit restricted form of equality

• Personalisation and Uncertainty -- Representing some levels of fuzzy rules with the help of datatype built-ins

• PeterPatelSchneider

• Cross-Platform Rule Development & Deployment

• Discussion of UC1 - Negotiating eBusiness Contracts Across Rule Platforms
• UCR/Negotiating eBusiness Contracts Across Rule Platforms

• Semantics Extensibility Point

• Refund Policies in E-Commerce
• UCR/Managing Inter-Organizational Business Policies and Practices
• UCR/Managing Inter-Organizational Business Policies and Practices - EX1
• UCR/Managing Inter-Organizational Business Policies and Practices - Original
• UCR/Negotiating eCommerce Transactions Through Disclosure of Buyer and Seller Policies and Preferences

• Policy - Preference Computing
• Policy-Based Transaction Authorization and Access Control
• RIFUCR - Use cases - Policy-Based
• RegretsPolicy
• UCR/Collaborative Policy Development for Dynamic Spectrum Access

• AxelPolleres

• Portability

• Arch/XML Syntax Issues/Positional Arguments

• A.1 Basis: Positive Conditions
• A.1.0 Nucleus: Positive Conditions
• A.1.1 Basis: Positive Conditions over Bipartitioned Constants
• CORE/Conditions/Positive
• CORE/Positive Conditions
• Core/Positive Conditions
• Core/Positive Conditions 2007-6-28
• PositiveConditions.dtd

• UCR/Managing Inter-Organizational Business Policies and Practices
• UCR/Managing Inter-Organizational Business Policies and Practices - EX1
• UCR/Managing Inter-Organizational Business Policies and Practices - Original

• Policy - Preference Computing

• UCR/Negotiating eCommerce Transactions Through Disclosure of Buyer and Seller Policies and Preferences

• Price Discounting

• Design Principles

• E-Contracts with Exceptions, with OWL Process Ontologies

• UCR/Basic RIF Processing Model

• E-Procurement Contract Exchange, with Default-Inheritance Ontologies

• Product Compatibility

• C. Extension: RIF Production and Reaction Rule Languages
• Production Rule

• Prolog
• Pure Prolog
• RIF Core must cover pure Prolog
• Standard RIF should be Prolog-like but not Prolog-compatible

• F2F4 MITRE Proposal
• ISWC Colocation Proposal
• REWERSE's Proposal: A Versatile, Declarative Format with Annotations

• Proposals for RIF's design goals

• Concrete examples given in Protune

• Publication
• Publication of semantics (e.g. SKOS, RDFS)
• UCR/Candidate Use Cases for 2nd Draft/PublicationAlternative
• UCR/Publication
• UCR/Publication of Intensional, Interlinked Metadata

• RIFUCR - Use Cases - Publication2

• UCR/Publishing Rules for Interlinked Metadata

• Pure Prolog

• XQuery

• R2ML

• RifRafKickoffScribeNotes

• PRdialect
• PRdialect/Action
• PRdialect/Compatibility
• PRdialect/Condition
• PRdialect/Glossary
• PRdialect/Overview
• PRdialect/Pattern
• PRdialect/Rules

• C. Extension: RIF Production and Reaction Rule Languages

• Rule-Based Reactive Organizer

• Real-time contract exchange

• Fuzzy Reasoning with Brain Anatomical Structures

• RecentScribes

• Automated Trust Establishment for Accessing Medical Records

• BLD/References
• Core/References
• FLD/References
• SWC/References

• Refund Policies in E-Commerce

• RegretsPolicy

• Interpretation and Interchange of Regulations

• RegulatoryCompliance

• Frame-based representation, Inheritance of defaults, Reification

• Rich Knowledge Representation

• Personalisation and Uncertainty -- Representing some levels of fuzzy rules with the help of datatype built-ins

• Draft - Requirements on RIF
• F2F2/RequirementsBrainstorming
• Goals, Critical Success Factors and Requirements
• RIF Use Cases and Requirements
• RIFUCR - List of Classified Requirements (with Duplicate Elimination)
• RIFUCR - List of Requirements (as Found in the Initial Use Cases)
• Towards a Rule Interchange Format: Goals, Critical Success Factors, Requirements
• UCR/Requirements
• UCR/Requirements (Not in This Version)
• UCR/Requirements Lists

• Conflict Resolution Strategies

• WG Resolutions

• A.4 Extension: Resource Conditions

• Response to PPS1
• Response to PPS2

• Supporting the Reuse of Rules

• AdrianGiurca/FLD-Review

• DaveReynolds

• Rich Knowledge Representation

• RifClassification
• RifRafKickoffScribeNotes

• JosDeRoo

• Arch/XML Syntax Issues/Root Element

• A.7 Mapping Rule Bodies of Other Languages to RIF Condition Language
• Arch/RIF Components/Rules and Rule Sets
• B. Extension: RIF Horn Rule Language
• B. Extension: RIF Rule Language
• B.2 Extension: General Rule Sets
• Business Rule
• C. Extension: RIF Production and Reaction Rule Languages
• Cross-Platform Rule Development & Deployment
• Discussion of UC1 - Negotiating eBusiness Contracts Across Rule Platforms
• List of Rule Systems
• Production Rule
• RIF RuleML FOAF
• RIFUCR - Use cases - Managing Rule
• Rule
• Rule Based Service Level Management and SLAs for Service Oriented Computing
• Rule Interchange Through Test-Driven Verification and Validation
• Rule-Based Combined Access to XML and RDF Data
• Rule-Based Email Manipulation
• Rule-Based Intelligent Guiding
• Rule-Based Reactive Organizer
• Rule-based Service Level Agreements (SLA) and Web Services
• Rule-based User Notification (RUN) framework
• RuleLanguageDialects
• RuleML
• Third Party Rule-Interchange Services
• Towards a Rule Interchange Format: Goals, Critical Success Factors, Requirements
• UCR/BPEL Orchestration of Rule-Based Web Services
• UCR/Interchanging Rule Extensions to OWL
• UCR/Motivation for a Rule Interchange Format
• UCR/Negotiating eBusiness Contracts Across Rule Platforms
• UCR/What is a Rule Interchange Format And Why Create One
• WebRuleLanguage

• Arch/RIF Components/Rules and Rule Sets
• B.1 Horn Rules
• CORE/Horn Rules
• CORE/Rules
• CORE/Rules/Horn
• Classification of Rules
• Classification of Rules w.r.t. their role
• Core/Horn Rules
• Core/Horn Rules 2007-6-28
• Core/Horn Rules Alternative
• Core/Rules
• Core/Rules 2007-6-28
• Horn Rules Semantics
• Information Integration with Rules and Taxonomies
• Interchange of Business Rules between Business People in Different Organizations (Units) When Making Agreements
• Interchange of Business Rules between People Who Run Organizations and Internally/Externally Supplied IT Systems
• Interchange of Human-oriented Business Rules
• Ontology Mapping with OWL and Rules
• PRdialect/Rules
• Rules Systems Supporting Business Communication of Rules
• Rules for a Credit Approval Service
• SWSL-Rules
• Supporting the Reuse of Rules
• UCR/Access to Business Rules of Supply Chain Partners
• UCR/Critical Factors Analysis/Exchange of Rules
• UCR/Publishing Rules for Interlinked Metadata

• UCR/Ruleset Integration for Medical Decision Support

• Arch/XML Syntax Issues/Identifying Rulesets

• Rulesystem Arrangement Framework

• Interchange of Business Rules between People Who Run Organizations and Internally/Externally Supplied IT Systems

• Response to PPS1

• Response to PPS2