29 Apr 2010

See also: IRC log





<scribe> scribe: jeffw

hi Eva

<eblomqvi> hi

hi, Udi

<UdiBauman> hi..

Udi, are you able to call in?

udi: experience with decision-support systems, several large systems that basically collect and analyze and recommend
... what should be decided and allow them to document and track decisions. The systems apply to various domains,

including market analysis and using various source, inputs from all parts of the compaines, activity models, and various information systems

udi: market, customer inputs, all kinds of optional scenarios and recommended which would maximize profit.
... The application allowed users to select value drivers and impact global measure of the company.
... Lately an open source project, Ekkli, tries to address how you achieve collective decision-making.
... Companies usually discuss options and limited number of participants and usually not that effective and unstructured and meetings take time.
... usually not tracked and analyzed. These are painful problems in today's decision-making. The way we've tried to address is to use web-based software
... to accumulate knowledge from decision tools and other sources, then using analytical and linguistic algorithms to get to better decisions with less time.
... To do that, there are several principles to guide system, you can always have a top view of the full discussion in one screen, and we classify discussions to types
... and before you start the discussion, you select the type, which is required for our mechanism. When you enter messages into discussion,
... we classify messages to types of speech acts, so you select which speech act for that discussion type and the sentiment in two dimensions (good/bad)
... the system tries to suggest automatic which messages group, which more relevant, and underlying properties, relations between messages, and
... tries to improve the discussion. We want to optimize the time of the participants. Also come up with recommended decisions.
... We currently have an initial prototype. There are about 10 developers, and we also have a lineup of organizations (govt) that want to start using the system.
... it is completely open source and i started going over the wiki, and the topic of situation awareness we have a discussion template for that.

<UdiBauman> http://ekkli.org

udi: We're happy to learn from your work and we can learn from each other.

<UdiBauman> http://xrl.us/ekkli

udi: it has an instance for quality assurance, still a prototype, but you can look here. Currently, we only have one template, scope of action, and another coming.

How does it work physically, are people together for a meeting?

udi: each participant can enter, you can do it online, decide on template of discussion, then just add messages and eventually points out conclusions of discussions.

We might see how the decision format could be instrumented in the tool?

udi: yes, and we have a participant focused on knowledge and perception, and we're always interested in this topic

Are you affiliated with an organization or on your own?

udi: The tool is open source, but also an affiliation with a consulting company on open source technology

eva: I was thinking about these systems, do you have a kind of a model of a decision and a process, perhaps not formalized, but idea of a decision process
... has these parts and so on, do you have something like this that you have agreed on?

udi: our approach is similar to use case, we try to handle specific template types of discussion, we have a theory defined well and the process to derive the decision
... I'm not sure if the process, logic flow, of the arguments and how you arrive the decision, it is not like an abstraction of a decision in that sense
... it is more automatic but can be tested and something we could adopt from you some model of the process

eva: I imagined something like this, you think of the decision process like discussion and argumentation and the end result is some decision

don: if we come up with a format, it should be a messaging format and put it in there and maybe even develop a plug-in for conversations they already have
... to see how well they fit into format and what mining and processing they can do on this

(Jeff summarized work on Information Flow use case with extreme design and neon toolkit)

Eva: it's a work in progress and there are issues with the patterns, but we can make updates in the patterns and happy that things are in use
... it takes time for people to use and now we are discovering these issues
... you wrote about contacint RPI about govt data
... would you like me to contact them?

That would be great..

We will continue the extreme design approach with selected use cases and for next time, I will see if I can have something concrete to show for

the information flow and for a decision core component (basic who decided what, when and where, no criteria, no options, just that something was decided)

We can build from those modules

Thanks to Udi for his presentation and we will continue collaboration with him through wiki and e-mail. We will explore learning from him their concept

model for decisions, discussions and consider the potential opportunity to have our decision format utilized by the open-source tool, Ekkli

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/04/29 15:02:49 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: jeffw
Inferring ScribeNick: jeffw

WARNING: No "Topic:" lines found.

WARNING: No "Present: ... " found!
Possibly Present: Eva UdiBauman don eblomqvi udi
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 29 Apr 2010
Guessing minutes URL: http://www.w3.org/2010/04/29-decision-xg-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

[End of scribe.perl diagnostic output]