Differences From
Artifact [0535a222ee]:
1160 1160 there's currently no standard way to describe the intent and desired formatting of a document besides placing pragmata in the source file itself. this is extremely suboptimal, as when generating collections of documents, it's ideal to be able to keep all formatting information in one place. users should also be able to specify their own styling overrides that describe the way they prefer to read [`cortav] files, especially for uses like gemini or gopher integration.
1161 1161
1162 1162 at some point soon [`cortav] needs to address this by adding intent files that can be activated from outside the source file, such as with a command line flag or a configuration file setting. these will probably consist of lines that are interpreted as pragmata. in addition to the standard intent format however, individual implementations should feel free to provide their own ways to provide intent metadata; e.g. the reference implementation, which has a lua interpreter available, should be able to take a lua script that runs after the parse stage and makes arbitrary alterations to the AST. this will be particularly useful for the end-user who wishes to specify a particular format she likes reading her files in without forcing that format on everyone she sends the compiled document to, as it will be able to interrogate the document and make intelligent decisions about what pragmata to apply.
1163 1163
1164 1164 intent files should also be able to define [>rsrc resources], [>ctxvar context variables], and macros.
1165 1165
1166 1166 ## implementation license
1167 -the cortav reference implementation is made available under the terms of the European Union Public License v1.2. the binding license text may be found in the [`cortav] source control tree at the following paths:
1167 +the cortav reference implementation is made available under the terms of the GNU Affero General Public License v3. the binding license text may be found in the [`cortav] source control tree at the following paths:
1168 1168 + language + license text location
1169 -| english | [`legal/eupl.en]
1170 -| german | [`legal/eupl.de]
1169 +| english | [`legal/agpl.en]
1171 1170 [*should the texts be interpreted to conflict in translation, the most restrictive subset of terms shall apply.]
1172 1171
1173 1172 # trademarks
1174 1173 the name "cortav" is a trademark of alexis hale, and may be used only insofar as the following terms apply:
1175 1174 : the name "cortav" is applied to an implementation of the cortav language that strictly conforms to at least [>levels level 1] of this specification
1176 1175 : the name is not used unqualified; i.e. no project may name itself simply "cortav". below are some examples of permissible names under this term:
1177 1176 :: cortav-scheme
1178 1177 :: cortav.c
1179 1178 :: pycortav
1180 1179 this grant may be revoked at any time, for any reason, by the trademark owner. if you wish to use the name "cortav" in contravention of this grant or simply require stronger legal guarantees, feel free to contact me and we can probably work something out as long as you're not some corporate asshole.