summaryrefslogtreecommitdiff
path: root/macros/latex/contrib/proposal/eu
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
committerNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
commite0c6872cf40896c7be36b11dcc744620f10adf1d (patch)
tree60335e10d2f4354b0674ec22d7b53f0f8abee672 /macros/latex/contrib/proposal/eu
Initial commit
Diffstat (limited to 'macros/latex/contrib/proposal/eu')
-rw-r--r--macros/latex/contrib/proposal/eu/README14
-rw-r--r--macros/latex/contrib/proposal/eu/euproposal.dtx601
-rw-r--r--macros/latex/contrib/proposal/eu/euproposal.ins37
-rw-r--r--macros/latex/contrib/proposal/eu/euproposal.pdfbin0 -> 273933 bytes
-rw-r--r--macros/latex/contrib/proposal/eu/strep/Makefile77
-rw-r--r--macros/latex/contrib/proposal/eu/strep/README14
-rw-r--r--macros/latex/contrib/proposal/eu/strep/deliverables.tex34
-rw-r--r--macros/latex/contrib/proposal/eu/strep/draft.tex1
-rw-r--r--macros/latex/contrib/proposal/eu/strep/final.tex7
-rw-r--r--macros/latex/contrib/proposal/eu/strep/grantagreement.tex7
-rw-r--r--macros/latex/contrib/proposal/eu/strep/impact.tex40
-rw-r--r--macros/latex/contrib/proposal/eu/strep/implementation.tex103
-rw-r--r--macros/latex/contrib/proposal/eu/strep/issues.tex59
-rw-r--r--macros/latex/contrib/proposal/eu/strep/methodology.tex49
-rw-r--r--macros/latex/contrib/proposal/eu/strep/milestones.tex40
-rw-r--r--macros/latex/contrib/proposal/eu/strep/objectives.tex13
-rw-r--r--macros/latex/contrib/proposal/eu/strep/progress.tex11
-rw-r--r--macros/latex/contrib/proposal/eu/strep/propB.pdfbin0 -> 220999 bytes
-rw-r--r--macros/latex/contrib/proposal/eu/strep/propB.tex65
-rw-r--r--macros/latex/contrib/proposal/eu/strep/public.pdfbin0 -> 109019 bytes
-rw-r--r--macros/latex/contrib/proposal/eu/strep/public.tex7
-rw-r--r--macros/latex/contrib/proposal/eu/strep/quality.tex14
-rw-r--r--macros/latex/contrib/proposal/eu/strep/risks.tex17
-rw-r--r--macros/latex/contrib/proposal/eu/strep/site-bar.tex19
-rw-r--r--macros/latex/contrib/proposal/eu/strep/site-baz.tex13
-rw-r--r--macros/latex/contrib/proposal/eu/strep/site-efo.tex14
-rw-r--r--macros/latex/contrib/proposal/eu/strep/site-jacu.tex53
-rw-r--r--macros/latex/contrib/proposal/eu/strep/site-templatex.tex40
-rw-r--r--macros/latex/contrib/proposal/eu/strep/submit.pdfbin0 -> 97709 bytes
-rw-r--r--macros/latex/contrib/proposal/eu/strep/submit.tex7
-rw-r--r--macros/latex/contrib/proposal/eu/strep/workplan.tex19
-rw-r--r--macros/latex/contrib/proposal/eu/strep/wp-class.tex44
-rw-r--r--macros/latex/contrib/proposal/eu/strep/wp-dissem.tex62
-rw-r--r--macros/latex/contrib/proposal/eu/strep/wp-management.tex61
-rw-r--r--macros/latex/contrib/proposal/eu/strep/wp-temple.tex44
35 files changed, 1586 insertions, 0 deletions
diff --git a/macros/latex/contrib/proposal/eu/README b/macros/latex/contrib/proposal/eu/README
new file mode 100644
index 0000000000..5f055101d0
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/README
@@ -0,0 +1,14 @@
+euproposal.cls: A class for preparing FP7 proposals for collaborative projects
+
+The euproposal class supports many of the specific elements of a Framework 7 Proposal. It
+is optimized towards collaborative projects. The package comes with extensive examples. To
+start a new proposal just copy a suitable one and modify it to your needs. Note that the
+structure of EU proposals changes from time to time, so that the examples may be out of
+date.
+
+Copyright(c) 2007 Michael Kohlhase
+The package is distributed under the terms of the LaTeX Project Public License (LPPL)
+
+The development version of this package can be found at
+https://svn.kwarc.info/repos/kwarc/doc/macros/forCTAN/proposal/eu
+
diff --git a/macros/latex/contrib/proposal/eu/euproposal.dtx b/macros/latex/contrib/proposal/eu/euproposal.dtx
new file mode 100644
index 0000000000..d9b2e3884a
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/euproposal.dtx
@@ -0,0 +1,601 @@
+% \iffalse meta-comment
+% A class for preparing FP7 proposals for collaborative projects
+%
+% Copyright (c) 2011 Michael Kohlhase, all rights reserved
+%
+% This file is distributed under the terms of the LaTeX Project Public
+% License from CTAN archives in directory macros/latex/base/lppl.txt.
+% Either version 1.0 or, at your option, any later version.
+%
+% The development version of this file can be found at
+% https://github.com/KWARC/LaTeX-proposal
+% \fi
+%
+% \iffalse
+%<cls|pdata|reporting>\NeedsTeXFormat{LaTeX2e}[1999/12/01]
+%<cls>\ProvidesClass{euproposal}[2016/04/15 v1.5 EU Proposal]
+%<pdata>\ProvidesPackage{eupdata}[2016/04/15 v1.5 EU Project Data]
+%<reporting>\ProvidesPackage{eureporting}[2016/04/15 v1.5 EU Project Reporting]
+%<*driver>
+\documentclass[twoside]{ltxdoc}
+\DoNotIndex{\def,\long,\edef,\xdef,\gdef,\let,\global}
+\DoNotIndex{\begin,\AtEndDocument,\newcommand,\newcounter,\stepcounter}
+\DoNotIndex{\immediate,\openout,\closeout,\message,\typeout}
+\DoNotIndex{\section,\scshape,\arabic}
+\EnableCrossrefs
+%\CodelineIndex
+%\OnlyDescription
+\RecordChanges
+\usepackage{textcomp,url,paralist,a4wide,xspace}
+\usepackage[show]{ed}
+\usepackage[maxnames=6,hyperref=auto,style=alphabetic,backend=bibtex]{biblatex}
+\addbibresource{../lib/proposal.bib}
+\usepackage[bookmarks=true,linkcolor=blue,
+ citecolor=blue,urlcolor=blue,colorlinks=true,
+ breaklinks=true, bookmarksopen=true]{hyperref}
+\makeindex
+\newcommand\subversion{\textsc{Subversion}\xspace}
+\begin{document}
+\DocInput{euproposal.dtx}
+\end{document}
+%</driver>
+% \fi
+%
+%\CheckSum{639}
+%
+% \changes{v0.1}{2007/05/07}{used in the SciML proposal}
+% \changes{v0.2}{2007/05/09}{First Version with Documentation}
+% \changes{v0.3}{2007/06/04}{staff effort table finally works, released}
+% \changes{v0.3a}{2008/01/18}{error corrections and more documentation}
+% \changes{v1.3}{2011/05/18}{basing this on proposal.cls}
+% \changes{v1.4}{2012/01/18}{various tweaks for the Jan 2012 proposal deadline}
+% \changes{v1.4}{2015/01/14}{lots of tweaks}
+%
+% \GetFileInfo{euproposal.cls}
+%
+% \MakeShortVerb{\|}
+% \title{Preparing FP7 EU Proposals and Reports in {\LaTeX} with \texttt{euproposal.cls}}
+% \author{Michael Kohlhase\\
+% Computer Science, Jacobs University Bremen\\
+% \url{http://kwarc.info/kohlhase}}
+% \maketitle
+%
+% \begin{abstract}
+% The |euproposal| class supports many of the specific elements of a Framework 7
+% Proposal. It is optimized towards collaborative projects. The package comes with an
+% extensive example (a fake EU proposal) that shows all elements in action.
+% \end{abstract}
+%
+% \tableofcontents\newpage
+%
+% \section{Introduction}\label{sec:intro}
+%
+% Writing grant proposals is a collaborative effort that requires the integration of
+% contributions from many individuals. The use of an ASCII-based format like {\LaTeX}
+% allows to coordinate the process via a source code control system like
+% \subversion, allowing the proposal writing team to concentrate on the contents
+% rather than the mechanics of wrangling with text fragments and revisions.
+%
+% The |euproposal| class extends the |proposal| class~\cite{Kohlhase:pplp:svn} and
+% supports many of the specific elements of Part B of a Framework 7 Proposal. The
+% package documentation is still preliminary, fragmented and incomplete and only dwells
+% on the particulars of DFG proposals, so we treat~\cite{Kohlhase:pplp:svn} as a
+% prerequisite. Please consult the example proposal |propB.tex|, which comes with the
+% package and shows the usage of the class in action. It is intended as a template for
+% your proposal, but please bear in mind that the EU guidelines may change from call to
+% call, if in doubt, please consult the FP7 guide for proposers.\ednote{say something
+% about the proposers guide.}
+%
+% The |eureporting| class supports most of the specific elements of the project reports
+% to the EC. The example report |dfg/report.tex| is intended as a template for your
+% final report\ednote{say something about reporting}.
+%
+% The |euproposal| and |eureporting| classes and the |eupdata| package are distributed
+% under the terms of the LaTeX Project Public License from CTAN archives in directory
+% macros/latex/base/lppl.txt. Either version 1.0 or, at your option, any later
+% version. The CTAN archive always contains the latest stable version, the development
+% version can be found at \url{https://github.com/KWARC/LaTeX-proposal}. For bug reports
+% please use the sTeX TRAC at \url{https://github.com/KWARC/LaTeX-proposal/issues}.
+%
+% \section{The User Interface}\label{sec:user-interface}
+%
+% In this section we will describe the functionality offered by the |euproposal| class
+% along the lines of the macros and environments the class provides. Much of the
+% functionality can better be understood by studying the functional example |proposal.tex|
+% (and its dependents) that comes with the |euproposal| package in conjunction with the
+% proposer's EU proposer's guidelines (we have included it as |***| for convenience into
+% the package distribution).\ednote{MK@MK do that and talk about reporting as well.}
+%
+% \subsection{Package Options}\label{sec:user:options}
+%
+% As usual in {\LaTeX}, the package is loaded by
+% |\documentclass[|\meta{options}|]{euproposal}|, where |[|\meta{options}|]| is optional
+% and gives a comma separated list of options specified in~\cite{Kohlhase:pplp:svn}. Some
+% versions EU proposals want non-standard numbering schemes (e.g. starting with
+% \textbf{B...} since we are writing Part B.), this can be reached by giving the |propB|
+% option.
+%
+% \subsection{Proposal Metadata and Title page}\label{sec:user:metadata}
+%
+% The metadata of the proposal is specified in the \DescribeEnv{proposal}|proposal|
+% environment, which also generates the title page and the first section of the proposal
+% as well as the last pages of the proposal with the signatures, enclosures, and
+% references. The |proposal| environment should contain all the mandatory parts of the
+% proposal text. The |proposal| environment uses the following EU-specific keys to
+% specify metadata.
+% \begin{compactitem}
+% \item \DescribeMacro{callname}|callname| specifies the call the proposal addresses. It is
+% usually a string of the form |ICT Call 1|, \DescribeMacro{callid}|callid| is the
+% corresponding identifier, usually a string of the form |FP7-???-200?-?|. An overview
+% over open calls can be found at \url{http://cordis.europa.eu/fp7/dc/index.cfm}
+% \item The \DescribeMacro{challenge}|challenge|, \DescribeMacro{objective}|objective|,
+% and \DescribeMacro{outcome}|outcome| keys specifies the specific parts in the call
+% this proposal addresses. These are specified in the ``call fiche'' that can be
+% obtained from the URL above. All of these have an identifier, which can be specified
+% via the \DescribeMacro{challengeid}|challengeid|,
+% \DescribeMacro{objectiveid}|objectiveid|, and \DescribeMacro{outcomeid}|outcomeid|
+% keys.\ednote{MK@MK: the outcomeid should key should be a list key, I am not
+% implementing this right now, since it comes more natural when we change the class to
+% metakeys support.}
+% \item \DescribeMacro{topicsaddressed}|topicsaddressed| allows to enter free-form text
+% instead of specifying the |challenge*|, |objective*|, and |outcome*| keys.
+% \item The \DescribeMacro{coordinator}|coordinator| key gives the identifier of the
+% proposal coordinator. The |euproposal| package uses the |workaddress| package for
+% representation of personal metadata, see~\cite{Kohlhase:workaddress:ctan} for details.
+% \item The \DescribeMacro{coordinatorsite}|coordinatorsite| key gives the identifier of
+% the coordinating site (for the table).
+% \item If given, the \DescribeMacro{iconrowheight}|iconrowheight| key instructs the
+% |euproposal| class to make a line with the logos of the participants at the bottom of
+% the title page, and specify their heights; |1.5cm| is often a good value.
+% \end{compactitem}
+%
+% \subsection{Work Packages and Work Areas}\label{sec:user:wpwa}
+%
+% \DescribeMacro{type} The |type| key specifies the activity type of the work package:
+% |RTD| = Research and technological development (including any activities to prepare for
+% the dissemination and/or exploitation of project results, and coordination activities);
+% |DEM| = Demonstration; |MGT| = Management of the consortium; |OTHER| = Other specific
+% activities, if applicable in this call.
+%
+% \subsection{Milestones and Deliverables}\label{sec:user:deliverables}
+%
+% |euproposal.cls| adds the \DescribeMacro{verif}|verif| key to \DescribeMacro{\milestone}
+% for specifying a means of verification that the milestone has been successful.
+%
+% With this, we can generate the milestone table that is required in many EU
+% proposals. This can simply be done via the
+% \DescribeMacro{\milestonetable}|\milestonetable| macro. It takes a keyword argument with
+% the keys \DescribeMacro{caption}|caption| for specifying a different caption, and the
+% widths \DescribeMacro{wname}|wname|, \DescribeMacro{wdeliv}|wdeliv|, and
+% \DescribeMacro{wverif}|wverif| that can be used to specify different widths for the
+% name/deliverables/verification columns in the milestone table.
+%
+% \subsection{Risks}\label{sec:user:risks}
+% In some EU proposals (e.g. FET), we need to identify risks and contingency and specify
+% mitigation plans for them. In the |euproposal| we use two environments to mark them up.
+%
+% \DescribeMacro{risk}|\begin{risk}{|\meta{title}|}{|\meta{prob}|}{|\meta{grav}|}|\ldots|\end{risk}|
+% makes a paragraph no a risk \meta{title} with gravity \meta{grav} and probability
+% \meta{prob}, where the body of the environment contains a description of the risk. The
+% \DescribeMacro{riskcont}|riskcont| is a variant, where \meta{title} names a risk and the
+% body is a description of the contingency plan.
+%
+% \begin{newpart}{MK@MK: This is new, and only partially implemented}
+% \subsection{Reporting Infrastructure}\label{sec:user:report}
+%
+% The |eureporting| class gives an infrastructure for writing final reports of completed
+% projects (see the file |finalreport.tex| in the package distribution). The
+% \DescribeEnv{report}|report| environment has functionality analogous to the |proposal|
+% environment. It takes the same metadata keys --- making it easy to generate by
+% copy/paste from the proposal --- but adds the keys \DescribeMacro{key}|key| can be used
+% to specify the reference key (something like \texttt{KO 2428 47-11}) given to the
+% project by EU. Note that in the case of multiple proposers, you can use multiple
+% instances of |key| to specify more than one reference key.
+% \end{newpart}
+%
+% \section{Limitations and Enhancements}\label{sec:limitations}
+%
+% The |euproposal| is relatively early in its development, and many enhancements are
+% conceivable. We will list them here.
+% \begin{enumerate}
+% \item none reported yet.
+% \end{enumerate}
+% If you have other enhancements to propose or feel you can alleviate some limitation,
+% please feel free to contact the author.
+%
+% \StopEventually{\newpage\PrintIndex\newpage\PrintChanges\newpage\printbibliography}\newpage
+%
+% \section{The Implementation}\label{sec:implementation}
+%
+% In this section we describe the implementation of the functionality of the |euproposal|
+% and |eureporting| classes and the |eupdata| package.
+%
+% \subsection{Package Options and Format Initialization}\label{sec:impl:options}
+%
+% We first set up the options for the package.
+%
+% \begin{macrocode}
+%<*cls>
+\newif\ifpartB\partBfalse
+\DeclareOption{partB}{\partBtrue}
+\DeclareOption*{\PassOptionsToClass{\CurrentOption}{proposal}}
+%</cls>
+%<reporting>\DeclareOption*{\PassOptionsToClass{\CurrentOption}{reporting}}
+%<cls|reporting>\ProcessOptions
+% \end{macrocode}
+%
+% Then we load the packages we make use of
+%
+% \begin{macrocode}
+%<cls>\ifpartB\LoadClass[report,noRAM]{proposal}\else\LoadClass[noRAM]{proposal}\fi
+%<reporting>\LoadClass[report,noRAM]{reporting}
+%<*cls|reporting>
+\RequirePackage{longtable}
+\RequirePackage{eurosym}
+\RequirePackage{wrapfig}
+\RequirePackage{eupdata}
+% \end{macrocode}
+% we want to change the numbering of figures and tables
+% \begin{macrocode}
+\RequirePackage{chngcntr}
+\counterwithin{figure}{subsection}
+\counterwithin{table}{subsection}
+%</cls|reporting>
+% \end{macrocode}
+%
+% \subsection{Proposal Metadata and Title Page}\label{sec:impl:metadata}
+%
+% We extend the metadata keys from the |proposal| class.
+% \begin{macrocode}
+%<*pdata>
+\define@key{prop@gen}{coordinator}{\def\prop@gen@coordinator{#1}\pdata@def{prop}{gen}{coordinator}{#1}}
+\define@key{prop@gen}{coordinatorsite}{\def\prop@gen@coordinatorsite{#1}\pdata@def{prop}{gen}{coordinator}{#1}}
+\def\prop@gen@challenge{??}\def\prop@gen@challengeid{??}
+\define@key{prop@gen}{challenge}{\def\prop@gen@challenge{#1}\pdata@def{prop}{gen}{challenge}{#1}}
+\define@key{prop@gen}{challengeid}{\def\prop@gen@challengeid{#1}\pdata@def{prop}{gen}{challengeid}{#1}}
+\def\prop@gen@objective{??}\def\prop@gen@objectiveid{??}
+\define@key{prop@gen}{objective}{\def\prop@gen@objective{#1}\pdata@def{prop}{gen}{objective}{#1}}
+\define@key{prop@gen}{objectiveid}{\def\prop@gen@objectiveid{#1}\pdata@def{prop}{gen}{objectiveid}{#1}}
+\def\prop@gen@outcome{??}\def\prop@gen@outcomeid{??}
+\define@key{prop@gen}{outcome}{\def\prop@gen@outcome{#1}\pdata@def{prop}{gen}{outcome}{#1}}
+\define@key{prop@gen}{outcomeid}{\def\prop@gen@outcomeid{#1}\pdata@def{prop}{gen}{outcomeid}{#1}}
+\define@key{prop@gen}{callname}{\def\prop@gen@call{#1}\pdata@def{prop}{gen}{callname}{#1}}
+\define@key{prop@gen}{callid}{\def\prop@gen@call{#1}\pdata@def{prop}{gen}{callid}{#1}}
+\define@key{prop@gen}{iconrowheight}{\def\prop@gen@iconrowheight{#1}}
+\define@key{prop@gen}{topicsaddressed}{\def\prop@gen@topicsaddressed{#1}}
+%</pdata>
+% \end{macrocode}
+%
+% and now the ones for the final report
+% \begin{macrocode}
+%<*reporting>
+\define@key{prop@gen}{reportperiod}{\def\prop@gen@reportperiod{#1}}
+\define@key{prop@gen}{key}{\@dmp{key=#1}%
+\@ifundefined{prop@gen@keys}{\xdef\prop@gen@keys{#1}}{\xdef\prop@gen@keys{\prop@gen@keys,#1}}}
+\define@key{prop@gen}{projpapers}{\def\prop@gen@projpapers{#1}}
+%</reporting>
+% \end{macrocode}
+%
+% and the default values, these will be used, if the author does not specify something
+% better.
+%
+% If the |propB| option is given, we need to redefine some of the internal counters and
+% table of contents mechanisms to adapt to the fact that the proposal text is just Part B.
+%
+% \begin{macrocode}
+%<*cls>
+\ifpartB
+\def\thepart{\Alph{part}}
+\setcounter{part}{2}
+\def\thechapter{\thepart.\arabic{chapter}}
+\def\numberline#1{\hb@xt@\@tempdima{#1\hfil} }
+\fi
+% \end{macrocode}
+%
+% \begin{macro}{\prop@sites@table}
+% \begin{macrocode}
+\newcommand\prop@sites@table{\def\@@table{}
+{\let\tabularnewline\relax\let\hline\relax
+\@for\@I:=\prop@gen@sites\do{\xdef\@@table{\@@table\pdataref{site}\@I{number}}
+\xdef\@@table{\@@table&\@nameuse{wa@institution@\@I @name}
+\ifx\@I\prop@gen@coordinatorsite (coordinator)\fi}
+\xdef\@@table{\@@table&\@nameuse{wa@institution@\@I @acronym}}
+\xdef\@@table{\@@table&\@nameuse{wa@institution@\@I @countryshort}\tabularnewline\hline}}}
+\begin{tabular}{|l|p{8cm}|l|l|}\hline%|
+\# & Participant organisation name & Short name & Country\\\hline\hline
+\@@table
+\end{tabular}}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{environment}{prop@proposal}
+% \begin{macrocode}
+\renewenvironment{prop@proposal}
+{\ifgrantagreement\else
+ \thispagestyle{empty}\begin{center}
+ {\Large \prop@gen@instrument}\\[.2cm]
+ {\Large\textbf\prop@gen@callname}\\[.4cm]
+ {\LARGE \prop@gen@callid}\\[.8cm]
+ {\huge\textbf\prop@gen@title}\\[.4cm]
+ {\LARGE Acronym: {\prop@gen@acronym}}\\[2cm]
+\end{center}
+%{\large\prop@gen@instrument}\\
+{\large\textbf{Date of Preparation: \today}}
+% \ifsubmit\else\if@svninfo\if@gitinfo\\
+% {\large\textbf{Revision}:
+% \if@svninfo\svnInfoRevision\fi\if@gitinfo\gitAbbrevHash\fi
+% of
+% \if@svninfo\svnInfoDate\fi\if@gitinfo\gitAuthorDate\fi}
+% \fi\fi\fi
+\\[1em]
+\begin{large}
+ \begin{description}
+ % \item[Work program topics addressed by \pn:]
+ % \@ifundefined{prop@gen@topicsaddressed}
+ % {\textbf{Challenge \prop@gen@challengeid}: \prop@gen@challenge,
+ % \textbf{Objective \prop@gen@objectiveid}: \prop@gen@objective,
+ % \textbf{target outcome \prop@gen@outcomeid}) \prop@gen@outcome.
+ % {\prop@gen@topicsaddressed}\\[1em]
+ \item[Coordinator:] \wa@ref{person}\prop@gen@coordinator{name}
+ \item[e-mail:] \wa@ref{person}\prop@gen@coordinator{email}
+ \item[tel/fax:] \wa@ref{person}\prop@gen@coordinator{worktelfax}
+ \@ifundefined{prop@gen@keywords}{}{\item[Keywords:] \prop@gen@keywords}
+ \end{description}
+\end{large}
+\vspace*{1em}
+\begin{center}
+\prop@sites@table\vfill
+\@ifundefined{prop@gen@iconrowheight}{}
+{\@for\@site:=\prop@gen@sites\do{\wa@institution@logo[height=\prop@gen@iconrowheight]\@site\qquad}}
+\end{center}
+\newpage
+\fi% ifgrantagreement
+\setcounter{tocdepth}{2}\setcounter{part}{2}}
+{\newpage\printbibliography[heading=warnpubs,maxnames=999]}
+% \end{macrocode}
+% \end{environment}
+%
+% \begin{macrocode}
+\def\prop@gen@instrument{Proposal Instrument (e.g. IP)}
+% \end{macrocode}
+%
+% \subsection{Site Descriptions}\label{sec:sitedesc}
+% \ednote {this functionality should probably be refactored into proposal.dtx}
+%
+% \begin{environment}{sitedescription}
+% \ednote{document this above} |\begin{sitedescritpion}[|\meta{opt}|]{\meta{site}}|
+% marks up the description for the site \meta{site}. It looks up the relevant metadata
+% from the respective |\WAinstitution| declarations. The options argument \meta{opt}
+% is a key-value list for the keys \DescribeMacro{logo}|logo| (add the logo from
+% |\WAinstitution| to the site description), \DescribeMacro{width}|width|,
+% \DescribeMacro{height}|height| (intended dimensions of the logo), \ednote{more?}.
+% \begin{macrocode}
+\define@key{site@desc}{box}[true]{\def\site@desc@box{#1}%
+\pdata@def{sitedesc}{\@site}{box}{#1}}
+\define@key{site@desc}{logo}[true]{\def\site@desc@logo{#1}%
+\pdata@def{sitedesc}{\@site}{logo}{#1}}
+\define@key{site@desc}{width}{\def\site@desc@width{#1}%
+\pdata@def{sitedesc}{\@site}{width}{#1}\@dmp{wd=#1}}
+\define@key{site@desc}{height}{\def\site@desc@height{#1}%
+\pdata@def{sitedesc}{\@site}{height}{#1}\@dmp{ht=#1}}
+\newenvironment{sitedescription}[2][]%
+{\def\c@site{#2}% remember the site ID
+\newcounter{site@#2@PM} % for the site PM
+\def\site@desc@box{false}% not box unless requested
+\def\site@desc@logo{false}% not logo unless requested
+\def\site@desc@height{1.3cm}% default height
+\def\site@desc@width{5cm}% default width
+\setkeys{site@desc}{#1}% read the keys to overwrite the defaults
+\ifx\@site@desc@box\@true% if we want a logo
+\begin{wrapfigure}{r}{\site@desc@width}\vspace{-2.5ex}%
+\begin{tabular}{|p{\site@desc@width}|}\hline\vspace{1mm}%
+\ifx\@site@desc@logo\@true% if we want a logo
+\wa@institution@logo[height=\site@desc@width]{#2}\\[1ex]%
+\fi% end logo
+\textbf{\wa@ref{institution}{#2}{type}.\hfill \wa@ref{institution}{#2}{country}}\\%
+\small\wa@ref{institution}{#2}{streetaddress}, \wa@ref{institution}{#2}{townzip}\\\hline%
+\end{tabular}\vspace{-2.5ex}%
+\end{wrapfigure}%
+\fi% end box
+\pdata@target{site}{#2}%
+{\subsubsection{\wa@ref{institution}{#2}{acronym}: % space here
+{\textsc{\wa@ref{institution}{#2}{name}} (\wa@ref{institution}{#2}{countryshort})}}}%
+\small%
+\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
+ {0.25ex \@plus1ex \@minus.2ex}%
+ {-1em}%
+ {\normalfont\normalsize\bfseries}}}
+{\pdata@def{site}{\c@site}{reqPM}{\csname thesite@\c@site @PM\endcsname}}
+% \end{macrocode}
+% \end{environment}
+%
+% \begin{environment}{participant}
+% \ednote{document this above} |\begin{picv}[|\meta{PM}|]{\meta{name}}| marks up the CV
+% and metadata about a principal investigator of a site (it can only be use inside a
+% |sitedescription| environment). The first argument \meta{PM} specifies the
+% involvement in person months: a fair estimation this PI will spend on this specific
+% project over its whole duration.
+% \begin{macrocode}
+\define@key{site@part}{type}{\def\site@part@type{#1}\@dmp{type=#1}}
+\define@key{site@part}{PM}{\def\site@part@PM{#1}\@dmp{PM=#1}}
+\define@key{site@part}{salary}{\def\site@part@salary{#1}}%\@dmp{\euro=#1}}
+\define@key{site@part}{gender}{\def\site@part@gender{#1}}%\@dmp{\euro=#1}}
+\newenvironment{participant}[2][]%
+{\def\site@part@type{}\def\site@part@PM{}\def\site@part@salary{}\def\site@part@gender{}%
+\setkeys{site@part}{#1}%
+\ifx\site@part@PM\@empty\else\addtocounter{site@\c@site @PM}{\site@part@PM}\fi%
+\paragraph*{#2\ %
+(\ifx\site@part@type\@empty\else\site@part@type\fi%
+\ifx\site@part@gender\@empty\else, \site@part@gender\fi%
+\ifx\site@part@PM\@empty\else, \site@part@PM~PM\fi%
+)}%
+\ignorespaces}
+{\par\medskip}
+% \end{macrocode}
+% \end{environment}
+%
+% \subsection{Work Packages, Work Areas, and Deliverables}\label{sec::impl:wpwa}
+%
+% \begin{environment}{wp*}
+% \begin{macrocode}
+\newmdenv[frametitle=Objectives]{wpobjectives}
+\newmdenv[frametitle=Description]{wpdescription}
+% \end{macrocode}
+% \end{environment}
+%
+% \begin{environment}{workpackage}
+%
+% \begin{macrocode}
+\renewenvironment{workpackage}[1][]
+{\begin{work@package}[#1]\medskip\wpheadertable%
+\addcontentsline{toc}{subsubsection}{\wp@label\wp@num: \pdataref{wp}\wp@id{title}}}
+{\end{work@package}}
+% \end{macrocode}
+% \end{environment}
+%
+% \begin{macro}{\wpheadertable}
+% We redefine the macro that computes the default work package header table, since there
+% are more sites in a EU proposal, we do this in a tabular form as asked for in the
+% template. We use the internal counter |@sites@po| (sites plus one) for convenience.
+% \begin{macrocode}
+\newcounter{@sitespo}\newcounter{@sitespt}
+\renewcommand\wpheadertable{%
+\wp@sites@efforts@lines%
+\setcounter{@sitespo}{\thewp@sites@num}\addtocounter{@sitespo}{1}%
+\par\noindent\begin{tabular}{|l|*{\thewp@sites@num}{c|}c|}\hline%
+\multicolumn{\the@sitespo}{|l|}{\textbf{\wp@mk@title{\wp@num}: }%
+\textsf{\pdata@target{wp}{\wp@id}{\pdataref{wp}\wp@id{title}}}}
+&\textbf{Start: }\pdataref{wp}\wp@id{start}\\\hline%
+\wp@sites@line\\\hline%
+\wp@efforts@line\\\hline%
+\end{tabular}\smallskip\par\noindent\ignorespaces}
+% \end{macrocode}
+% \end{macro}
+%
+% \subsection{Milestones and Deliverables}\label{sec:impl:deliverables}
+%
+% \begin{environment}{wpdelivs}
+% We make the deliverables boxed in EU proposals, this is simple with |mdframed.sty|.
+% \begin{macrocode}
+\surroundwithmdframed{wpdelivs}
+% \end{macrocode}
+% \end{environment}
+%
+% \begin{macro}{\milestone}
+% \begin{macrocode}
+\define@key{milestone}{verif}{\gdef\mile@verif{#1}\pdata@def{mile}\mile@id{verif}{#1}}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{milestonetable}
+% here we do the work.
+% \begin{macrocode}
+\define@key{mst}{caption}{\gdef\mst@caption{#1}}
+\define@key{mst}{wname}{\gdef\mst@wname{#1}}
+\define@key{mst}{wdeliv}{\gdef\mst@wdeliv{#1}}
+\define@key{mst}{wverif}{\gdef\mst@wverif{#1}}
+\newcommand\milestonetable[1][]{%
+\def\mst@caption{Milestones, Deliverables, and Verification}%
+\def\mst@wname{2.5cm}\def\mst@wdeliv{7cm}\def\mst@wverif{4cm}
+\setkeys{mst}{#1}%
+{\gdef\mst@lines{}%initialize
+\let\tabularnewline\relax\let\hline\relax% so they
+\let\textbf\relax\let\emph\relax% do not bother us
+\edef\@@miles{\pdataref{all}{mile}{ids}}
+\@for\@I:=\@@miles\do{
+\edef\@delivs{\pdataref@safe{mile}{\@I}{delivs}}%
+\def\@@delivs{}
+\@for\@J:=\@delivs\do{\xdef\@@delivs{\@@delivs\ \pdataref{deliv}\@J{label}}}
+\def\@@line{
+\textbf{\pdataref{mile}\@I{label}}&
+\emph{\pdataref{mile}{\@I}{title}} &
+\@@delivs&
+\pdataref{mile}\@I{month} &
+\pdataref{mile}\@I{verif}}
+\xdef\mst@lines{\mst@lines\@@line\tabularnewline\hline}}}
+\begin{table}[ht]
+\begin{tabular}{|l|p{\mst@wname}|p{\mst@wdeliv}|l|p{\mst@wverif}|}\hline
+\#&\textbf{\miles@legend@name}
+&\textbf{\miles@legend@involved}
+&\textbf{\miles@legend@mo}
+&\textbf{\miles@legend@verif}\\\hline\hline
+\mst@lines
+\end{tabular}
+\caption{\mst@caption}\label{tab:milestonetable}
+\end{table}
+\footnotetext\miles@legend@footnote}
+% \end{macrocode}
+% now the multilinguality support
+% \begin{macrocode}
+\newcommand\miles@legend@name{Name}
+\newcommand\miles@legend@mo{Mo}
+\newcommand\miles@legend@verif{Means of Verif.}
+\newcommand\miles@legend@involved{WPs\footnotemark/Deliverables involved}
+\newcommand\miles@legend@footnote{The work package number is the first number in the deliverable number.}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\prop@milesfor}
+% the due date is the first argument to facilitate sorting
+% \begin{macrocode}
+\newcommand\prop@milesfor[1]{\edef\@delivs{\pdataref@safe{mile}{#1}{delivs}}%
+\let\m@sep=\relax\def\new@sep{,\ }%
+\@for\@I:=\@delivs\do{\m@sep\pdataRef{deliv}\@I{label}\let\m@sep=\new@sep}}
+% \end{macrocode}
+% \end{macro}
+%
+% \subsection{Risks}\label{sec:impl:risks}
+%
+% \begin{environment}{risk}
+% \begin{macrocode}
+\newenvironment{risk}[3]
+{\paragraph{Risk: #1}\hfill\emph{probability}: #2, \emph{gravity}: #3\par\noindent\ignorespaces}
+{}
+% \end{macrocode}
+% \end{environment}
+%
+% \begin{environment}{riskcont}
+% \begin{macrocode}
+\newenvironment{riskcont}[3]
+{\begin{risk}{#1}{#2}{#3}\textbf{Contingency:} }
+{\end{risk}}
+% \end{macrocode}
+% \end{environment}
+%
+% \subsection{Relevant Papers}\label{sec:impl:papers}
+%
+% \begin{macro}{\keypubs}
+% \ednote{MK: the baselinestretch manipulation does not work here, since
+% \texttt{prop@paperslist} makes its own provisions. We should provide a way of
+% manipulating sizes here.}
+% \begin{macrocode}
+\newcommand\keypubs[1]{%
+\paragraph{Key publications relevant to the project}%
+{\renewcommand{\baselinestretch}{.9}\prop@paperlist{#1}}}
+%</cls>
+% \end{macrocode}
+% \end{macro}
+%
+% \Finale
+\endinput
+% LocalWords: iffalse cls euproposal euproposal.dtx tt maketitle newpage wpwa eudata dfg
+% LocalWords: tableofcontents ednote euproposal DescribeEnv compactitem impl eureporting
+% LocalWords: longtable eurosym pdata thepart setcounter env vfill qquad NeedsTeXFormat
+% LocalWords: thechapter newcommand tabularnewline hline xdef pdataref nameuse SciML gen
+% LocalWords: countryshort rpoposal clange wrapfig wrapfigure vspace bfseries eupdata wd
+% LocalWords: startsection normalfont normalsize baselinestretch callname hb newpart wp
+% LocalWords: countryshort rpoposal clange wrapfig renewenvironment worktelfax prop@gen
+% LocalWords: tocdepth wpobjectives newenvironment noindent boxedminipage fbox warnpubs
+% LocalWords: textwidth textbf wpdescription sitedescription pgfdeclareimage projpapers
+% LocalWords: wrapfigure vspace pgfuseimage streetaddress townzip textsc xt wa maxnames
+% LocalWords: renewcommand startsection normalfont normalsize bfseries wptitle sitedesc
+% LocalWords: workpackage subsubsection wpheadertable newcounter sitespo hfil if@svninfo
+% LocalWords: newcounter sitespt addtocounter textsf smallskip ignorespaces pn setkeys
+% LocalWords: cellcolor lightgray keypubs paperlist callname callid callid ifx csname
+% LocalWords: challengeid challengeid objectiveid objectiveid outcomeid hfill if@gitinfo
+% LocalWords: outcomeid metakeys workaddress numberline tempdima ifsubmit iconrowheight
+% LocalWords: proposal.dtx texttt paperslist workaddress.dtx topicsaddressed thesite
+% LocalWords: topicsaddressed iconrowheight finalreport.tex printbibliography endcsname
+% LocalWords: reportperiod organisation thispagestyle gitAbbrevHash sitedescritpion
+% LocalWords: WAinstitution picv medskip newmdenv frametitle wpdelivs mdframed.sty emph
+% LocalWords: surroundwithmdframed emph riskcont prob grav ldots endinput
diff --git a/macros/latex/contrib/proposal/eu/euproposal.ins b/macros/latex/contrib/proposal/eu/euproposal.ins
new file mode 100644
index 0000000000..eba8cbf9bb
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/euproposal.ins
@@ -0,0 +1,37 @@
+%%
+%% This file generates files required to use the dfgproposal package.
+%% At your command prompt write
+%%
+%% latex dfgproposal.ins
+%%
+%% Copyright(c) 2010 Michael Kohlhase
+%%
+%% This file is distributed under the terms of the LaTeX Project Public
+%% License from CTAN archives in directory macros/latex/base/lppl.txt.
+%% Either version 1.0 or, at your option, any later version.
+%%
+%% $Id: euproposal.ins 23009 2012-01-18 10:12:28Z kohlhase $
+%% $HeadURL: https://svn.kwarc.info/repos/kwarc/doc/macros/forCTAN/proposal/eu/euproposal.ins $
+
+\input docstrip
+\preamble
+\endpreamble
+
+%\usedir{tex/latex/listings}
+\keepsilent
+\askforoverwritefalse
+
+% generate base package
+\generate{\file{eupdata.sty}{\from{euproposal.dtx}{pdata}}}
+\generate{\file{euproposal.cls}{\from{euproposal.dtx}{cls}}}
+\generate{\file{eureporting.cls}{\from{euproposal.dtx}{reporting}}}
+
+\Msg{*}
+\Msg{* You probably need to move the file euproposal.cls, eureporting.cls, and eupdata.sty}
+\Msg{* into a directory searched by TeX.}
+\Msg{*}
+\Msg{* And don't forget to refresh your filename database}
+\Msg{* if your TeX distribution uses such a database.}
+\Msg{*}
+
+\endbatchfile
diff --git a/macros/latex/contrib/proposal/eu/euproposal.pdf b/macros/latex/contrib/proposal/eu/euproposal.pdf
new file mode 100644
index 0000000000..8d3cd256f0
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/euproposal.pdf
Binary files differ
diff --git a/macros/latex/contrib/proposal/eu/strep/Makefile b/macros/latex/contrib/proposal/eu/strep/Makefile
new file mode 100644
index 0000000000..9b4a6fdb04
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/Makefile
@@ -0,0 +1,77 @@
+###########################################################################
+# Automating proposal management by make.
+# The participants work on proposal.tex in "draft" mode, which gives a lot
+# of information to the developers. Variants submit.tex and public.tex are
+# used to prepare official versions (hiding development/private info).
+###########################################################################
+# possibly customize the following variables to your setting
+PROPOSAL = propB.tex # the proposal
+BIB = ../lib/dummy.bib # bibTeX databases
+PROP.dir = ../../..
+###########################################################################
+# the following are computed
+TSIMP = # pdflatex Targets without bibTeX
+TSIMP.pdf = $(TSIMP:%.tex=%.pdf) # PDFs to be produced
+TBIB = $(PROPOSAL) # pdflatex Targets with bibTeX
+TARGET = $(TSIMP) $(TBIB) # all pdflatex targets
+TBIB.pdf = $(TBIB:%.tex=%.pdf) # PDFs to be produced
+TBIB.aux = $(TBIB:%.tex=%.aux) # their aux files.
+PDATA = $(PROPOSAL:%.tex=%.pdata) # the proposal project data
+SRC = $(filter-out $(TARGET),$(shell ls *.tex)) # included files
+PDFLATEX = pdflatex -interaction batchmode -file-line-error
+BBL.base = 1 2 3 4
+BBL = $(PROPOSAL:%.tex=%.bbl) $(BBL.base:%=$(PROPOSAL:%.tex=%)%-blx.bbl)
+PROPCLS.dir = $(PROP.dir)/base
+PROPETC.dir = $(PROP.dir)/etc
+EUPROPCLS.dir = $(PROP.dir)/eu
+TEXINPUTS := .//:$(PROPCLS.dir)//:$(EUPROPCLS.dir)//:$(PROPETC.dir)//:
+BIBINPUTS := ../lib:$(BIBINPUTS)
+PROPCLS.clssty = proposal.cls pdata.sty
+PROPETC.sty = workaddress.sty metakeys.sty sref.sty
+EUPROPCLS.clssty = euproposal.cls
+PROPCLS = $(PROPCLS.clssty:%=$(PROPCLS.dir)/%) $(EUPROPCLS.clssty:%=$(EUPROPCLS.dir)/%) $(PROPETC.sty:%=$(PROPETC.dir)/%)
+
+all: $(TBIB.pdf) $(TSIMP.pdf)
+
+submit:
+ $(MAKE) -w PROPOSAL=final.tex all
+
+public:
+ $(MAKE) -w PROPOSAL=public.tex all
+
+bbl: $(BBL)
+$(BBL): %.bbl: %.aux
+ bibtex -min-crossrefs=100 -terse $<
+
+$(TSIMP.pdf): %.pdf: %.tex $(PROPCLS) $(PDATA)
+ $(PDFLATEX) $< || $(RM) $@
+
+$(PDATA): %.pdata: %.tex
+ $(PDFLATEX) $<
+
+$(TBIB.aux): %.aux: %.tex
+ $(PDFLATEX) $<
+
+$(TBIB.pdf): %.pdf: %.tex $(SRC) $(BIB) $(PROPCLS)
+ $(PDFLATEX) $< || $(RM) $@
+ sort $(PROPOSAL:%.tex=%.delivs) > $(PROPOSAL:%.tex=%.deliverables)
+ @if (test -e $(patsubst %.tex, %.idx, $<));\
+ then makeindex $(patsubst %.tex, %.idx, $<); fi
+ $(MAKE) -$(MAKEFLAGS) $(BBL)
+ @if (grep "(re)run BibTeX" $(patsubst %.tex, %.log, $<)> /dev/null);\
+ then $(MAKE) -B $(BBL); fi
+ $(PDFLATEX) $< || $(RM) $@
+ @if (grep Rerun $(patsubst %.tex, %.log, $<) > /dev/null);\
+ then $(PDFLATEX) $< || $(RM) $@; fi
+ @if (grep Rerun $(patsubst %.tex, %.log, $<) > /dev/null);\
+ then $(PDFLATEX) $< || $(RM) $@; fi
+
+clean:
+ rm -f *.log *.blg *~ *.synctex.gz *.cut
+
+distclean: clean
+ rm -f *.aux *.out *.run.xml *.bbl *.toc *.deliv* *.pdata
+ rm -Rf auto
+
+echo:
+ echo $(BBL)
diff --git a/macros/latex/contrib/proposal/eu/strep/README b/macros/latex/contrib/proposal/eu/strep/README
new file mode 100644
index 0000000000..72aee78682
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/README
@@ -0,0 +1,14 @@
+An Exapmle for euproposal.cls
+
+proposal.tex is a fake EU proposal that shows all elements of euproposal.cls
+ in action.
+*.tex the rest are intemediate files
+Makefile allows the automation via a unix Makefile on the author's
+ machine, adapt it to your needs
+
+Copyright(c) 2010 Michael Kohlhase
+The package is distributed under the terms of the LaTeX Project Public License (LPPL)
+
+The development version of this package can be found at
+https://svn.kwarc.info/repos/kwarc/doc/macros/forCTAN/euproposal
+
diff --git a/macros/latex/contrib/proposal/eu/strep/deliverables.tex b/macros/latex/contrib/proposal/eu/strep/deliverables.tex
new file mode 100644
index 0000000000..355a7fd13e
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/deliverables.tex
@@ -0,0 +1,34 @@
+\subsection{List of Deliverables}\label{sec:deliverables}
+
+\begin{todo}{from the proposal template}
+\begin{compactenum}
+\item Deliverable numbers in order of delivery dates. Please use the numbering convention <WP number>.<number of deliverable within
+that WP>. For example, deliverable 4.2 would be the second deliverable from work package 4.
+\item Please indicate the nature of the deliverable using one of the following codes:
+R = Report, P = Prototype, D = Demonstrator, O = Other
+\item Please indicate the dissemination level using one of the following codes:
+PU = Public
+PP = Restricted to other programme participants (including the Commission Services).
+RE = Restricted to a group specified by the consortium (including the Commission Services).
+CO = Confidential, only for members of the consortium (including the Commission Services).
+\end{compactenum}
+\end{todo}
+We will now give an overview over the deliverables and milestones of the work
+packages. Note that the times of deliverables after month 24 are estimates and may change
+as the work packages progress.
+
+In the table below, {\emph{integrating work deliverables}} (see top of
+section~\ref{sec:wplist}) are printed in boldface to mark them. They integrate
+contributions from multiple work packages. \ednote{CL: the rest of this paragraph does not
+ comply with the EU guide for applicants, needs to be rewritten}These can have the
+dissemination level ``partial'', which indicates that it contains parts of level
+``project'' that are to be disseminated to the project and evaluators only. In such
+reports, two versions are prepared, and disseminated accordingly.
+
+{\footnotesize\inputdelivs{8cm}}
+
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: "propB"
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/draft.tex b/macros/latex/contrib/proposal/eu/strep/draft.tex
new file mode 100644
index 0000000000..9b8be16dd9
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/draft.tex
@@ -0,0 +1 @@
+\input{proposal.tex}
diff --git a/macros/latex/contrib/proposal/eu/strep/final.tex b/macros/latex/contrib/proposal/eu/strep/final.tex
new file mode 100644
index 0000000000..3d105cc409
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/final.tex
@@ -0,0 +1,7 @@
+\newcommand{\classoptions}{submit}
+\input{proposal.tex}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: t
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/grantagreement.tex b/macros/latex/contrib/proposal/eu/strep/grantagreement.tex
new file mode 100644
index 0000000000..b90ee7b8f7
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/grantagreement.tex
@@ -0,0 +1,7 @@
+\newcommand{\classoptions}{submit,grantagreement}
+\input{proposal.tex}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: t
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/impact.tex b/macros/latex/contrib/proposal/eu/strep/impact.tex
new file mode 100644
index 0000000000..210ebdee35
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/impact.tex
@@ -0,0 +1,40 @@
+\chapter{Impact}\label{chap:impact}
+\ednote{Maximum length for the whole of Section 3 –-- ten pages}
+
+\section{Expected Impacts listed in the Work Programe }\label{sec:expected-impact}
+\begin{todo}{from the proposal template}
+ Describe how your project will contribute towards the expected impacts listed in the
+ work programme in relation to the topic or topics in question. Mention the steps that
+ will be needed to bring about these impacts. Explain why this contribution requires a
+ European (rather than a national or local) approach. Indicate how account is taken of
+ other national or international research activities. Mention any assumptions and
+ external factors that may determine whether the impacts will be achieved.
+\end{todo}
+\subsection{Medium Term Expected Outcome}
+
+\subsection{Long Term Expected Outcomes}
+\subsection{Use Cases}
+
+\section{Dissemination and/or Use of Project Results, and Management of Intellectual Property}\label{sec:dissemination}
+
+\begin{todo}{from the proposal template}
+ Describe the measures you propose for the dissemination and/or exploitation of project
+ results, and how these will increase the impact of the project. In designing these
+ measures, you should take into account a variety of communication means and target
+ groups as appropriate (e.g. policy-makers, interest groups, media and the public at
+ large).
+
+ For more information on communication guidance, see the URL
+ \url{http://ec.europa.eu/research/science-society/science-communication/index_en.htm}
+
+ Describe also your plans for the management of knowledge (intellectual property)
+ acquired in the course of the project.
+\end{todo}
+
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: ednote
diff --git a/macros/latex/contrib/proposal/eu/strep/implementation.tex b/macros/latex/contrib/proposal/eu/strep/implementation.tex
new file mode 100644
index 0000000000..5d687c903d
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/implementation.tex
@@ -0,0 +1,103 @@
+\chapter{Implementation}\label{chap:implementation}
+
+\section{Management Structure and Procedures}\label{chap:management}
+\begin{todo}{from the proposal template}
+ Describe the organizational structure and decision-making mechanisms
+ of the project. Show how they are matched to the nature, complexity
+ and scale of the project. Maximum length of this section: five pages.
+\end{todo}
+
+The Project Management of {\pn} is based on its Consortium Agreement, which will be
+signed before the Contract is signed by the Commission. The Consortium Agreement will
+enter into force as from the date the contract with the European Commission is signed.
+\subsection{Organizational structure}\label{sec:management-structure}
+\subsection{Milestones}\label{sec:milestones}
+\milestonetable
+\subsection{Risk Assessment and Management}
+\subsection{Information Flow and Outreach}\label{sec:spread-excellence}
+\subsection{Quality Procedures}\label{sec:quality-management}
+\subsection{Internal Evaluation Procedures}
+\newpage
+\section{Individual Participants}\label{sec:partners}
+\begin{todo}{from the proposal template}
+For each participant in the proposed project, provide a brief description of the legal entity, the main
+tasks they have been attributed, and the previous experience relevant to those tasks. Provide also a
+short profile of the individuals who will be undertaking the work.\\
+Maximum length for Section 2.2: one page per participant. However, where two or more departments within
+an organisation have quite distinct roles within the proposal, one page per department is acceptable.\\
+The maximum length applying to a legal entity composed of several members, each of which is a separate
+legal entity (for example an EEIG1), is one page per member, provided that the members have quite distinct
+roles within the proposal.
+\end{todo}
+\newpage
+\input{site-jacu}\newpage
+\input{site-efo}\newpage
+\input{site-bar}\newpage
+\input{site-baz}\newpage
+
+\section{The {\protect\pn} consortium as a whole}
+\begin{todo}{from the proposal template}
+ Describe how the participants collectively constitute a consortium capable of achieving
+ the project objectives, and how they are suited and are committed to the tasks assigned
+ to them. Show the complementarity between participants. Explain how the composition of
+ the consortium is well-balanced in relation to the objectives of the project.
+
+ If appropriate describe the industrial/commercial involvement to ensure exploitation of
+ the results. Show how the opportunity of involving SMEs has been addressed
+\end{todo}
+
+The project partners of the \pn project have a long history of successful collaboration;
+Figure~\ref{tab:collaboration} gives an overview over joint projects (including proposals) and
+joint publications (only international, peer reviewed ones).
+
+\jointorga{jacu,efo,baz}
+\jointpub{efo,baz,jacu}
+\jointproj{efo,bar}
+\jointsup{jacu,bar}
+\jointsoft{baz,efo}
+\coherencetable
+
+\subsection{Subcontracting}\label{sec:subcontracting}
+\begin{todo}{from the proposal template}
+ If any part of the work is to be sub-contracted by the participant responsible for it,
+ describe the work involved and explain why a sub-contract approach has been chosen for
+ it.
+\end{todo}
+\subsection{Other Countries}\label{sec:other-countries}
+\begin{todo}{from the proposal template}
+ If a one or more of the participants requesting EU funding is based outside of the EU
+ Member states, Associated countries and the list of International Cooperation Partner
+ Countries\footnote{See CORDIS web-site, and annex 1 of the work programme.}, explain in
+ terms of the project’s objectives why such funding would be essential.
+\end{todo}
+
+\subsection{Additional Partners}\label{sec:assoc-partner}
+\begin{todo}{from the proposal template}
+ If there are as-yet-unidentified participants in the project, the expected competences,
+ the role of the potential participants and their integration into the running project
+ should be described
+\end{todo}
+\section{Resources to be Committed}\label{sec:resources}
+\begin{todo}{from the proposal template}
+Maximum length: two pages
+
+Describe how the totality of the necessary resources will be mobilized, including any resources that
+will complement the EC contribution. Show how the resources will be integrated in a coherent way,
+and show how the overall financial plan for the project is adequate.
+
+In addition to the costs indicated on form A3 of the proposal, and the effort shown in Section 1.3
+above, please identify any other major costs (e.g. equipment). Ensure that the figures stated in Part B
+are consistent with these.
+\end{todo}
+
+\subsection{Travel Costs and Consumables}\label{sec:travel-costs}
+\subsection{Subcontracting Costs}
+\subsection{Other Costs}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: pn newpage site-jacu site-efo site-baz jointpub efo baz
+% LocalWords: jointproj coherencetable assoc-partner
diff --git a/macros/latex/contrib/proposal/eu/strep/issues.tex b/macros/latex/contrib/proposal/eu/strep/issues.tex
new file mode 100644
index 0000000000..e17761b8b7
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/issues.tex
@@ -0,0 +1,59 @@
+\chapter{Ethical Issues}\label{chap:ethical}
+\begin{todo}{from the proposal template}
+ Describe any ethical issues that may arise in the project. In particular, you should
+ explain the benefit and burden of the experiments and the effects it may have on the
+ research subject. Identify the countries where research will be undertaken and which
+ ethical committees and regulatory organisations will need to be approached during the
+ life of the project.
+
+ Include the Ethical issues table below. If you indicate YES to any issue, please
+ identify the pages in the proposal where this ethical issue is described. Answering
+ 'YES' to some of these boxes does not automatically lead to an ethical review1. It
+ enables the independent experts to decide if an ethical review is required. If you are
+ sure that none of the issues apply to your proposal, simply tick the YES box in the last
+ row.
+\end{todo}
+
+\begin{small}
+\begin{tabular}{|p{1em}p{11cm}|l|l|}\hline
+ \multicolumn{2}{|l|}{\cellcolor{lightgray}{\strut}} &
+ \cellcolor{lightgray}{YES} &
+ \cellcolor{lightgray}{PAGE}\\\hline
+ \multicolumn{2}{|l|}{\bf{Informed Consent}} & & \\\hline
+ & Does the proposal involve children? & & \\\hline
+ & Does the proposal involve patients or persons not able to give consent? & & \\\hline
+ & Does the proposal involve adult healthy volunteers? & & \\\hline
+ & Does the proposal involve Human Genetic Material? & & \\\hline
+ & Does the proposal involve Human biological samples? & & \\\hline
+ & Does the proposal involve Human data collection? & & \\\hline
+ \multicolumn{2}{|l|}{\bf{Research on Human embryo/foetus}} & & \\\hline
+ & Does the proposal involve Human Embryos? & & \\\hline
+ & Does the proposal involve Human Foetal Tissue / Cells? & & \\\hline
+ & Does the proposal involve Human Embryonic Stem Cells? & & \\\hline
+ \multicolumn{2}{|l|}{\bf{Privacy}} & & \\\hline
+ & Does the proposal involve processing of genetic information
+ or personal data (eg. health, sexual lifestyle, ethnicity,
+ political opinion, religious or philosophical conviction) & & \\\hline
+ & Does the proposal involve tracking the location or observation
+ of people? & & \\\hline
+ \multicolumn{2}{|l|}{\bf{Research on Animals}} & & \\\hline
+ & Does the proposal involve research on animals? & & \\\hline
+ & Are those animals transgenic small laboratory animals? & & \\\hline
+ & Are those animals transgenic farm animals? & & \\\hline
+ & Are those animals cloned farm animals? & & \\\hline
+ & Are those animals non-human primates? & & \\\hline
+ \multicolumn{2}{|l|}{\bf{Research Involving Developing Countries}} & & \\\hline
+ & Use of local resources (genetic, animal, plant etc) & & \\\hline
+ & Benefit to local community (capacity building
+ i.e. access to healthcare, education etc) & & \\\hline
+ \multicolumn{2}{|l|}{\bf{Dual Use}} & & \\\hline
+ & Research having direct military application & & \\\hline
+ & Research having the potential for terrorist abuse & & \\\hline
+ \multicolumn{2}{|l|}{\bf{ICT Implants}} & & \\\hline
+ & Does the proposal involve clinical trials of ICT implants? & & \\\hline
+ \multicolumn{2}{|l|}{\bf\footnotesize{I CONFIRM THAT NONE OF THE ABOVE ISSUES APPLY TO MY PROPOSAL}}
+ & &\cellcolor{lightgray}{} \\\hline
+\end{tabular}
+\end{small}
+
+\section{Personal Data}
diff --git a/macros/latex/contrib/proposal/eu/strep/methodology.tex b/macros/latex/contrib/proposal/eu/strep/methodology.tex
new file mode 100644
index 0000000000..86eea4c848
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/methodology.tex
@@ -0,0 +1,49 @@
+\section{Scientific/Technical Methodology and Work Plan}\label{sec:methodology}
+\begin{todo}{from the proposal template}
+ A detailed work plan should be presented, broken down into work packages\footnote{A work
+ package is a major sub-division of the proposed project with a verifiable end-point –
+ normally a deliverable or an important milestone in the overall project.} (WPs) which
+ should follow the logical phases of the implementation of the project, and include
+ consortium management and assessment of progress and results. (Note that your overall
+ approach to management will be described later, in Section 2).
+
+Notes: The number of work packages used must be appropriate to the complexity of the work
+and the overall value of the proposed project. The planning should be sufficiently
+detailed to justify the proposed effort and allow progress monitoring by the Commission.
+
+Any significant risks should be identified, and contingency plans described
+\end{todo}
+\newpage\input{workplan}
+
+\newpage
+\subsection{Work Package List}\label{sec:wplist}
+
+\begin{todo}{from the proposal template}
+Please indicate one activity per work package:
+RTD = Research and technological development; DEM = Demonstration; MGT = Management of the consortium
+\end{todo}
+
+%\makeatletter\wp@total@RM{management}\makeatother
+\wpfigstyle{\footnotesize}
+\wpfig[pages,type,start,end]
+
+\newpage\input{deliverables}
+\newpage\input{milestones}
+
+\subsection{Work Package Descriptions}\label{sec:workpackages}
+\begin{workplan}
+\input{wp-management}\newpage
+\input{wp-dissem}\newpage
+\input{wp-class}\newpage
+\input{wp-temple}\newpage
+\end{workplan}
+\newpage\input{risks}
+
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: workplan newpage wplist makeatletter makeatother wpfig
+% LocalWords: workpackages wp-dissem wp-class wp-temple
diff --git a/macros/latex/contrib/proposal/eu/strep/milestones.tex b/macros/latex/contrib/proposal/eu/strep/milestones.tex
new file mode 100644
index 0000000000..b64a865eac
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/milestones.tex
@@ -0,0 +1,40 @@
+\subsection{List of Milestones}\label{sec:milestones}
+
+\begin{todo}{from the proposal template}
+ Milestones are control points where decisions are needed with regard to the next stage
+ of the project. For example, a milestone may occur when a major result has been
+ achieved, if its successful attainment is a requirement for the next phase of
+ work. Another example would be a point when the consortium must decide which of several
+ technologies to adopt for further development.
+
+ Means of verification: Show how you will confirm that the milestone has been
+ attained. Refer to indicators if appropriate. For examples: a laboratory prototype
+ completed and running flawlessly, software released and validated by a user group, field
+ survey complete and data quality validated.
+\end{todo}
+
+
+The work in the {\pn} project is structured by seven milestones, which coincide with the
+project meetings in summer and fall. Since the meetings are the main face-to-face
+interaction points in the project, it is suitable to schedule the milestones for these
+events, where they can be discussed in detail. We envision that this setup will give the
+project the vital coherence in spite of the broad mix of disciplinary backgrounds of the
+participants.\ednote{maybe automate the milestones}
+
+\begin{milestones}
+ \milestone[id=kickoff,verif=Inspection,month=1]
+ {Initial Infrastructure}
+ {Set up the organizational infrastructure, in particular: Web Presence, project TRAC,\ldots}
+ \milestone[id=consensus,verif=Inspection,month=24]{Consensus} {Reach Consensus on the
+ way the project goes}
+ \milestone[id=exploitation,verif=Inspection,month=36]{Exploitation}{The exploitation
+ plan should be clear so that we can start on this in the last year.}
+ \milestone[id=final,verif=Inspection,month=48]{Final Results}{all is done}
+\end{milestones}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: pn ednote verif ldots
diff --git a/macros/latex/contrib/proposal/eu/strep/objectives.tex b/macros/latex/contrib/proposal/eu/strep/objectives.tex
new file mode 100644
index 0000000000..d960032a30
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/objectives.tex
@@ -0,0 +1,13 @@
+\section{Concept and Objectives}\label{sec:objectives}
+\begin{todo}{from the proposal template}
+ Explain the concept of your project. What are the main ideas that led you to propose
+ this work? Describe in detail the S\&T objectives. Show how they relate to the topics
+ addressed by the call. The objectives should be those achievable within the project, not
+ through subsequent development. They should be stated in a measurable and verifiable
+ form, including through the milestones that will be indicated under Section 1.3 below.
+\end{todo}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: "propB"
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/progress.tex b/macros/latex/contrib/proposal/eu/strep/progress.tex
new file mode 100644
index 0000000000..bd39229025
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/progress.tex
@@ -0,0 +1,11 @@
+\section{Progress beyond the State-of-the-Art}\label{sec:progress}
+\begin{todo}{from the proposal template}
+ Describe the state-of-the-art in the area concerned, and the advance that the proposed
+ project would bring about. If applicable, refer to the results of any patent search you
+ might have carried out.
+\end{todo}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: "propB"
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/propB.pdf b/macros/latex/contrib/proposal/eu/strep/propB.pdf
new file mode 100644
index 0000000000..1c5eebf5f1
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/propB.pdf
Binary files differ
diff --git a/macros/latex/contrib/proposal/eu/strep/propB.tex b/macros/latex/contrib/proposal/eu/strep/propB.tex
new file mode 100644
index 0000000000..13afd61a7d
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/propB.tex
@@ -0,0 +1,65 @@
+% The main file for developing the proposal.
+% Variants with different class options are
+% - submit.tex (no draft stuff, no ednotes, no revision information)
+% - public.tex (like submit.tex, but no financials either)
+\providecommand{\classoptions}{,keys} % to be overwritten in variants
+\documentclass[noworkareas,deliverables,gitinfo,propB\classoptions]{euproposal}
+\usepackage[T1]{fontenc}
+\usepackage[utf8]{inputenc}
+\addbibresource{../lib/dummy}
+\input{../lib/WApersons}% Some sections of the included files depend on this.
+
+\begin{document}
+\begin{center}\color{red}\huge
+ This mock proposal is just an example for \texttt{euproposal.cls} it reflects the ICT
+ template of January 2012
+\end{center}
+\begin{proposal}[site=jacu,jacuRM=36,
+ site=efo,efoRM=36,
+ site=bar,barRM=36,
+ site=baz,bazRM=36,
+ coordinator=miko,
+ acronym={iPoWr},
+ acrolong={\underline{I}ntelligent} {\underline{P}r\underline{o}sal} {\underline{Wr}iting},
+ title=\pn: \protect\pnlong,
+ callname = ICT Call 1,
+ callid = FP7-???-200?-?,
+ instrument= Small or Medium-Scale Focused Research Project (STREP),
+ challengeid = 4,
+ challenge = ICT for EU Proposals,
+ objectiveid={ICT-2012.4.4},
+ objective = Technology-enhanced Documents,
+ outcomeid = b1,
+ outcome = {More time for Research, not Proposal writing},
+ coordinator=miko,
+ months=24,
+ compactht]
+\begin{abstract}
+ Writing grant proposals is a collaborative effort that requires the integration of
+ contributions from many individuals. The use of an ASCII-based format like {\LaTeX}
+ allows to coordinate the process via a source code control system like
+ {\textsc{Subversion}}, allowing the proposal writing team to concentrate on the contents
+ rather than the mechanics of wrangling with text fragments and revisions.
+\end{abstract}
+
+\tableofcontents
+
+\begin{todo}{from the proposal template}
+ Recommended length for the whole part B: 50--60 pages (including tables, references,
+ etc.)
+\end{todo}
+\include{quality}\newpage
+\include{implementation}\newpage
+\include{impact}\newpage
+\include{issues}
+\end{proposal}
+\end{document}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: t
+%%% End:
+
+% LocalWords: efo efoRM baz bazRM miko acrolong ntelligent iting pn pnlong
+% LocalWords: textsc newpage compactht texttt euproposal.cls callname callid
+% LocalWords: challengeid objectiveid outcomeid tableofcontents
diff --git a/macros/latex/contrib/proposal/eu/strep/public.pdf b/macros/latex/contrib/proposal/eu/strep/public.pdf
new file mode 100644
index 0000000000..2c9e43abdb
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/public.pdf
Binary files differ
diff --git a/macros/latex/contrib/proposal/eu/strep/public.tex b/macros/latex/contrib/proposal/eu/strep/public.tex
new file mode 100644
index 0000000000..00c95f15a3
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/public.tex
@@ -0,0 +1,7 @@
+\newcommand{\classoptions}{,submit,public}
+\input{proposal}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/quality.tex b/macros/latex/contrib/proposal/eu/strep/quality.tex
new file mode 100644
index 0000000000..5aee278b8f
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/quality.tex
@@ -0,0 +1,14 @@
+\chapter{Scientific and Technical Quality}\label{chap:quality}
+\begin{todo}{from the proposal template}
+ Maximum length for the whole of Section 1 –-- twenty pages, not including the tables in
+ Section 1.3
+\end{todo}
+
+\input{objectives}
+\input{progress}
+\input{methodology}
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
+
diff --git a/macros/latex/contrib/proposal/eu/strep/risks.tex b/macros/latex/contrib/proposal/eu/strep/risks.tex
new file mode 100644
index 0000000000..19580761f7
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/risks.tex
@@ -0,0 +1,17 @@
+\subsection{Significant Risks and Associated Contingency Plans}\label{sec:risks}
+\begin{todo}{from the proposal template}
+ Describe any significant risks, and associated contingency plans
+\end{todo}
+\begin{oldpart}{need to integrate this somewhere. CL: I will check other proposals to see how they did it; the Guide does not really prescribe anything.}
+\paragraph{Global Risk Management}
+The crucial problem of \pn (and similar endeavors that offer a new basis for communication
+and interaction) is that of community uptake: Unless we can convince scientists and
+knowledge workers industry to use the new tools and interactions, we will
+never be able to assemble the large repositories of flexiformal mathematical knowledge we
+envision. We will consider uptake to be the main ongoing evaluation criterion for the network.
+\end{oldpart}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: "propB"
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/site-bar.tex b/macros/latex/contrib/proposal/eu/strep/site-bar.tex
new file mode 100644
index 0000000000..13868a7e78
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/site-bar.tex
@@ -0,0 +1,19 @@
+\begin{sitedescription}{bar}
+
+\paragraph{Organization}
+ Universit\'e de BAR specializes on drinking lots of red wine. It is a partner in the
+ consortium, because it has a very nice chateau on the Cote d'Azure, where it can host
+ gorgeous project meetings.
+
+\paragraph{Main tasks}
+\paragraph{Relevant previous experience}
+\paragraph{Specific expertise}
+\paragraph{Staff members undertaking the work}
+\keypubs{providemore}
+
+\end{sitedescription}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/site-baz.tex b/macros/latex/contrib/proposal/eu/strep/site-baz.tex
new file mode 100644
index 0000000000..d3f5d1f0fd
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/site-baz.tex
@@ -0,0 +1,13 @@
+\begin{sitedescription}{baz}
+\paragraph{Organization}
+\paragraph{Main tasks}
+\paragraph{Relevant previous experience}
+\paragraph{Specific expertise}
+\paragraph{Staff members undertaking the work}
+\keypubs{providemore}
+\end{sitedescription}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/site-efo.tex b/macros/latex/contrib/proposal/eu/strep/site-efo.tex
new file mode 100644
index 0000000000..c3bafffadf
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/site-efo.tex
@@ -0,0 +1,14 @@
+\begin{sitedescription}{efo}
+\paragraph{Organization}
+ The EFO is the world leader in futurology, \ldots
+\paragraph{Main tasks}
+\paragraph{Relevant previous experience}
+\paragraph{Specific expertise}
+\paragraph{Staff members undertaking the work}
+\keypubs{providemore}
+\end{sitedescription}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/site-jacu.tex b/macros/latex/contrib/proposal/eu/strep/site-jacu.tex
new file mode 100644
index 0000000000..6b4fe3b8c7
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/site-jacu.tex
@@ -0,0 +1,53 @@
+\begin{sitedescription}{jacu}
+
+\paragraph{Organization} Jacobs University Bremen is a private research university patterned
+after the Anglo-Saxon university system. The university opened in
+2001 and has an international student body ($1,245$ students from 102
+nations as of 2011, admitted in a highly selective process).
+
+The KWARC (KnoWledge Adaptation and Reasoning for
+Content\footnote{\url{http://kwarc.info}}) Group headed by
+{\emph{Prof.\ Dr.\ Michael Kohlhase}} specializes in building
+knowledge management systems for e-science applications, in particular
+for the natural and mathematical sciences. Formal logic, natural
+language semantics, and semantic web technology provide the
+foundations for the research of the group.
+
+ Since doing research and developing systems is much more fun than writing proposals,
+ they try go do that as efficiently as possible, hence this meta-proposal.
+
+\paragraph{Main tasks}
+
+\begin{itemize}
+\item creating {\LaTeX} class files
+\end{itemize}
+
+\paragraph{Relevant previous experience}
+
+The KWARC group is the main center and lead implementor of the OMDoc
+(Open Mathematical Document) format for representing mathematical
+knowledge. The group has developed added-value services powered by such semantically rich representations, different paths to obtaining them, as well as platforms that integrate both aspects. Services include the adaptive context-sensitive presentation framework JOMDoc and the semantic search engine MathWebSearch. For obtaining rich mathematical content, the group has been pursuing the two alternatives of assisting manual editing (with the sTeXIDE editing environment) and automatic annotation using natural language processing techniques. The latter is work in progress but builds on the arXMLiv system, which is currently capable of converting 70\% out of the 600,000 scientific publications in the arXiv from {\LaTeX} to XHTML+MathML without errors. Finally, the KWARC group has been developing the Planetary integrated environment.
+
+\paragraph{Specific expertise}
+
+\begin{itemize}
+\item writing intelligent proposals
+\end{itemize}
+
+\paragraph{Staff members involved}
+
+\textbf{Prof.\ Dr.\ Michael Kohlhase} is head of the KWARC research
+group. He is the head developer of the OMDoc mathematical markup
+language. He was a member of the Math Working Group at W3C, which finished its work with the publication of the MathML 3 recommendation. He is president of the OpenMath society and trustee of the MKM
+interest group.
+
+\keypubs{KohDavGin:psewads11,Kohlhase:pdpl10,Kohlhase:omdoc1.2,CarlisleEd:MathML10,StaKoh:tlcspx10}
+\end{sitedescription}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: site-jacu.tex sitedescription emph textbf keypubs KohDavGin
+% LocalWords: psewads11 pdpl10 StaKoh tlcspx10
diff --git a/macros/latex/contrib/proposal/eu/strep/site-templatex.tex b/macros/latex/contrib/proposal/eu/strep/site-templatex.tex
new file mode 100644
index 0000000000..6ffc6ad724
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/site-templatex.tex
@@ -0,0 +1,40 @@
+\begin{sitedescription}{???}
+
+\paragraph{Organization:}
+\ednote{Give a one-paragraph run-down of the site and the team there. }
+
+\paragraph{Main tasks:}
+
+\begin{compactitem}
+\item\ednote{specify the main tasks and reference the respective work packages}
+\end{compactitem}
+
+
+\paragraph{Relevant previous experience:}
+
+\ednote{give an overview over previous work and projects that add to the \pn project}
+
+\paragraph{Specific expertise:}
+
+\begin{compactitem}
+\item \ednote{give three to five specific areas of expertise that pertain to the \pn project}
+\end{compactitem}
+
+\paragraph{Staff members undertaking the work:}
+
+\textbf{Dr.\ Great Leader}\ednote{describe the site leader and his expertise}
+\textbf{Joe Implementor}\ednote{and more of them. }
+\ednote{provide the key publications below}
+\keypubs{providemore}
+\end{sitedescription}
+\end{oldpart}
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: site-jacu.tex clange sitedescription emph compactitem pn semmath
+% LocalWords: prosuming-flexiformal KohSuc asemf06 GinJucAnc alsaacl09 StaKoh
+% LocalWords: tlcspx10 KohDavGin psewads11 ednote Radboud Bia ystok CALCULEMUS
+% LocalWords: textbf keypubs OntoLangMathSemWeb uwb Deyan Ginev Stamerjohanns
+% LocalWords: searchability
diff --git a/macros/latex/contrib/proposal/eu/strep/submit.pdf b/macros/latex/contrib/proposal/eu/strep/submit.pdf
new file mode 100644
index 0000000000..9fee253527
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/submit.pdf
Binary files differ
diff --git a/macros/latex/contrib/proposal/eu/strep/submit.tex b/macros/latex/contrib/proposal/eu/strep/submit.tex
new file mode 100644
index 0000000000..5d92f9374d
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/submit.tex
@@ -0,0 +1,7 @@
+\newcommand{\classoptions}{submit}
+\input{proposal}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/workplan.tex b/macros/latex/contrib/proposal/eu/strep/workplan.tex
new file mode 100644
index 0000000000..d189192bbe
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/workplan.tex
@@ -0,0 +1,19 @@
+\begin{todo}{from the proposal template}
+\begin{enumerate}
+\item Describe the overall strategy of the work plan\ednote{Maximum length – one page}
+\item Show the timing of the different WPs and their components (Gantt chart or similar).
+\end{enumerate}
+\end{todo}
+\begin{figure}
+ \caption{Work package dependencies}
+ \label{fig:wp-deps}
+\end{figure}
+
+\ganttchart[draft,xscale=.45]
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: workplan.tex ednote wp-deps ganttchart xscale
diff --git a/macros/latex/contrib/proposal/eu/strep/wp-class.tex b/macros/latex/contrib/proposal/eu/strep/wp-class.tex
new file mode 100644
index 0000000000..c0c4519861
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/wp-class.tex
@@ -0,0 +1,44 @@
+\begin{workpackage}[id=class,type=RTD,lead=jacu,
+ wphases=3-9!1,
+ title=A {\LaTeX} class for EU Proposals,short=Class,
+ jacuRM=12,barRM=12]
+We can state the state of the art and similar things before the summary in the boxes
+here.
+\wpheadertable
+\begin{wpobjectives}
+\LaTeX is the best document markup language, it can even be used for literate
+programming~\cite{DK:LP,Lamport:ladps94,Knuth:ttb84}
+
+ To develop a {\LaTeX} class for marking up EU Proposals
+\end{wpobjectives}
+
+\begin{wpdescription}
+ We will follow strict software design principles, first comes a requirements analys,
+ then \ldots
+\end{wpdescription}
+
+\begin{wpdelivs}
+ \begin{wpdeliv}[due=6,id=req,nature=R,dissem=PP,miles=kickoff]
+ {Requirements analysis}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=12,id=spec,nature=R,dissem=PU,miles=consensus]
+ {{\pn} Specification }
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=18,id=demonstrator,nature=P,dissem=PU,miles={consensus,final}]
+ {First demonstrator ({\tt{article.cls}} really)}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=24,id=proto,nature=P,dissem=PU,miles=final]
+ {First prototype}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=36,id=release,nature=P,dissem=PU,miles=final]
+ {Final {\LaTeX} class, ready for release}
+ \end{wpdeliv}
+ \end{wpdelivs}
+Furthermore, this work package contributes to {\pdataRef{deliv}{managementreport2}{label}} and
+{\pdataRef{deliv}{managementreport7}{label}}.
+\end{workpackage}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
diff --git a/macros/latex/contrib/proposal/eu/strep/wp-dissem.tex b/macros/latex/contrib/proposal/eu/strep/wp-dissem.tex
new file mode 100644
index 0000000000..7ad3fa9b1f
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/wp-dissem.tex
@@ -0,0 +1,62 @@
+\begin{workpackage}%
+[id=dissem,type=RTD,lead=efo,
+ wphases=10-24!1,
+ title=Dissemination and Exploitation,short=Dissemination,
+ efoRM=8,jacuRM=2,barRM=2,bazRM=2]
+We can state the state of the art and similar things before the summary in the boxes
+here.
+\wpheadertable
+
+\begin{wpobjectives}
+ Much of the activity of a project involves small groups of nodes in joint work. This
+ work package is set up to ensure their best wide-scale integration, communication, and
+ synergetic presentation of the results. Clearly identified means of dissemination of
+ work-in-progress as well as final results will serve the effectiveness of work within
+ the project and steadily improve the visibility and usage of the emerging semantic
+ services.
+\end{wpobjectives}
+
+\begin{wpdescription}
+ The work package members set up events for dissemination of the research and
+ work-in-progress results for researchers (workshops and summer schools), and for
+ industry (trade fairs). An in-depth evaluation will be undertaken of the response of
+ test-users.
+
+ Within two months of the start of the project, a project website will go live. This
+ website will have two areas: a members' area and a public area.\ldots
+\end{wpdescription}
+
+\begin{wpdelivs}
+ \begin{wpdeliv}[due=2,id=website,nature=O,dissem=PU,miles=kickoff]
+ {Set-up of the Project web server}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=8,id=ws1proc,nature=R,dissem=PU,miles={kickoff}]
+ {Proceedings of the first {\pn} Summer School.}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=9,id=dissem,nature=R,dissem=PP]
+ {Dissemination Plan}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=9,id=exploitplan,nature=R,dissem=PP,miles=exploitation]
+ {Scientific and Commercial Exploitation Plan}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=20,id=ws2proc,nature=R,dissem=PU,miles={exploitation}]
+ {Proceedings of the second {\pn} Summer School.}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=32,id=ss1proc,nature=R,dissem=PU,miles={exploitation}]
+ {Proceedings of the third {\pn} Summer School.}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=44,id=ws3proc,nature=R,dissem=PU,miles=exploitation]
+ {Proceedings of the fourth {\pn} Summer School.}
+ \end{wpdeliv}
+ \end{wpdelivs}
+\end{workpackage}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: wp-dissem.tex workpackage dissem efo fromto bazRM wpheadertable
+% LocalWords: wpobjectives wpdescription ldots wpdelivs wpdeliv ws1proc pn
+% LocalWords: exploitplan ws2proc ss1proc ws3proc pdataRef deliv
+% LocalWords: mansubsusintReport
diff --git a/macros/latex/contrib/proposal/eu/strep/wp-management.tex b/macros/latex/contrib/proposal/eu/strep/wp-management.tex
new file mode 100644
index 0000000000..4ee5c645d3
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/wp-management.tex
@@ -0,0 +1,61 @@
+\begin{workpackage}[id=management,type=MGT,wphases=0-24!.2,
+ title=Project Management,short=Management,
+ jacuRM=2,barRM=2,efoRM=2,bazRM=2]
+We can state the state of the art and similar things before the summary in the boxes
+here.
+\wpheadertable
+\begin{wpobjectives}
+ \begin{itemize}
+ \item To perform the administrative, scientific/technical, and financial
+ management of the project
+ \item To co-ordinate the contacts with the EU
+ \item To control quality and timing of project results and to resolve conflicts
+ \item To set up inter-project communication rules and mechanisms
+ \end{itemize}
+\end{wpobjectives}
+
+\begin{wpdescription}
+ Based on the Consortium Agreement, i.e. the contract with the European Commission, and
+ based on the financial and administrative data agreed, the project manager will carry
+ out the overall project management, including administrative management. A project
+ quality handbook will be defined, and a {\pn} help-desk for answering questions about
+ the format (first project-internal, and after month 12 public) will be established. The
+ project management will\ldots we can even reference deliverables:
+ \delivref{management}{report2} and even the variant with a title:
+ \delivtref{management}{report2}
+\end{wpdescription}
+
+\begin{wpdelivs}
+ \begin{wpdeliv}[due=1,id=mailing,nature=O,dissem=PP,miles=kickoff]
+ {Project-internal mailing lists}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=3,id=handbook,nature=R,dissem=PU,miles=consensus]
+ {Project management handbook}
+ \end{wpdeliv}
+\begin{wpdeliv}[due={6,12,18,24,30,36,42,48},id=report2,nature=R,dissem=public,miles={consensus,final}]
+ {Periodic activity report}
+ Partly compiled from activity reports of the work package
+ coordinators; to be approved by the work package coordinators before delivery to the
+ Commission. Financial reporting is mainly done in months 18 and 36.\Ednote{how about
+ these numbers?}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=6,id=helpdesk,dissem=PU,nature=O,miles=kickoff]
+ {{\pn} Helpdesk}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=36,id=report6,nature=R,dissem=PU,miles=final]
+ {Final plan for using and disseminating the knowledge}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=48,id=report7,nature=R,dissem=PU,miles=final]
+ {Final management report}
+ \end{wpdeliv}
+\end{wpdelivs}
+\end{workpackage}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: wp-management.tex workpackage efoRM bazRM wpheadertable pn ldots
+% LocalWords: wpobjectives wpdescription delivref delivtref wpdelivs wpdeliv
+% LocalWords: dissem Ednote pdataRef deliv mansubsusintReport wphases
diff --git a/macros/latex/contrib/proposal/eu/strep/wp-temple.tex b/macros/latex/contrib/proposal/eu/strep/wp-temple.tex
new file mode 100644
index 0000000000..92426deaf6
--- /dev/null
+++ b/macros/latex/contrib/proposal/eu/strep/wp-temple.tex
@@ -0,0 +1,44 @@
+\begin{workpackage}[id=temple,type=DEM,lead=bar,
+ wphases=6-12!1,
+ title={\pn} Proposal Template,short=Template,barRM=6,bazRM=6]
+We can state the state of the art and similar things before the summary in the boxes
+here.
+\wpheadertable
+
+\begin{wpobjectives}
+ To develop a template file for {\pn} proposals
+\end{wpobjectives}
+
+\begin{wpdescription}
+ We abstract an example from existing proposals
+\end{wpdescription}
+
+\begin{wpdelivs}
+ \begin{wpdeliv}[due=6,id=req,nature=R,dissem=PP,miles=kickoff]
+ {Requirements analysis}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=12,id=spec,nature=R,dissem=PU,miles=consensus]
+ {{\pn} Specification }
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=18,id=demonstrator,nature=D,dissem=PU,miles={consensus,final}]
+ {First demonstrator ({\tt{article.cls}} really)}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=24,id=proto,nature=P,dissem=PU,miles=final]
+ {First prototype}
+ \end{wpdeliv}
+ \begin{wpdeliv}[due=36,id=release,nature=P,dissem=PU,miles=final]
+ {Final Template, ready for release}
+ \end{wpdeliv}
+\end{wpdelivs}
+Furthermore, this work package contributes to {\pdataRef{deliv}{managementreport2}{label}} and
+{\pdataRef{deliv}{managementreport7}{label}}.
+\end{workpackage}
+
+%%% Local Variables:
+%%% mode: LaTeX
+%%% TeX-master: "propB"
+%%% End:
+
+% LocalWords: wp-temple.tex workpackage fromto pn bazRM wpheadertable wpdelivs
+% LocalWords: wpobjectives wpdescription wpdeliv req dissem tt article.cls
+% LocalWords: pdataRef deliv systemsintReport