<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi - let me contribute the coordinator's personal view on this
discussion - following up what John Pereira said, yesterday:<br>
<br>
1) The IKS community back in May 2009, identified "semantic editing" as
a major theme for CMS<br>
2) Aloha is one (of the first) of probably a bunch of emerging HTML5/JS
based novel editing tools<br>
<br>
Note at this point that "novel editing tool" IS-NOT-EQUAL "semantic
editor"!<br>
Aloha does a number of smart EDITING, but it has at present, little
support for any "knowledge objects".<br>
The mutual interest is in combining Aloha-style "novel/smart editing"
with IKS-style "knowledge-aware" computing.<br>
<br>
3) I would expect the IKS semantic editor develepment group to come up
with specs and a prototype implementation (perhaps based on Aloha) that
shows how I can easily enrich the text about an upcoming music event
with "knowledge" (machine readable semantics!) about where it will
happen, who will be on stage, how to get there and all sorts of
background information (e.g. what music equipment the keyboarder uses
on the song "Semantic Sunrise".) ;-)<br>
<br>
4) While I appreciate the open discussion about Aloha's licensing
scheme (we are all learning from the exchange and the emerging
collective experience, here) I would like to point out that IKS'
contribution should be in defining an OPEN knowledge-level API for any
semantic editor, Aloha being the first one that has dared to come
forward as a candidate implementation.<br>
<br>
I guess Henri expressed something similar when he said he is not too
worried at present. One thing should remain clear: IKS funded
development is BSD/Apache based as defined in our legal framework. We
should perhaps give the Gentics people a little more time to consider
their licensing options, but everybody could in the meantime,
contribute to developing a "knowledge aware" API for semantic editors,
starting with reqs and specs. I would like to see the Helsinki
Hackathon to go ahead in that spirit, irrespective of the licensing
question.<br>
<br>
Please let me know if my position is too liberal or flawed in any other
way.<br>
<br>
Best regards,<br>
<br>
Wernher<br>
<br>
<br>
Stéphane Croisier wrote the following on 20.07.10 22:41:
<blockquote
cite="mid:AANLkTin3--xLr2FvpW7Sw5NoaDtB8wgKP5v6ygaqGSj3@mail.gmail.com"
type="cite"><br>
<div class="gmail_quote">On Tue, Jul 20, 2010 at 1:26 PM, Henri
Bergius <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:henri.bergius@nemein.com">henri.bergius@nemein.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Of course, the question with both licensing and copyright assignments<br>
is also on where the border between "Aloha core" that requires<br>
copyright-assigned AGPL, and plugins that can be made by anybody is<br>
drawn. If everything that IKS would do in context of the semantic<br>
editor can happen in plugin space and be more liberally licensed, then<br>
I don't see a problem.<br>
</blockquote>
<div><br>
... But the AGPL will see some.<br>
<br>
As far as I understand this thread, it looks like it is still unclear
if Gentics wants to adopt a dual-licensing or an Open Core approach (or
a pure community-driven approach).<br>
<br>
I agree with you Henri. If Aloha is built from a very modular manner,
it could be great to create a marketplace of "aloha modules" which
could be available under various open source or proprietary licenses. <br>
<br>
Then Aloha would rather follow an OpenCore paradigm by providing the
core under a very permissive license to rapidly gain a certain traction
and a momentum in the industry and Gentics (or others) could resell
dual-licensed modules/add-ons (or even fully proprietary ones if they
prefer) on top of this core.<br>
<br>
This would make sense as basic WYSIWYG editing capabilities are already
a commodity. And some "extensions" (e.g. some grammatical checkers) are
only availabe under more proprietary licenses. So I do not see a lot
of added values to purchase some basic editing capabilities and I would
prefer to rely on a strong community of developers to ensure the proper
level of stability/testing/bug fixing for such a core. But I do see
some real potentials to buy certain advanced "plug-ins" on a per
customer need basis.<br>
<br>
However:<br>
1) The OpenCore business model is also subject to a lot of criticism.
Precisely defining the boundaries between what belongs to the core and
what belongs to the modules is not an easy tasks. Conflict of interests
between the community and the vendor(s) may rapidly happen. (cf: some
cross-refs mentionned here: <a moz-do-not-send="true"
href="http://stephanecroisier.jahia.com/future-of-open-source-cms">http://stephanecroisier.jahia.com/future-of-open-source-cms</a>
)<br>
2) Dependencies on ExtJS could be a real problem. It looks like ExtJS
considers that the viral effect of the GPL also impacts the underlying
server-side applications. This means that, if you want to integrate
Aloha as part of a proprietary CMS (or another dual-licensed CMS), you
would not only have to acquire a Gentics OEM license but also a ExtJS
one (now I am not a lawyer, so one has to legally check all these
constraints)<br>
<br>
So no ideal solution. Enforcing a real quid pro quo paradigm is not
possible with OSI licenses. I already wrote an article on this subject
back in 2004 (p.20 - <a moz-do-not-send="true"
href="http://www.methodsandtools.com/PDF/mt200402.pdf">http://www.methodsandtools.com/PDF/mt200402.pdf</a>
).<br>
<br>
But an OpenCore approach with a truly permissive core (BSD/ASL) would
be perhaps the best manner to satisfy all the parties. Not sure however
it is possible to do with dependencies on ExtJS.<br>
<br>
Cheers,<br>
Stéphane<br>
<br>
</div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">/Henri<br>
<br>
</blockquote>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
iks-community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:iks-community@iks-project.eu">iks-community@iks-project.eu</a>
<a class="moz-txt-link-freetext" href="http://lists.iks-project.eu/cgi-bin/mailman/listinfo/iks-community">http://lists.iks-project.eu/cgi-bin/mailman/listinfo/iks-community</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Wernher Behrendt
Salzburg Research Forschungsgesellschaft
Knowledge and Media Technologies Group
Jakob-Haringer Strasse 5/II
5020 Salzburg
Austria
email <a class="moz-txt-link-abbreviated" href="mailto:wernher.behrendt@salzburgresearch.at">wernher.behrendt@salzburgresearch.at</a>
phone +43 (0)662 2288 409
fax +43 (0)662 2288 222
<a class="moz-txt-link-freetext" href="http://www.salzburgresearch.at">http://www.salzburgresearch.at</a>
<a class="moz-txt-link-freetext" href="http://www.iks-project.eu">http://www.iks-project.eu</a>
Bringing Semantic Technologies to Content Management</pre>
</body>
</html>