Decision Mtg 13 Agenda

From Decision XG
Jump to: navigation, search

Decision Meeting #13 Goal & Agenda


The dial-in information for this week's meeting is here. The Decision Incubator Activity is intended to explore the use cases and design of a Decision Representation format (e.g. in XML, RDF, OWL…) available on the wiki along with its use by participants in testbed settings for experiments and exercises. Each meeting will be an opportunity to summarize progress & contributions to the wiki, review next steps and action items, and to review the current representation format.

Summary from the Last Meeting

At the last meeting (see minutes), the agenda covered four topics: (1) Update on "Core Decision" Model for Decisions; (2) Suggested Process for Exploring and Validating Models; (3) Conversion of Emergency Management Data into Linked Data format; (4) Schedule and Future Papers. Regarding (1), Eva walked us through her example of a decision to choose a shop. The user has a product to buy and needs to decide on a shop to do the purchase. The shops are the options and the criteria are distance and cost. Using the realization pattern, the text is the realization of the question concept and the option is a concrete entry of the shop concept. After some discussion, it appeared that a description pattern might be used effectively here as well. The original idea was that the decision and its components are concepts and the data representing those concepts is the realization, just as a performance of the play Hamlet is a concept and the specific date and time and other details of a particular performance are the realization. One is an extension of the other. We had a good discussion of the potential for utilizing this pattern effectively. Regarding (2), Jeff summarized the main points for a process for exploring and validating the models using tools and an interoperability testbed. Currently, Jeff's colleagues are developing a basic tool to support the decision concepts and format with potential interaction through mobile apps. This would include a data repository as part of the testbed infrastructure to support the client application saving the format. And if we ingest linked data, then we can incorporate easily data from other domains, such as emergency management, by simply putting the data into the linked data format. Eva also described a tool on her end that can support alignment rules, so that rdf data can be aligned with a domain ontology, and we could potentially use this tool as part of this testing. Also other testbed partners could participate. Regarding (3), the emergency management domain, there is an opportunity to use data from that domain, put it in the linked data format, and utilize it for decision-making with these types of tools and format. Regarding (4), we ran out of time to carry on the discussion of schedule and papers.

Since our last meeting, Piotr Nowara provided good comments back on Eva's design for the decision model. Piotr will join us and this will be our major topic for discussion at this current meeting.

Goal for this Meeting

At this thirteenth meeting of the Decision Incubator, we will enjoy hearing from Piotr Nowara and Eva regarding insights they've recently shared about the decision model. Piotr will review his initial comments and Eva will update us on the impact of this feedback on our current updated model. Also we will discuss insights regarding a few patterns (Question, Statement, addressable statements)and a list of the decision patterns and a schedule for implementation and integration.


The following agenda items will be discussed at the next meeting. The topic, time, summary and discussion leader are provided for each agenda item.

(0) Review of Status, Goals & Agenda Overview (5 min, Jeff)

Use of our core component models and patterns list will be mentioned and suggested goals for next few weeks.

(1) Update and Insights on "Core Decision" Model for Decisions (30 min, Eva/Piotr)

Piotr and Eva will update us on the recent shared insights regarding how best to represent the decision model and ideas for improvement.

(2) Pattern Concepts: Statement with Event Attributes, Statement with Variable, Links to Statements (15 min, Jeff)

Jeff will share some thoughts to spark discussion on how to implement patterns that he's considered for supporting (a) any decision component (question, option, criteria) as statements which contain the common event-type attributes (who, what, where, when), (b) question (statement with variable), and (c) linkable statements.

(3) Pattern Implementation Schedule and Future Papers. (15 minutes, Jeff/Marion)

Marion will cover some paper opportunities for us to share insights and gather feedback on our current activities at upcoming conferences. Jeff will recommend a schedule for completion of our work based on a list of patterns, signing people up for each, and having a rough schedule for development and integration and tryout in the tools/testbed mentioned previously.