diff options
Diffstat (limited to 'Master/texmf-dist/doc')
| -rw-r--r-- | Master/texmf-dist/doc/latex/euproposal/README | 13 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/latex/euproposal/euproposal.pdf | bin | 0 -> 161643 bytes | |||
| -rw-r--r-- | Master/texmf-dist/doc/latex/euproposal/propB.delivs | 39 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/latex/euproposal/propB.pdf | bin | 0 -> 156026 bytes | |||
| -rw-r--r-- | Master/texmf-dist/doc/latex/euproposal/propB.tex | 573 |
5 files changed, 625 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/latex/euproposal/README b/Master/texmf-dist/doc/latex/euproposal/README new file mode 100644 index 00000000000..d0e1b89917e --- /dev/null +++ b/Master/texmf-dist/doc/latex/euproposal/README @@ -0,0 +1,13 @@ +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 an +extensive example (a fake EU proposal; see the file propB.tex) that shows all elements in +action. + +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/euproposal + diff --git a/Master/texmf-dist/doc/latex/euproposal/euproposal.pdf b/Master/texmf-dist/doc/latex/euproposal/euproposal.pdf Binary files differnew file mode 100644 index 00000000000..4073a348ba1 --- /dev/null +++ b/Master/texmf-dist/doc/latex/euproposal/euproposal.pdf diff --git a/Master/texmf-dist/doc/latex/euproposal/propB.delivs b/Master/texmf-dist/doc/latex/euproposal/propB.delivs new file mode 100644 index 00000000000..109c289c743 --- /dev/null +++ b/Master/texmf-dist/doc/latex/euproposal/propB.delivs @@ -0,0 +1,39 @@ +\delivrable{6}{D0.1}{mansubsus:intReport}{partial}{report}{Integrative report.} +\delivrable{12}{D0.1}{mansubsus:intReport}{partial}{report}{Integrative report.} +\delivrable{18}{D0.1}{mansubsus:intReport}{partial}{report}{Integrative report.} +\delivrable{24}{D0.1}{mansubsus:intReport}{partial}{report}{Integrative report.} +\delivrable{30}{D0.1}{mansubsus:intReport}{partial}{report}{Integrative report.} +\delivrable{36}{D0.1}{mansubsus:intReport}{partial}{report}{Integrative report.} +\delivrable{42}{D0.1}{mansubsus:intReport}{partial}{report}{Integrative report.} +\delivrable{48}{D0.1}{mansubsus:intReport}{partial}{report}{Integrative report.} +\delivrable{1}{D0.1.1}{management:mailing}{project}{infra}{Project-internal mailing lists} +\delivrable{3}{D0.1.2}{management:handbook}{public}{report}{Project management handbook} +\delivrable{6}{D0.1.3}{management:report2}{public}{report}{Periodic management report} +\delivrable{12}{D0.1.3}{management:report2}{public}{report}{Periodic management report} +\delivrable{18}{D0.1.3}{management:report2}{public}{report}{Periodic management report} +\delivrable{24}{D0.1.3}{management:report2}{public}{report}{Periodic management report} +\delivrable{30}{D0.1.3}{management:report2}{public}{report}{Periodic management report} +\delivrable{36}{D0.1.3}{management:report2}{public}{report}{Periodic management report} +\delivrable{42}{D0.1.3}{management:report2}{public}{report}{Periodic management report} +\delivrable{6}{D0.1.4}{management:helpdesk}{public}{infra}{{{\sc {iPoWr}}} Helpdesk} +\delivrable{36}{D0.1.5}{management:report6}{public}{report}{Final plan for using and disseminating the knowledge} +\delivrable{48}{D0.1.6}{management:report7}{public}{report}{Final management report} +\delivrable{2}{D0.2.1}{dissem:website}{public}{infra}{Set-up of the Project web server} +\delivrable{8}{D0.2.2}{dissem:ws1proc}{public}{report}{Proceedings of the first {{\sc {iPoWr}}} Summer School.} +\delivrable{9}{D0.2.3}{dissem:dissem}{project}{report}{Dissemination Plan} +\delivrable{9}{D0.2.4}{dissem:exploitplan}{project}{report}{Scientific and Commercial Exploitation Plan} +\delivrable{20}{D0.2.5}{dissem:ws2proc}{public}{report}{Proceedings of the second {{\sc {iPoWr}}} Summer School.} +\delivrable{32}{D0.2.6}{dissem:ss1proc}{public}{report}{Proceedings of the third {{\sc {iPoWr}}} Summer School.} +\delivrable{44}{D0.2.7}{dissem:ws3proc}{public}{report}{Proceedings of the fourth {{\sc {iPoWr}}} Summer School.} +\delivrable{30}{D1.1}{systems:intReport}{public}{report}{Integration report.} +\delivrable{48}{D1.2}{systems:finalReport}{public}{report}{Final report.} +\delivrable{6}{D1.1.1}{class:req}{project}{report}{Requirements analysis} +\delivrable{12}{D1.1.2}{class:spec}{public}{report}{{{\sc {iPoWr}}} Specification } +\delivrable{18}{D1.1.3}{class:demonstrator}{public}{software}{First demonstrator ({\tt {article.cls}} really)} +\delivrable{24}{D1.1.4}{class:proto}{public}{software}{First prototype} +\delivrable{36}{D1.1.5}{class:release}{public}{software}{Final {\LaTeX } class, ready for release} +\delivrable{6}{D1.2.1}{temple:req}{project}{report}{Requirements analysis} +\delivrable{12}{D1.2.2}{temple:spec}{public}{report}{{{\sc {iPoWr}}} Specification } +\delivrable{18}{D1.2.3}{temple:demonstrator}{public}{software}{First demonstrator ({\tt {article.cls}} really)} +\delivrable{24}{D1.2.4}{temple:proto}{public}{software}{First prototype} +\delivrable{36}{D1.2.5}{temple:release}{public}{software}{Final Template, ready for release} diff --git a/Master/texmf-dist/doc/latex/euproposal/propB.pdf b/Master/texmf-dist/doc/latex/euproposal/propB.pdf Binary files differnew file mode 100644 index 00000000000..71bbaa4b1d6 --- /dev/null +++ b/Master/texmf-dist/doc/latex/euproposal/propB.pdf diff --git a/Master/texmf-dist/doc/latex/euproposal/propB.tex b/Master/texmf-dist/doc/latex/euproposal/propB.tex new file mode 100644 index 00000000000..cd051978ab4 --- /dev/null +++ b/Master/texmf-dist/doc/latex/euproposal/propB.tex @@ -0,0 +1,573 @@ +\documentclass[11pt,eudraft,twoside]{euproposal} +\usepackage{wrapfig,rotating} +\usepackage{a4wide} +\usepackage{xspace} +\usepackage{paralist} +\usepackage{times} + +\def\ipower{{\sc{iPoWr}}} +\ProposalAcronym\ipower +\ProposalTitle{{\underline{I}ntellitent} {\underline{P}r\underline{o}sal} {\underline{Wr}iting}} +\ProposalCall{ICT Call 1: FP7-???-200?-?} +\ProposalInstrument{Large-scale Integrating Project (IP) Proposal} +\ProposalTopics{???-200?.?.? Intelligent Proposal Writing} +\ProposalCoordinatorName{Prof. Dr. Michael Kohlhase} +\ProposalCoordinatorEmail{m.kohlhase@jacobs-university.de} +\ProposalCoordinatorTelFax{(+49) 421 200-3140/-493140} + +\ProposalCoordinator{JACU}{Jacobs University Bremen}{D} +\ProposalPartner{EFO}{European Future Office}{NL} +\ProposalPartner{BAR}{Universit\`e de BAR}{F} +\ProposalPartner{BAZ}{BAZ International Ltd}{UK} + +\begin{document} +\svnInfo $Id: propB.tex 13984 2007-11-04 14:50:45Z kohlhase $ +\svnKeyword $HeadURL: https://svn.kwarc.info/repos/kwarc/doc/macros/euproposal/propB.tex $ +\begin{titlepageabstract} + 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 + {\sc{Subversion}}, allowing the proposal writing team to concentrate on the contents + rather than the mechanics of wrangling with text fragments and revisions. +\end{titlepageabstract} +\setcounter{tocdepth}{1} +{\small\tableofcontents} +\setcounter{part}{2}% part B + +\chapter{Scientific and Technical Quality}\label{chap:quality} +\begin{todo} + Recommended length for the whole of Section 1 –-- twenty pages, not including the tables + in Section 1.3 +\end{todo} + + +\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} +\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} +\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 a 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. (Please note that your overall + approach to management will be described later, in Section 2). + + Please present your plans as follows: + \begin{enumerate} + \item Describe the overall strategy of the work plan. + \item Show the timing of the different WPs and their components (Gantt chart or similar). +\item Provide a detailed work description broken down into work packages: + \begin{description} + \item [Work package list] (please use table \ref{fig:wplist}); + \item [Deliverables list] (please use table \ref{}); + \item[Description of each work package] (please use table 1.3c) + \item [Summary effort tabl]e (1.3d) + \item [List of milestones] (please use table 1.3e) + \end{description} + \item Provide a graphical presentation of the components showing their + interdependencies (Pert diagram or similar) + \end{enumerate} + The number of work packages used must be appropriate es 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} + +\subsection{Work Planning}\label{sec:workplanning} +\begin{todo} + Give a short high-level introduction to how the work in the project should proceed, + explain Table~\ref{fig:wplist}. + + In the table below indicate one activity per 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. +\end{todo} + +\begin{figure}[ht]\centering +\begin{wptable} + \wgline{mansubsus}\wpline{management}\wpline{dissem}\hline + \wgline{systems}\wpline{class}\wpline{temple} +\end{wptable} +\caption{Work Groups and Packages}\label{fig:wplist} +\end{figure} + + + +\begin{figure}[ht] +\begin{footnotesize} +\begin{minipage}{\textwidth} +\begin{sideways} +\begin{tabular}{|l|l||llllllllllllllll|}\hline + WP & title & 1 & 4 & 7 & 10 & 13 & 16 & 19 & 22 & 25 & 28 & 31 & 34 & 37 & 40 & 43 & 46 \\\hline + \euRef{wp}{management}{number} & \euref{wp}{management}{short} & + \act{3}{kickoff \& SS1} & \pause{9} & \act{4}{exploitation} \\\hline + + \euRef{wp}{dissem}{number} & \euref{wp}{dissem}{short} & + \pause{6} & \act{1}{SS2} & \pause{3} & \act{1}{SS3} & \pause{3}& + \act{1}{SS4}& \pause{1}\\\hline\hline + + \euRef{wp}{class}{number} & \euref{wp}{class}{short} & + \act{2}{req} & \pause{2} &\act{4}{proto} &\pause{2} & \act{4}{deployment}\\\hline + + \euRef{wp}{class}{number} & \euref{wp}{class}{short} & + \pause{4} & \act{4}{proto} & \pause{4} & \act{4}{deployment}\\\hline +\end{tabular} +\end{sideways} +\hspace*{1cm} +%\includegraphics[angle=90,height=19.2cm]{../tables/staffeffort} +\end{minipage} +\end{footnotesize} +\caption{Overview Work Package Activities and Staff Involvement}\label{fig:activities} +\end{figure} +\ednote{add generation here} + +\subsubsection{Project 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 required 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. +\end{todo} + +The work in the {\ipower} project is structured by seven milestones, which coincide with +the project meetings in summer and fall (see Section~\ref{sec:outreach} for details). +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. +\def\milesfor#1{} +\begin{footnotesize} +\begin{longtable}{|l|l|l|p{5cm}|p{5cm}|}\hline + \# & Event & Mo. & Description & Means of Verification \\\hline + & \multicolumn{4}{p{14cm}|}{Workpackages involved}\\\hline\hline + \milestone{kickoff} & Kickoff & 1 + & Initial (Organizational) Project Infra\-structure + & Inspection \\\hline + & \multicolumn{4}{p{14cm}|}{\milesfor{kickoff}}\\\hline\hline + \milestone{consensus} & Consensus & 24 + & Consensus + & Inspection \\\hline + & \multicolumn{4}{p{14cm}|}{\milesfor{consensus}}\\\hline + \milestone{exploitation} & Exploitation & 36 + & Expl + & Inspection \\\hline + & \multicolumn{4}{p{14cm}|}{\milesfor{exploitation}}\\\hline\hline + \milestone{final} & Final & 48 + & Final Results + & Inspection \\\hline + & \multicolumn{4}{p{14cm}|}{\milesfor{final}}\\\hline\hline +\end{longtable} +\end{footnotesize} + +\newpage +\subsubsection{Work Packages}\label{sec:workpackages} + +\begin{workplan} +\begin{workgroup}[id=mansubsus,title={Management, Support \& Sustainability}, + short=Management,lead=JACU] + \begin{wgd} + \wpobjectives This work-group has two work packages: one for management proper + ({\euref{wp}{management}{label}}), and one each for dissemination + ({\euref{wp}{dissem}{label}})\\\hline + + \wpdescription This work group ensures the dissemination and creation of the periodic + integrative reports containing the periodic Project Management Report, the Project + Management Handbook, an Knowledge Dissemination Plan ({\euref{wp}{management}{label}}), + the Proceedings of the Annual {\ipower} Summer School as well as non-public + Dissermination and Exploitation plans ({\euref{wp}{dissem}{label}}), as well as a report + of the {\ipower} project milestones.\\\hline + +\begin{wgdelivs} + \wgdeliv[due={6,12,18,24,30,36,42,48},id=intReport,type=report, + dissem=partial, + miles={kickoff,final}] + {Integrative report.} +\end{wgdelivs}\\\hline\hline +\end{wgd} + + +\newpage +\begin{wpd}[id=management,type=MGT,duration=48,start=1,lead=JACU, + title=Project Management,short=Management, + JACU=2,BAR=2,EFO=2,BAZ=2] +\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} +\\\hline + +\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 {\ipower} help-desk for answering +questions about the format (first project-internal, and after month 12 public) will be +established. The project management will\ldots\\\hline + +\begin{wpdelivs} + \wpdeliv[due=1,id=mailing,type=infra,dissem=project,miles=kickoff] + {Project-internal mailing lists} + \wpdeliv[due=3,id=handbook,type=report,dissem=public,miles=consensus] + {Project management handbook} + \wpdeliv[due={6,12,18,24,30,36,42},id=report2,type=report,dissem=public,miles={consensus,final}] + {Periodic management report} + \wpdeliv[due=6,id=helpdesk,dissem=public,type=infra,miles=kickoff] + {{\ipower} Helpdesk} + \wpdeliv[due=36,id=report6,type=report,dissem=public,miles=final] + {Final plan for using and disseminating the knowledge} + \wpdeliv[due=48,id=report7,type=report,dissem=public,miles=final] + {Final management report} +\end{wpdelivs}\\\hline +Furthermore, this work package contributes to {\euRef{deliv}{mansubsusintReport}{label}} +with an Periodic Management Report, a Project Management Handbook, and a plan for using +and disseminating the project results.\\\hline +\end{wpd} + +\newpage +\begin{wpd}% +[id=dissem,type=RTD,duration=48,start=1,lead=EFO, + title=Dissemination and Exploitation,short=Dissem, + EFO=8,JACU=2,BAR=2,BAZ=2] + +\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. \\\hline + + +\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\\\hline + +\begin{wpdelivs} + \wpdeliv[due=2,id=website,type=infra,dissem=public,miles=kickoff] + {Set-up of the Project web server} + \wpdeliv[due=8,id=ws1proc,type=report,dissem=public,miles={kickoff}] + {Proceedings of the first {\ipower} Summer School.} + \wpdeliv[due=9,id=dissem,type=report,dissem=project] + {Dissemination Plan} + \wpdeliv[due=9,id=exploitplan,type=report,dissem=project,miles=exploitation] + {Scientific and Commercial Exploitation Plan} + \wpdeliv[due=20,id=ws2proc,type=report,dissem=public,miles={exploitation}] + {Proceedings of the second {\ipower} Summer School.} + \wpdeliv[due=32,id=ss1proc,type=report,dissem=public,miles={exploitation}] + {Proceedings of the third {\ipower} Summer School.} + \wpdeliv[due=44,id=ws3proc,type=report,dissem=public,miles=exploitation] + {Proceedings of the fourth {\ipower} Summer School.} +\end{wpdelivs}\\\hline + + +Furthermore, this work package contributes to {\euRef{deliv}{mansubsusintReport}{label}} +with the annual Proceedings of the {\ipower} Summer School and the (non-public) +Dissemination Plan as well as the (non-public) scientific and commercial Exploitation +Plan. \\\hline +\end{wpd} +\end{workgroup} +\newpage +\begin{workgroup}[id=systems,title={System Development},short=Systems,lead=JACU] + +\begin{wgd} + \wpobjectives This work-group has two work packages: one for the development of the + {\LaTeX} class ({\euref{wp}{class}{label}}), and for the proposal template + ({\euref{wp}{temple}{label}}) \\\hline + + \wpdescription This work group coordinates the system development.\\\hline + +\begin{wgdelivs} + \wgdeliv[due=30,id=intReport,type=report,dissem=public,miles={consensus}] + {Integration report.} + \wgdeliv[due=48,id=finalReport,type=report,dissem=public,miles={consensus}] + {Final report.} +\end{wgdelivs}\\\hline\hline +\end{wgd} + +\newpage +\begin{wpd}[id=class,type=MGT,duration=48,start=1,lead=JACU, + title=A {\LaTeX} class for EU Proposals,short=Class, + JACU=12,BAR=12] +\wpobjectives To devlop a {\LaTeX} class for marking up EU Proposals\\\hline + +\wpdescription We will follow strict software design principles, first comes a +requirements analys, then \ldots\\\hline + +\begin{wpdelivs} + \wpdeliv[due=6,id=req,type=report,dissem=project,miles=kickoff] + {Requirements analysis} + \wpdeliv[due=12,id=spec,type=report,dissem=public,miles=consensus] + {{\ipower} Specification } + \wpdeliv[due=18,id=demonstrator,type=software,dissem=public,miles={consensus,final}] + {First demonstrator ({\tt{article.cls}} really)} + \wpdeliv[due=24,id=proto,type=software,dissem=public,miles=final] + {First prototype} + \wpdeliv[due=36,id=release,type=software,dissem=public,miles=final] + {Final {\LaTeX} class, ready for release} +\end{wpdelivs}\\\hline +Furthermore, this work package contributes to {\euRef{deliv}{systemsintReport}{label}} and +{\euRef{deliv}{finalReport}{label}}.\\\hline +\end{wpd} + +\newpage +\begin{wpd}[id=temple,type=DEM,duration=48,start=1,lead=BAR, + title={\ipower} Proposal Template,short=Template,BAR=12,BAZ=24] + +\wpobjectives To develop a template file for {\ipower} proposals\\\hline +\wpdescription We abstract an example from existing proposals\\\hline + +\begin{wpdelivs} + \wpdeliv[due=6,id=req,type=report,dissem=project,miles=kickoff] + {Requirements analysis} + \wpdeliv[due=12,id=spec,type=report,dissem=public,miles=consensus] + {{\ipower} Specification } + \wpdeliv[due=18,id=demonstrator,type=software,dissem=public,miles={consensus,final}] + {First demonstrator ({\tt{article.cls}} really)} + \wpdeliv[due=24,id=proto,type=software,dissem=public,miles=final] + {First prototype} + \wpdeliv[due=36,id=release,type=software,dissem=public,miles=final] + {Final Template, ready for release} +\end{wpdelivs}\\\hline +Furthermore, this work package contributes to {\euRef{deliv}{systemsintReport}{label}} and +{\euRef{deliv}{finalReport}{label}}.\\\hline +\end{wpd} +\end{workgroup} +\newpage +\end{workplan} + +\subsection{Deliverables}\label{sec:delivrables} + +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:workplanning}) are printed in boldface to mark them. They integrate +contributions from multiple work packages. 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{10cm}} + +\ednote{here?} +\staffefforttable +\newpage +\chapter{Implementation}\label{chap:implementation} + +\section{Management Structure and Procedures}\label{chap:management} +\begin{todo}{from the proposal template} + Describe the organisational structure and decision-making mechanisms of the + project. Show how they are matched to the complexity and scale of the project. +\end{todo} + +The Project Management of {\ipower} 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{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 + organisation, the main tasks they have been attributed, and the previous experience + relevant to those tasks. Provide also a short profile of the staff members who will be + undertaking the work. +\end{todo} +\newpage +\begin{partnerdesc}{JACU} + Jacobs University is a new private research university patterned after the Anglo-Saxon + university system. The university was founded in 2000 and has an international student + body (ca. 1000 students from over 90 nations, admitted in a highly selective process). + + The KWARC (KnoWledge Adaptation and Reasoning for Content \url{http://kwarc.info}) Group + headed by {\emph{Prof. Dr. Michael Kohlhase}} specializes in knowledge representation + systems for mathematics, formal mathematics, natural language semantics and the semantic + web. It is the main center and lead implementor of the OMDoc (Open Mathematical + Document) representation format for knowledge representation in Mathematics. + + 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. +\end{partnerdesc} +\newpage +\begin{partnerdesc}{EFO} +The EFO is the world leader in futurology, \ldots +\end{partnerdesc} +\newpage +\begin{partnerdesc}{BAR} +The 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 host +gorgeous project meetings. +\end{partnerdesc} +\newpage +\begin{partnerdesc}{BAZ} +\ednote{add something here} +\end{partnerdesc} + +\newpage +\section{The {\ipower} 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} + +\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} + Recommended length for Section 2.4 – two pages + + In addition to the costs indicated on form A3 of the proposal, and the staff effort + shown in Section 1.3 above, please identify any other major costs (e.g. equipment). + Describe how the totality of the necessary resources will be mobilised, 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. +\end{todo} + +\subsection{Travel Costs and Consumables}\label{sec:travel-costs} +\subsection{Subcontracting Costs} +\subsection{Other Costs} + +\chapter{Impact}\label{chap:impact} +\ednote{Recommended length for the whole of Section 3 –-- ten pages} +\section{Expected Impact}\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 Exploitation of Project Results}\label{sec:outreach} + +\begin{todo}{from the proposal template} + Describe the measures you propose for the dissemination and/or exploitation of project + results, and the management of knowledge, of intellectual property, and of other + innovation-related activities arising from the project. +\end{todo} +\subsection{Dissemination} +\subsection{Exploitation} +\subsection{Management of Intellectual Property} +\subsection{Sustainability} + +\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} + +\bibliographystyle{alpha} +\bibliography{prop} +\ednotemessage +\end{document} + +% |