<div dir="ltr">On Wed, Mar 6, 2013 at 1:33 PM, marc <span dir="ltr"><<a href="mailto:marc@merkstduwas.de" target="_blank">marc@merkstduwas.de</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi Michael,<br> <br> You wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Frauke and Alex,<br> Frauke said:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> The first question must be: in which case is it necessary to bring<br> different tools together and why?<br> If you can answer this question, we can go on.<br> </blockquote></blockquote> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> We answered this already. Cooperation is necessary in order to level<br> the playing field among platforms, prevent the formation of a de-facto<br> monopoly, and thus maintain the user's freedom of choice. (See also<br> the German translation below.)<br> </blockquote> <br> Yes, most of AG MFT are on this track, therefore our work is mainly towards cooperation!<br> <br> But I am currently more describing the position of the "Prototype Core Team" (PCT), that is part of the working group AG MFT.<br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Alex said:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I'm ALL IN on (1), and I think that's what the "Ontology" is all<br> about. Its a way to map one plattform onto another, ... where<br> plattform is called a plugin when it comes to AG<br> Meinungsfindungstool. But as mentioned in discussions way earlier,<br> these plugins do not necessarily plug into something, but instead<br> into each other, ...which means a plugin is just a plattform that<br> uses ontologies for "Vote mirroring" :-)<br> </blockquote></blockquote> <br> That is also my understanding.<br> <br> The PCT don't want to encourage one special implementation. Instead we want to enable all participating implementations to collaborate. Indeed this needs an agreement on a common understanding of "something".<br> <br> I would like to refer to this little "something" as the Common Discussion Standard (CDS). We want to describe the CDS with the help of an Ontologie to picture the "data" part and a Web API to cover the possible "workflows".<br> <br> Finally the CDS is what enables plug-ins to plug into each other.<br></blockquote><div><br></div><div style>[alex]<br>Sounds great.<br>It would also be cool to have a very detailed prototype as a proof of concept implementation.<br> A tool that people could actually use and other programmers could look at the source in order to understand how to implement the CDS<br>[/alex]</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Yes, it could be. Let's see if the AGM engineers agree about (1) in<br> regard to all platforms, including non-AGM platforms such as Votorola.<br> Unfortunately they're confronted with a language barrier owing to my<br> lack of German. Here's a Google translation:<br> [snipped]<br> I hope that makes sense. If not, please correct the translation<br> errors. Here's the original English:<br> </blockquote> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> It's often difficult for competitors to understand each other. But we<br> must be clear on this issue. A platform cannot succeed without users.<br> There are two ways to obtain those users:<br> (1) Eliminate the network effects between platforms, thus levelling<br> the playing field and enabling the users to range freely from<br> platform to platform.<br> </blockquote> <br> That's what I think we would like to achieve. Even if there is no chance to eleminate the networking effects between individuals, the PCT focus more on the interchangeability of individual implementations.<br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> This is the right way.<br> </blockquote> <br> To be honest, I don't know if this is the right way. But it's the only one I am aware of right now ;o)<br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Let's wait for the answer, as cooperation necessarily depends on it.<br> </blockquote> <br> I think most of the members of our working group AG MFT are towards (1).<br> <br> At least the Prototype Core Team fully agrees. So far our solution is not to build yet another discussion/voting/<u></u>collaboration/networking tool, but to define an environment where tools can plug in and share data and extend workflows. The working title for this is "d!sco" (Discussion Ontology) Framework.<br> <br> The PCT don't care much about distinct methodologies of discussion/voting/<u></u>collaboration/networking as far as they don't influence or concern the overall process of decision-making. The idea is to achieve an agreement between all participants on the Common Discussion Standard. This standard consists of an ontology and a web api to enable communication between all implementations.<br> <br> <br> Our goal is to enable cooperation by defining a standard. This is how the internet succeeds. Defining a standard that everyone can implement to gain benefit from it. The main benefit of CDS is to obtain users and to preserve data.<br> <br> <br> Does this make sense?<br> <br> Cheers<span class="HOEnZb"><font color="#888888"><br> Marc <br> ______________________________<u></u>_________________<br> Votorola mailing list<br> <a href="mailto:Votorola@zelea.com" target="_blank">Votorola@zelea.com</a><br> <a href="http://mail.zelea.com/mailman/listinfo/votorola" target="_blank">http://mail.zelea.com/mailman/<u></u>listinfo/votorola</a><br> </font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div style="color:rgb(34,34,34);font-family:arial,sans-serif"><br>Best Regards / Mit freundlichen Grüßen</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif"> ***********************************************</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">Alexander Praetorius</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">Rappstraße 13</div> <div style="color:rgb(34,34,34);font-family:arial,sans-serif">D - 60318 Frankfurt am Main</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">Germany</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif"> <b>[skype] </b>alexander.praetorius</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif"><b>[mail] </b><a href="mailto:alexander.praetorius@serapath.de" target="_blank">citizen@serapath.de</a></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif"> <b>[web] </b><a href="http://wiki.piratenpartei.de/Benutzer:Serapath" target="_blank">http://wiki.piratenpartei.de/Benutzer:Serapath</a> </div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">***********************************************</div> </div> </div></div>