diff options
author | Karl Berry <karl@freefriends.org> | 2015-11-23 23:03:44 +0000 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2015-11-23 23:03:44 +0000 |
commit | a30f052f895d1f1fd9f112c555d360a2f5845929 (patch) | |
tree | 75e851693ac839f7510674f192badb317e43d87b /Master/texmf-dist/doc/latex/proposal/dfg | |
parent | 17317dd1f84901e202fb95e31a0eee9c51e50d74 (diff) |
proposal (23nov15)
git-svn-id: svn://tug.org/texlive/trunk@38923 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/latex/proposal/dfg')
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/dfgproposal.pdf | bin | 279618 -> 246265 bytes | |||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/Makefile | 74 | ||||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/funds.tex | 81 | ||||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/preconditions.tex | 104 | ||||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/proposal.tex | 98 | ||||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/public.pdf | bin | 0 -> 109019 bytes | |||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/public.tex | 7 | ||||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/state.tex | 59 | ||||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/submit.pdf | bin | 0 -> 97709 bytes | |||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/submit.tex | 7 | ||||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/workplan.tex | 215 | ||||
-rw-r--r-- | Master/texmf-dist/doc/latex/proposal/dfg/proposal/zusammenfassung.tex | 20 |
12 files changed, 665 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/dfgproposal.pdf b/Master/texmf-dist/doc/latex/proposal/dfg/dfgproposal.pdf Binary files differindex 3feea998f21..fe2aee6b1f3 100644 --- a/Master/texmf-dist/doc/latex/proposal/dfg/dfgproposal.pdf +++ b/Master/texmf-dist/doc/latex/proposal/dfg/dfgproposal.pdf diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/Makefile b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/Makefile new file mode 100644 index 00000000000..44336c1ef7f --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/Makefile @@ -0,0 +1,74 @@ +########################################################################### +# 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 = proposal.tex # the proposal +BIB = ../lib/dummy.bib # bibTeX databases +PROP.dir = ../../.. +########################################################################### +# the following are computed +TARGET = $(PROPOSAL) # all pdflatex targets +TARGET.pdf = $(TARGET:%.tex=%.pdf) # PDFs to be produced +TARGET.aux = $(TARGET:%.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 +BBL = $(PROPOSAL:%.tex=%.bbl) $(BBL.base:%=$(PROPOSAL:%.tex=%)%-blx.bbl) +PROPCLS.dir = $(PROP.dir)/base +PROPETC.dir = $(PROP.dir)/etc +DFGPROPCLS.dir = $(PROP.dir)/dfg +TEXINPUTS := .//:$(PROPCLS.dir)//:$(DFGPROPCLS.dir)//:$(PROPETC.dir)//: +BIBINPUTS := ../lib:$(BIBINPUTS) +PROPCLS.clssty = proposal.cls pdata.sty +PROPETC.sty = workaddress.sty metakeys.sty sref.sty +DFGPROPCLS.clssty = dfgproposal.cls dfgpdata.sty +PROPCLS = $(PROPCLS.clssty:%=$(PROPCLS.dir)/%) $(DFGPROPCLS.clssty:%=$(DFGPROPCLS.dir)/%) $(PROPETC.sty:%=$(PROPETC.dir)/%) + +all: $(TARGET.pdf) + +submit: + $(MAKE) -w PROPOSAL=submit.tex all + +public: + $(MAKE) -w PROPOSAL=public.tex all + +cd: # make cd will prepare CD for burning + mkdir CD;make $(TARGET.pdf); cp $(TARGET.pdf) CD + +bbl: $(BBL) +$(BBL): %.bbl: %.aux + bibtex -min-crossrefs=100 -terse $< + +$(PDATA): %.pdata: %.tex + $(PDFLATEX) $< + +$(TARGET.aux): %.aux: %.tex + $(PDFLATEX) $< + +$(TARGET.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 $(BIBINPUTS) diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/funds.tex b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/funds.tex new file mode 100644 index 00000000000..93faf326acf --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/funds.tex @@ -0,0 +1,81 @@ +\section{Requested Modules/Funds}\label{sec:funds} + +For each applicant, we apply for funding within the Basic Module. + +\subsection{Funding for Staff}\label{sec:positions} + +\subsubsection{Research Staff}\label{sec:positions:research} + +We apply for the following positions. All run over the entire duration of the proposed project. + +\paragraph*{Non-doctoral staff}\ednote{compute amount in elan and copy here} + +One doctoral researcher for 2 years at $100 \%$ for Michael Kohlhase. + +One doctoral researcher for 2 years at $100 \%$ for Florian Rabe. + +%\paragraph*{Postdoctoral staff} +%\ednote{postdoctoral researcher and comparable} + +\paragraph*{Other research assistants}\ednote{students with BSc.} + +One student with BSc. for 2 years at $100 \%$ for Michael Kohlhase. + +One student with BSc. for 2 years at $100 \%$ for Florian Rabe. + +\subsubsection{Non-Academic Staff \qquad None.} + +\subsubsection{Student Assistants \qquad None.} + +\subsection{Funding for Direct Project Costs}\label{sec;funds:direct} + +\subsubsection{Equipment up to 10,000 \texteuro, Software and Consumables} + +None. PC will cover the workspace, computing needs, and consumables for its staff as part +of the basic support. + +\subsubsection{Travel Expenses}\label{sec:travel} + +\begin{oldpart}{rework} + The travel budget shall cover: + \begin{itemize} + \item visits to external collaborators. We expect two international visits. We estimate + that each visit will be most effective, if the junior researchers can spend about 3 + weeks with the partners. Thus we estimate 2500 {\texteuro} per visit. + \item visits to national conferences to disseminate the results of {\pn}. We expect + one visit for each year for each of the three researchers. (3 x 3 x 1000 {\texteuro}) + \item visits to international conferences to disseminate the results of {\pn}. These + are in particular the International Joint Conference on Document Engineering (DocEng) + and the Tech User Group Meeting (TUG). We expect one visit for each proposed + researcher and for each year. (3 x 3 x 1500 {\texteuro}) + \end{itemize} + + This sums up to a total amount of 32.500 {\texteuro} for travel expenses for the whole + funding period of three years which is split into 16.250 {\texteuro} for each institute + (PC and Jacobs University). +\end{oldpart} + +\subsubsection{Visiting Researchers}\label{sec:funds:visiting} + +Total expenses \textbf{10.200 \texteuro} +\medskip + +As explained in Section~\ref{sec:travel}, we expect 5 incoming research visits. Assuming +an average duration of 3 weeks, we estimate the cost of one visit at 600 {\texteuro} for +traveling and 70 {\texteuro} per night for accommodation, amounting to 2040 \texteuro per +visit. + +\subsubsubsection{-- 4.1.2.6, 4.1.3 (Expenses for Laboratory Animals / Other Costs +/ Project Related Publication Expenses / Instrumentation) \sf\qquad n/a} + +% \subsubsection{Expenses for Laboratory Animals} None. +% \subsubsection{Other Costs} None. +% \subsubsection{Project-Related Publication Expenses} None. +% \subsection{Funding for Instrumentation} None. + +%%% Local Variables: +%%% mode: LaTeX +%%% TeX-master: "proposal" +%%% End: + +% LocalWords: ipower texteuro diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/preconditions.tex b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/preconditions.tex new file mode 100644 index 00000000000..7f4e82c5c3d --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/preconditions.tex @@ -0,0 +1,104 @@ +\section{Project Requirements}\label{sec:requirements} + +\subsection{Employment Status Information}\label{sec:req:employment-status} + +\begin{todo}{from the proposal template} + For each applicant, state the last name, first name, and employment status (including + duration of contract and funding body, if on a fixed-term contract). +\end{todo} + +\subsection{First-time Proposal Data}\label{sec:req:first} + +\begin{todo}{from the proposal template} + Only if applicable: Last name, first name of first-time applicant. + + If this is your first proposal, reviewers will consider this fact when assessing your + pro- posal. Previous proposals for research fellowships, publication funding, travel + allow- ances, or funding for scientific networks are not considered first proposals. If + you are submitting a “first-time proposal” and it is part of a joint proposal, please + note that your independent project must be distinct from the other projects. + + If you have already submitted a proposal as an applicant for a research grant and have + received a letter informing you of the funding decision, or if you have led an independ- + ent junior research group or project in a Collaborative Research Centre or Research + Unit, you are no longer eligible to submit a “first proposal”. If you have submitted a + “first-time proposal” and it was rejected, you may resubmit the application, in revised + form, as a first-time proposal for the same project. +\end{todo} + +\subsection{Composition of the Project Group}\label{sec:req:group} + +\begin{todo}{from the proposal template} + List only those individuals who will work on the project but will not be paid out of the + project funds. State each person’s name, academic title, employment status, and type of + funding. + + Please list separately the individuals paid by your institution and those paid using + other third-party funding (including fellowships). +\end{todo} + +\begin{sitedescription}{jacu} + The KWARC (Knowledge Adaptation and Reasoning for Content) research group headed by + Michael Kohlhase for has the following members + \begin{compactdesc} + \item[Dr. N.N.] is the \ldots She has a background in\ldots. + \end{compactdesc} + Additionally, the group has attracted about 10 undergraduate and master's students that + actively take part in the project work and various aspects of research. +\end{sitedescription} + +\begin{sitedescription}{pcg} + Power Consulting GmbH is the leading provider of semantic document solutions. Dr. Senior + Researcher leads an applied research group consisting of + \begin{compactdesc} + \item[Dr. N.N.] is the \ldots She has a background in\ldots. + \end{compactdesc} + The group has access to seven programming slaves specializing in web development and + document transformation techniques +\end{sitedescription} + + +\subsection{Cooperation with other Researchers}\label{sec:coop} + +\subsubsection{Planned Cooperations}\label{sec:coop:planned} +\begin{todo}{from the proposal template} + Researchers with whom you have agreed to cooperate on this project +\end{todo} +\begin{compactdesc} +\item[Prof. Dr. Super Akquisiteur (Uni Paderborn)] knows exactly what to do to get funding + with DFG, we will interview him closely and integrate all his intuitions into the {\pn} + templates. +\item[Prof. Dr. Habe Nichts (Uni Hinterpfuiteufel)] has never gotten a grant proposal + through with DFG, we will try to avoid his mistakes. +\item[Dr. Sach Bearbeiter (DFG)] will consult with the DFG requirements to be met in the + proposals. +\item[Dr. Donald Knuth (Stanford University)] is so surprised that we want to do grant + proposals in {\TeX/\LaTeX} that he will help us with any problems we have in coding in + this wonderful programming language. +\end{compactdesc} + +\subsubsection{Scientific Collaborations in the past Three Years}\label{sec:past-coop} + +\begin{todo}{from the proposal template} + Researchers with whom you have collaborated scientifically within the past three years + + This information will assist the DFG’s Head Office in avoiding potential conflicts of + in- terest during the review process. +\end{todo} + +\subsection{Scientific Equipment}\label{sec:req:equipment} + +Jacobs University provides laptops or desktop workstations for all academic +employees. Great Consulting GmbH. is rolling in money anyways and has all of the latest +gadgets. + + +\subsection{Project-Relevant Interests in Commercial Enterprises\qquad n/a} + +%%% Local Variables: +%%% mode: LaTeX +%%% TeX-master: "proposal" +%%% End: + +% LocalWords: Durchf uhrung subsubsection ipower Hinterpfuiteufel Sach Aktivit +% LocalWords: Erkl arungen diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/proposal.tex b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/proposal.tex new file mode 100644 index 00000000000..e586fc2461c --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/proposal.tex @@ -0,0 +1,98 @@ +% 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[RAM,gitinfo\classoptions]{dfgproposal} +\addbibresource{../lib/dummy} +\usepackage[utf8]{inputenc} +\input{../lib/WApersons} + + +\begin{document} + +\begin{center}\color{red}\huge + This mock proposal is just an example for \texttt{dfgproposal.cls} it reflects the + current DFG template valid from October 2011. +\end{center} + +\urldef{\gcpubs}\url{http://www.pcg.phony/~gc/pubs.html} +\urldef{\mikopubs}\url{http://kwarc.info/kohlhase/publications.html} +\begin{proposal}[PI=miko,PI=gc,site=jacu,site=pcg, + thema=Intelligentes Schreiben von Antr\"agen, + acronym={iPoWr}, + acrolong={\underline{I}ntelligent} {\underline{P}r\underline{o}posal} {\underline{Wr}iting}, + title=\pn: \protect\pnlong, + totalduration=3 years, + since=1. Feb 2009, + start=1. Feb. 2010, + months=24, + pcgRM=36, pcgRAM=36, jacuRM=36, jacuRAM=36, + discipline=Computer Science, + areas=Knowledge Management] + +\begin{Zusammenfassung} + \begin{todo}{in das Elan System kopieren} + Fassen Sie die relevanten Projektziele allgemeinverst''andlich in maximal 3000 Zeichen + (keine Sonderzeichen) zusammen + \end{todo} + Das Schreiben von Antr"agen ist ein kollaborativer Prozess in dem Betr"age von mehreren + Personen integriert werden mu"ussen. Ein ASCII-basiertes Format wie {\LaTeX} erlaubt die + Koordination dieses Prozesses mittels Versionsverwaltungssystemen wie + Subversion. Dadurch k''onnen sich die Antragsteller auf Inhalte konzentrieren anstatt + auf die Mechanik der Dokumentenverwaltung. +\end{Zusammenfassung} + +\begin{Summary} + \begin{todo}{copy into the Elan system} + Summarize the relevant goals of the proposed project in generally intelligible + terms. Do not use more than 3000 characters, no special characters allowed. + \end{todo} + 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. +\end{Summary} + +% It is often good to separate the top-level sections into separate files. +% Especially in collaborative proposals. We do this here. +\input{state} +\input{workplan} + +\section{Bibliography Concerning the State of the Art, the Research objectives, and the + Work Programme}\label{sec:bib} + +\begin{todo}{from the proposal template} +In this bibliography, list only the works you cite in your presentation of the state of the +art, the research objectives, and the work programme. This bibliography is not the list +of publications. Non-published works must be included with the proposal. +\end{todo} +\printbibliography[heading=empty,notcategory=featured] +% the following will not become part of the public proposal after all most of this is +% technical or confidential. +%\begin{private} +\input{funds} +\input{preconditions} + +\section{Additional Information}\label{sec:additional} + +Funding proposal XYZ-83282 has been submitted prior to this proposal on related topic XYZ. +\end{proposal} + +\end{document} + +%%% Local Variables: +%%% mode: LaTeX +%%% TeX-PDF-mode:t +%%% TeX-master: t +%%% End: + +% LocalWords: empty bibflorian systems rabe institutions modal historical pub +% LocalWords: kwarc till formalsafe miko gc ipower ipowerlong Antr agen Beitr + +% LocalWords: acrolong intellegible kollaboratives koh arenten ussen Proze pcg +% LocalWords: Versionsmanagementsystem textsc unterst utzt konzentieren stex +% LocalWords: mechanik workplan thispagestyle newpage Principcal cvpubsmiko pn +% LocalWords: ourpubs zusammenfassung printbibliography pubspage ntelligent +% LocalWords: iting pnlong diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/public.pdf b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/public.pdf Binary files differnew file mode 100644 index 00000000000..2c9e43abdba --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/public.pdf diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/public.tex b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/public.tex new file mode 100644 index 00000000000..00c95f15a35 --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/public.tex @@ -0,0 +1,7 @@ +\newcommand{\classoptions}{,submit,public} +\input{proposal} + +%%% Local Variables: +%%% mode: latex +%%% TeX-master: t +%%% End: diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/state.tex b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/state.tex new file mode 100644 index 00000000000..245c513b459 --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/state.tex @@ -0,0 +1,59 @@ +\section{State of the Art and Preliminary Work}\label{sec:state} +\begin{todo}{from the proposal guidelines} + For new proposals please explain briefly and precisely the state of the art in your + field in its direct relationship to your project. This description should make clear in + which context you situate your own research and in what areas you intend to make a + unique, innovative, promising contribution. This description must be concise and + understand- able without referring to additional literature. + + For renewal proposals, please report on your previous work. This report should also be + understandable without referring to additional literature. + + To illustrate and enhance your presentation you may refer to your own and others’ pub- + lications. Indicate whenever you are referring to other researchers’ work. Please list + all cited publications in your bibliography under section 3. This reference list is not + consid- ered your list of publications. Note that reviewers are not required to read any + of the works you cite. This also applies to review sessions that are held on site. In + this case, manuscripts and publications that provide more information on the progress + reports and are published up to the review panel’s meeting may be made available at the + meeting to enable reviewers to read through the information. Reviews will be based only + on the text of the actual proposal. +\end{todo} +\subsection{List of Project-Related Publications}\label{sec:projpapers} + +\begin{todo}{from the proposal template} + Please include a list of own publications that are related to the proposed project. It + serves as an important basis for assessing your proposal. The number of publications to + cite here is determined as follows: + \begin{compactdesc} + \item[Single applicant] two publications per year of the funding duration + \item[Multiple applicants] three publications per year of the funding duration + \end{compactdesc} + These rules refer to the proposed funding duration for new proposals and the completed + duration for renewal proposals. + + If you are submitting a proposal to the DFG for the first time and have therefore not + published in the proposed research area, please list the up to five most important + publications so far. +\end{todo} + +\subsubsection{Peer-Reviewed Articles} + +\dfgprojpapers{Kohlhase:pdpl10,providemore} + +\ednote{Anmerkung Jens: Ein nützliches Feature wäre hier, wenn das Paket eine (eventuell + über Optionen der Dokumentklasse unterdrückbare) Warnung ausgeben würde, wenn zu viele + Publikationen entsprechend DFG-Richtlinien angegeben werden. Die Anzahl ist sehr eng + begrenzt.} + +\subsubsection{Other Articles\qquad None.} +\subsubsection{Patents\qquad None.} + +%%% Local Variables: +%%% mode: LaTeX +%%% TeX-master: "proposal" +%%% End: + +% LocalWords: subsubsections dfgprojpapers pdpl10 providemore compactdesc +% LocalWords: ourpubs nociteprolist KohKoh ccbssmt09 KohRabZho tmlmrsca10 +% LocalWords: Hutter09 sifemp09 diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/submit.pdf b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/submit.pdf Binary files differnew file mode 100644 index 00000000000..9fee2535279 --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/submit.pdf diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/submit.tex b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/submit.tex new file mode 100644 index 00000000000..5d92f9374de --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/submit.tex @@ -0,0 +1,7 @@ +\newcommand{\classoptions}{submit} +\input{proposal} + +%%% Local Variables: +%%% mode: latex +%%% TeX-master: t +%%% End: diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/workplan.tex b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/workplan.tex new file mode 100644 index 00000000000..a68a3b553dd --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/workplan.tex @@ -0,0 +1,215 @@ +\section{Objectives and Work Programme}\label{sec:workplan} + +\subsection{Anticipated Total Duration of the Project}\label{sec:duration} + +\begin{todo}{from the proposal template} +Please state +\begin{itemize} + \item the project's intended duration 1 and how long DFG funds will be necessary, + \item for ongoing projects: since when the project has been active. +\end{itemize} +\end{todo} + +\subsection{Objectives}\label{sec:objectives} + +\begin{objective}[id=firstobj,title=Supporting Authors] + This is the first objective, after all we have to write proposals all the time, and we + would rather spend time on research. +\end{objective} + +\begin{objective}[id=secondobj,title=Supporting Reviewers] + They are only human too, so let's have a heart for them as well. +\end{objective} + + +\subsection{Work Programme Including Proposed Research Methods}\label{sec:wawp} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\LaTeX is the best document markup language, it can even be used for literate +programming~\cite{DK:LP,Lamport:ladps94,Knuth:ttb84} + +\begin{todo}{from the proposal template} + review the state of the art in the and your own contribution to it; probably you want to + divide this into subsubsections. +\end{todo} + +\begin{todo}{from the proposal template} +For each applicant + +Please give a detailed account of the steps planned during the proposed funding pe- +riod. (For experimental projects, a schedule detailing all planned experiments should +be provided.) + +The quality of the work programme is critical to the success of a funding proposal. The +work programme should clearly state how much funding will be requested, why the +funds are needed, and how they will be used, providing details on individual items +where applicable. + +Please provide a detailed description of the methods that you plan to use in the project: +What methods are already available? What methods need to be developed? What as- +sistance is needed from outside your own group/institute? +Please list all cited publications pertaining to the description of your work programme +in your bibliography under section 3. +\end{todo} + +The project is organized around \pdatacount{all}{wa} large-scale work areas which correspond +to the objectives formulated above. These are subdivided into \pdatacount{all}{wp} work +packages, which we summarize in Figure~\ref{fig:wplist}. Work area +\WAref{mansubsus} will run over the whole project\ednote{come up with a better + example, this is still oriented towards an EU project} duration of {\pn}. All +{\pdatacount{systems}{wp}} work packages in {\WAref{systems}} will and have to be +covered simultaneously in order to benefit from design-implementation-application feedback +loops. + +\wpfig + +\begin{workplan} +\begin{workarea}[id=mansubsus,title={Management, Support \& Sustainability}, short=Management] + This work-group corresponds to Objective \OBJref{firstobj} and has two work packages: + one for management proper ({\WPref{management}}), and one each for + dissemination ({\WPref{dissem}}) + + 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 ({\WPref{management}}), the Proceedings of the + Annual {\pn} Summer School as well as non-public Dissemination and Exploitation plans + ({\WPref{dissem}}), as well as a report of the {\pn} project milestones. + +\begin{workpackage}[id=management,lead=jacu, + title=Project Management, + jacuRM=2,jacuRAM=8,pcgRM=2] + Based on the ``Bewilligungsbescheid'' of the DFG, 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 consist of the following tasks +\begin{tasklist} +\begin{task}[id=foo,wphases=0-3,requires=\taskin{t1}{dissem}] + To perform the administrative, scientific/technical, and financial management of the + project +\end{task} +\begin{task}[wphases=13-17!.5] + To co-ordinate the contacts with the DFG and other funding bodies, building on the + results in \taskref{management}{foo} +\end{task} +\begin{task} + To control quality and timing of project results and to resolve conflicts +\end{task} +\begin{task} + To set up inter-project communication rules and mechanisms +\end{task} +\end{tasklist} + +\end{workpackage} + +\begin{workpackage}[id=dissem,lead=pcg, + title=Dissemination and Exploitation, +pcgRM=8,jacuRAM=2] +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. + + + 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. + + \begin{tasklist} + \begin{task}[id=t1,wphases=6-7] + sdfkj + \end{task} + \begin{task}[wphases=12-13] + sdflkjsdf + \end{task} + \begin{task}[wphases=18-19] + sdflkjsdf + \end{task} + \begin{task}[wphases=22-24] + \end{task} +\end{tasklist} + +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{workpackage} +\end{workarea} + + +\begin{workarea}[id=systems,title={System Development}] + This workarea does not correspond to \OBJtref{secondobj}, but it has two work packages: + one for the development of the {\LaTeX} class ({\WPref{class}}), and for the + proposal template ({\WPref{temple}}) + + This work group coordinates the system development. + +\begin{workpackage}[id=class,lead=jacu, + title=A LaTeX class for EU Proposals,short=Class, + jacuRM=12,jacuRAM=8,pcgRM=12,pcgRAM=2] +We plan to develop a {\LaTeX} class for marking up EU Proposals + +We will follow strict software design principles, first comes a +requirements analys, then \ldots +\begin{tasklist} + \begin{task}[wphases=0-2] + sdfsdf + \end{task} + \begin{task}[wphases=4-8] + sdfsdf + \end{task} + \begin{task}[id=t3,wphases=10-14] + sdfsdf + \end{task} + \begin{task}[wphases=20-24] + sdfsdfd + \end{task} +\end{tasklist} +\end{workpackage} + +\begin{workpackage}[id=temple,lead=pcg, + title= Proposal Template,short=Template,jacuRM=12] + +We plan to develop a template file for {\pn} proposals + +We abstract an example from existing proposals +\begin{tasklist} + \begin{task}[wphases=6-12] + sdfdsf + \end{task} + \begin{task}[id=temple2,wphases=18-24,requires=\taskin{t3}{class}] + sdfsdf + \end{task} +\end{tasklist} +\end{workpackage} + +\begin{workpackage}[id=workphase,title=A work package without tasks, + wphases=0-4!.5] + + And finally, a work package without tasks, so we can see the effect on the gantt chart + in fig~\ref{fig:gantt}. +\end{workpackage} +\end{workarea} +\end{workplan} + +\ganttchart[draft,xscale=.45] + +\subsection{Data Handling}\label{sec:data} + +The \pn project will not systematically produce researchdata. All project results will be +published for at least $x$ years at our archive at \url{http://example.org}. + +\subsection{-- 2.7 (Other Information / Explanations on the Proposed Investigations / Information on Scientific and Financial Involvement of International + Cooperation Partners) \qquad \sf n/a} + + +%%% Local Variables: +%%% mode: LaTeX +%%% TeX-master: "proposal" +%%% End: + +% LocalWords: workplan.tex wplist dfgcount wa mansubsus duratio ipower wpfig +% LocalWords: ganttchart xscale workplan workarea pdataref dissem workpackage foo +% LocalWords: tasklist taskin taskref sdfkj sdflkjsdf sdfsdf sdfsdfd sdfdsf pn +% LocalWords: firstobj secondobj pdatacount WAref ednote OBJref pcgRM pcg +% LocalWords: ldots OBJtref workphase diff --git a/Master/texmf-dist/doc/latex/proposal/dfg/proposal/zusammenfassung.tex b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/zusammenfassung.tex new file mode 100644 index 00000000000..ca39d955195 --- /dev/null +++ b/Master/texmf-dist/doc/latex/proposal/dfg/proposal/zusammenfassung.tex @@ -0,0 +1,20 @@ +\begin{Abriss} +\begin{todo}{from the proposal template} + Fassen Sie hier bitte die wesentlichen Ziele Ihres Vorhabens allgemeinverständlich und + in nicht mehr als 15 Zeilen (max. 1600 Zeichen) zusammen. +\end{todo} +Das Schreiben von Antr"agen ist oft ein kollaboratives Unterfangen in dem Beitr"age von +mehren Partnern in einen koh"arenten Text integriert werde m"ussen. Durch die Verwendung +eines ASCII-basierten Formates wie {\LaTeX} kann dieser Proze"s in einem +Versionsmanagementsystem wie {\textsc{Subversion}} unterst"utzt werden, wodurch sie das +Projektteam auf das Schreiben konzentrieren kann statt auf die Mechanik der Integration. +\end{Abriss} +%% Local Variables: +%%% mode: LaTeX +%%% TeX-master: "proposal" +%%% End: + +% LocalWords: ngerman zusammenfassung popul Komplexit eingef uhrt aquate utzen +% LocalWords: unterst pn inparaenum Anderungsmanagement zug onnen zugh erm koh +% LocalWords: oglichen Antr agen kollaboratives Beitr arenten ussen Proze utzt +% LocalWords: Versionsmanagementsystem |