Loading ...
Sorry, an error occurred while loading the content.

ICCBR EXPPORT - date correction

Expand Messages
  • leake_david
    The correct EXPPORT workshop date is *9 July* (corrected below). Thanks, and apologies for the typo! David
    Message 1 of 1 , Mar 12, 2013
    View Source
    • 0 Attachment
      The correct EXPPORT workshop date is *9 July* (corrected below). Thanks, and apologies for the typo!

      David


      On 3/12/2013 1:48 PM, leake_david wrote:
      > *Call for Papers. EXPPORT Workshop* at ICCBR 2013
      > EXperience reuse: Provenance, Process-ORientation and Traces
      >
      > July 9th 2013, Saratoga Springs, USA
      >
      >
      > _Workshop Description_
      >
      > *EXPPORT: EXperience reuse: Provenance, Process-ORientation and Traces*, is a workshop aiming to provide a medium of exchange for information in CBR for Processes, Traces, and Workflows research. Provenance, process-oriented CBR, and traces are all strong areas of current interest in the CBR community, and have close relationships. Process-oriented CBR focuses largely on workflows, which define sequences of actions for use and reuse. Provenance captures the results of such sequences, providing a resource for capturing workflow cases and for analyzing how action sequences may be refined. Traces capture the results of action sequences generated "on the fly," for example, as performed by the user of a computer system, and traces research must contend with how to generate useful cases from execution information.
      >
      > Consequently, several types of contributions are of interest of this workshop, related to a spectrum of areas such as *Business Process Management, Software Process reuse, reproducibility, learning by observation/demonstration, trace-based reasoning, opponent modeling in games*.
      >
      > Business Process Management (BPM) is a set of activities aimed at defining, executing, monitoring and optimizing BP, with the objective of making the business of an enterprise as effective and efficient as possible, and of increasing its economic success. Such activities are highly automated, typically by means of the workflow technology. BPM activities, and BP optimization in particular, may ask the enterprise to be able toflexibly change and adapt the predefined process schema, in response to expected situations (e.g. new laws, reengineering efforts) as well as to unanticipated exceptions and problems in the operating environment (e.g. emergencies). Agile workflow technology is the technical solution to deal with such adaptation and overriding needs. In order to provide an effective and quick workflow change support, many agile workflow systems share the idea of recalling and reusing concrete examples of changes adopted in the past. To this end, Case-based Reasoning (CBR) has been proposed as a natural methodological solution.
      >
      > Software Processes can be studied from different points of view. In the Software Engineering field, artifacts like models, diagrams, etc. define Software Development Processes that can be reused to generate new applications. There is also a significant trend on reusing different software components to compose a workflow that models the behavior of a system. Web Services, Scientific Software or Product Lines are some examples of such approaches, and we cannot forget the closely related task of Planning. All these areas are related to Software Processes and can take advantage of the CBR paradigm to reuse existing solutions, components, compositions or plans.
      >
      > In many complex domains such as automobile driving, for example, there is no explicit model of any process, or process models are not well known. Moreover, processes as well as knowledge evolve over time and their dynamic nature must be taken into account. This has given rise to significant interest in artificial intelligence approaches based on traces.
      >
      > An important part of users' experience can be stored in traces that record human activity supported by computer systems. Such traces can record user interactions with a computer system through an application, a game, etc. Traces take the form of sequences of temporally situated actions and may be collected either from log files, text files or from sensors in applications programs. The opportunity to collect user experience as traces enables reusing them by CBR. Thus they constitute a knowledge container from which a CBR process may build and reuse cases. Traces may also be used to discover or refine an underlying process model, or to study how actual usage fits a recommended process model, good practices, etc. The exploitation of these containers for various purposes presents opportunities for many facets of AI: reuse traces, dynamic users assistance, activity analysis, workflow mining and more generally cases and knowledge acquisition.
      >
      >
      > _Aims and Scope_
      >
      > The aim of the EXPPORT workshop is to provide a forum for the discussion of trends, research issues and practical experiences in all the areas illustrated above, to understand the commonalities and differences, and advance the state of the art in all of them, ideally, to forge shared goals and benefit from shared experiences. *Research contributions submitted to the workshop will be related to areas that include, but are not limited to, the following:*
      >
      > * Methodological issues:
      > o Case-based representation of process knowledge (by workflows,
      > traces, plans, etc.)
      > o Case-based retrieval for process reuse and optimization
      > o Similarity measures for process reuse and optimization
      > o Case-based adaptation for process optimization
      > o Extraction of process knowledge, workflow mining
      > o Interplay of provenance, trust, and confidence
      > o Acquisition and management of provenance and meta-data
      > o Use of provenance and meta-data in knowledge discovery, data
      > mining, and text mining for case acquisition
      > o Use of provenance to support case-based reasoning
      > o Provenance representation
      > o Visualization and explanation of process knowledge
      > o Toolkits / methodologies for managing and reusing traces
      > o Architectures of trace reusing systems
      > o Trace models, trace elements and cases
      > o Collecting traces, building/mining cases from traces
      > o Provenance information regarding traces
      > o Learning / adaptation of traces
      > o Reasoning via user demonstrations/observations
      > o Planning from user traces
      > * Applications, systems and tools:
      > o CBR applications in Business Process Management, Software
      > Processes, E-Science, Web Science, E-Governance, E-Health,
      > product development, search, games, cooking, and further
      > application domains
      > o Evaluating CBR tools for PO-CBR
      > o Agile workflow technology with CBR components
      > o CBR in (commercial) workflow management tools
      > o Novel applications of trace-based reasoning
      > o Integration of trace-based techniques and gaming environments
      > o Game playing via user traces
      > * Lessons learned in PO-CBR investigations and trace-based reasoning
      > * Challenge tasks for CBR systems in the context of business
      > processes, software processes, planning processes, search processes
      >
      > Depending on the submissions received, we anticipate pursuing a journal special issue based on extended versions of the best papers from the workshop.
      >
      >
      > _Participation in the Workshop_
      >
      > This workshop will be held on July 8, 2013 as part of the ICCBR 2013 workshop program in Saratoga Springs, USA. This workshop is open to all interested conference participants, but size may be limited by available room facilities.
      >
      > The Organizing Committee will select a subset of the submitted papers for oral presentation. We invite submissions both of *short position papers (4 pages)* and *long papers on research results (10 pages)*.
      >
      > Moreover, time will be reserved for ample discussion, and for a panel representing a sampling of areas.
      >
      >
      > _Submission Procedure and Format_
      >
      > We invite submissions of two types:
      >
      > * *Long research and application papers: a maximum of 10 pages
      > describing original contributions.*
      > * *Short position papers: a maximum of 4 pages describing new research
      > ideas and partially developed frameworks *
      >
      > Papers must be submitted in electronic form as PDF via *EasyChair*: https://www.easychair.org/conferences/?conf=iccbr2013 and *selecting "Workshop 3: EXPPORT: EXperience reuse: Provenance, Process-ORientation and Traces"*.
      >
      >
      > Springer LNCS is the format required for the final camera-ready copy. Authors' instructions along with LaTeX and Word macro files are available on the web at Springer http://www.springer.com/computer/lncs?SGWID=0-164-6-793341-0
      >
      >
      > _Workshop Chairs_
      >
      > David Leake, Indiana University, USA
      > Béatrice Fuchs, LIRIS, Université Jean Moulin Lyon 3, France
      > Stefania Montani, University of Piemonte Orientale, Italy
      > Juan A. Recio García, University Complutense of Madrid, Spain
      >
      >
      > _Program Committee_
      >
      > Pierre-Antoine Champin, University Claude Bernard Lyon 1, France
      > Amélie Cordier, University Claude Bernard Lyon 1, France
      > Pedro A. González-Calero, Complutense University of Madrid, Spain
      > Joseph Kendall-Morwick, Indiana University, USA
      > Mirjam Minor, Frankfurt University, Germany
      > Hector Muñoz-Ávila, Lehigh University, USA
      > Thomas Roth-Berghofer, University of West London, UK
      > Barbara Weber, University of Innsbruck, Austria
      >
      >
      > _Important Dates_
      >
      > *April 10, 2013 Deadline for workshop paper submission*
      > May 10, 2013 Notification of acceptance for workshop papers
      > May 31, 2013 Camera ready copy due
      > July 9, 2013 Workshop held at ICCBR-2013
      >
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.