changing line endings to the ones preferred by CTAN
This commit is contained in:
Michael Kohlhase
parent
5b8a8a37e3
commit
2652cde86e
@ -1,40 +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
|
||||
\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
|
||||
|
||||
@ -1,103 +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
|
||||
\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
|
||||
|
||||
@ -1,40 +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
|
||||
\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
|
||||
|
||||
@ -1,14 +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:
|
||||
|
||||
\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:
|
||||
|
||||
|
||||
@ -1,53 +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
|
||||
\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
|
||||
|
||||
@ -1,40 +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
|
||||
\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
|
||||
|
||||
@ -1,19 +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
|
||||
\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
|
||||
|
||||
Loading…
Reference in New Issue
Block a user