Re: What is the best license to use for open source software?

["G.B." <bauhaus@futureapps.invalid>]

On 29.01.15 09:50, Dmitry A. Kazakov wrote:
> On Wed, 28 Jan 2015 23:03:24 -0800 (PST), Vadim Godunko wrote:
>
>> On Tuesday, January 27, 2015 at 11:52:28 AM UTC+3, Dmitry A. Kazakov wrote:
>>>
>>> One basic issue more, should the template paradigm be:
>>>
>>> A. Substitution-based (some escape sequences in the text);
>>> B. Language-based;
>>> C. Programmable (some API to manipulate the template, plus intermediate
>>> embeddable code, plus GUI editor).
>>>
>> Matreshka includes templates engine that uses XML format for templates and
>> handles substitutions and conditional processing. Generated output can be
>> XML or optimized HTML (when template uses HTML namespace). See
>>
>> http://forge.ada-ru.org/matreshka/wiki/XML/Templates
>>
>> Source template not necessary should be file: it can be any stream of
>> stream elements or sequence of 'markup events' - elements of internal
>> representation of XML document.
>
> That would be A,

Microsoft Word files are A (XML), too. The tool does not
determine the representation.

> while I prefer C. E.g. instead of XML:
>
>     <mtl:if expression="boolean_expression">
>       ...
>     </mtl:if>

The template language need not be XML even when the
template documents are XML.

Also, using XML Processing Instructions (PIs), you could
be specifically using XML and avoid another XML namespace
plus more node names:

  <?gnoga-template-parser  if boolean_expression then ?>
    <div class="visible-instrument">
      ...
    </div>
  <?gnoga-template-parser end if ?>

boolean_expression can very well use Ada syntax, as it
is the job of the XML processor to take care of PIs!

We sometimes use a template language that lets us choose
indicators flexibly, which can mean HTML comments,
and in no way do we need to use namespaces, to get

   <!--[* IF boolean_expression *]-->
     ...
   <!--[* END *]-->

where we chose "<!--[*" and "*]-->" as the indicators.
The templates stay valid XML (XHTML, i.e.) in those
cases. In other cases, we switch indicators so that we can
put things in attribute values.

Design tools might require that JSP syntax or ASP syntax
be understood.