[ *** This list is for use by the OOR nsf-07061 team only - please do not share
or forward message without consent from the team! *** ] (01)
There is a Key Personnel document separate from the Project Description,
so I have split your writeup into the two documents. The Key Personnel
and Project Summary documents are attached. I am still working on the
Project Description. (01)
-- Ken (02)
On Tue, 4 Nov 2008, Obrst, Leo J. wrote: (03)
>
> [ *** This list is for use by the OOR nsf-07061 team only - please do not
>share or forward message without consent from the team! *** ]
>
> Ken,
>
> Yes, the change of title to "senior project participant" would work.
>
> As long as something like the following is said up-front, you can keep
> the bio and the description of potential MITRE activities (though these
> are aspects of activities and should not be considered actual
> deliverables: there's too much, and so I amend it below):
>
>
> "If the proposal is funded, MITRE would be requested on a
> non-competitive basis to provide expertise in tools development and
> standards interoperability to support services needed by the
> repository. The tools will allow researchers to more easily evaluate,
> modularize, map/align, and support efficient runtime reasoning over
> ontologies and instance data, and support orchestration and
> optimization of services. In the public interest, all MITRE work
> (tools, standards, and other products) would be made publicly
> available. Northeastern University would be the lead proposer; MITRE
> and others would be subawardees through Northeastern University.
> MITRE's participation is subject to the approval of our primary
> government sponsor, OSD NII (Office of Secretary of Defense, Networks
> and Information Integration)."
>
>
> I would modify our section in the project description to:
>
> Leo Obrst will lead a subcontract at MITRE. The MITRE sub-team will
> address a number of aspects relevant to an OOR, and assist other
> contributors in realizing tools that cover these aspects. These aspects
> are the following:
>
> 1. Ontology Evaluation. The development of methods, practices,
> services, and artifacts to support
> automated and human reviewed evaluation and comparison of ontologies
> stored in the
> repository. [35, 45, 44]
> 2. Ontology Architectures, Modularization, and Alignment/Mapping. The
> development of requisite
> ontology-based architectures, including ontology lifecycle management,
> theories and implementations
> of ontology modularity, upper and middle ontologies, and research and
> software
> development of methods for automatically and semi-automatically
> aligning and mapping ontologies.
> The use and linking of metadata, controlled vocabularies, and
> ontologies, for intelligent
> search and decision support. [14, 42, 47, 63, 65, 64]
> 3. Ontology, Instance, and Rule Reasoning. The development and
> implementation of efficient logic
> programming-based reasoning methods that amalgamate Semantic Web-based
> ontologies and
> rules with extended Prolog and Answer Set Programming, to be used for
> reasoning over the
> ontologies, instances, and rules of the repository. [56, 55, 67]
> 4. Service Orchestration and Optimization to Support OOR Artifacts.
> Design and implementation
> of service-oriented architectures and services, including automated and
> semi-automated service
> orchestration and parallel optimization to support the repository. [40,
> 52, 68]
> 5. Outreach to communities in bioinformatics, national command and
> control, and intelligence.
> [37, 36, 34, 48, 46, 50, 63, 66, 67, 68]
>
>
> I hope this helps. Comments/suggestions welcomed!
>
> Thanks,
> Leo
> _____________________________________________
> Dr. Leo Obrst The MITRE Corporation, Information Semantics
> lobrst@xxxxxxxxx Information Discovery & Understanding, Command and
> Control Center
> Voice: 703-983-6770 7515 Colshire Drive, M/S H305
> Fax: 703-983-1379 McLean, VA 22102-7508, USA
>
>
> -----Original Message-----
> From: oor-nsf07601-bounces@xxxxxxxxxxxxxxxx
> [mailto:oor-nsf07601-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Ken
> Baclawski
> Sent: Tuesday, November 04, 2008 11:47 AM
> To: oor-nsf07601
> Subject: Re: [oor-nsf07601] NEW: MITRE participation on the
> pre-proposal
>
>
> [ *** This list is for use by the OOR nsf-07061 team only - please do
> not share or forward message without consent from the team! *** ]
>
> Can I list you in the capacity of senior personnel (or to use the
> proper
> term "senior project participant")? This will allow the inclusion of
> your
> biosketch. The wording you have given below could be included in the
> Current and Pending Support section which requires that the proposal
> "Address any potential overlap between the federally funded projects
> that
> are listed and the proposed DataNet activities."
>
> -- Ken
>
> On Mon, 3 Nov 2008, Obrst, Leo J. wrote:
>
>>
>> [ *** This list is for use by the OOR nsf-07061 team only - please do
> not share or forward message without consent from the team! *** ]
>>
>> Folks,
>>
>> The word I get is the following:
>>
>>
>> "We are not allowed to compete for work, and we are not to help any
>> organization be more competitive.
>>
>> All the work that we do for an organization outside the DoD must be
>> approved by our primary DoD sponsor ...
>>
>> If there is a proposal that is attempting to compete for grant
>> funding, you should not be indicated as a co-PI, and the proposal
>> should not include any information from or about us that is not in
>> the public domain; i.e., any organization could have submitted it --
>> there's no special advantage to this one.
>>
>> An organization could state an intent to work with us or have support
>> from us if awarded a grant, but it must be subject to our agreement
>> and approval of our primary DoD FFRDC sponsor.
>>
>> Does this help?
>>
>> The restrictions on us have to do with our privileged role in support
>> of the government."
>>
>>
>> So, it looks like all I may be able to contribute is:
>>
>> "An organization could state an intent to work with us or have
> support
>>
>> from us if awarded a grant, but it must be subject to our agreement
>> and approval of our primary DoD FFRDC sponsor."
>>
>> The wording also needs to make clear that the reason MITRE is
>> participating is that it is in the public interest because ... [to be
>> continued].
>>
>> However, please wait for a few bits and I'll provide you some
> verbiage:
>> which, by the way, always sounds like rotting words, to me, like the
>> evolution of Galactese after several million years of Galactic
> Empire.
>>
>> Thanks and apologies,
>> Leo
>> _____________________________________________
>> Dr. Leo Obrst The MITRE Corporation, Information Semantics
>> lobrst@xxxxxxxxx Information Discovery & Understanding, Command
> and
>> Control Center
>> Voice: 703-983-6770 7515 Colshire Drive, M/S H305
>> Fax: 703-983-1379 McLean, VA 22102-7508, USA
>>
>>
>> -----Original Message-----
>> From: oor-nsf07601-bounces@xxxxxxxxxxxxxxxx
>> [mailto:oor-nsf07601-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Obrst,
> Leo
>> J.
>> Sent: Monday, November 03, 2008 4:59 PM
>> To: oor-nsf07601; bebargmeyer@xxxxxxx
>> Subject: Re: [oor-nsf07601] Contact Spreadsheet
>>
>>
>> [ *** This list is for use by the OOR nsf-07061 team only - please do
>> not share or forward message without consent from the team! *** ]
>>
>> Folks,
>>
>> I am still working through MITRE to see whether I can even actually
> be
>> listed on the pre-proposal. Sorry for the wrench in the works, but
> I've
>> heard different things. It may still be the case that I cannot be
>> listed as a participant in the pre-proposal. I hope to have this
>> question resolved very soon.
>>
>> Thanks,
>> Leo
>>
>> _____________________________________________
>> Dr. Leo Obrst The MITRE Corporation, Information Semantics
>> lobrst@xxxxxxxxx Information Discovery & Understanding, Command
> and
>> Control Center
>> Voice: 703-983-6770 7515 Colshire Drive, M/S H305
>> Fax: 703-983-1379 McLean, VA 22102-7508, USA
>>
>>
>> -----Original Message-----
>> From: oor-nsf07601-bounces@xxxxxxxxxxxxxxxx
>> [mailto:oor-nsf07601-bounces@xxxxxxxxxxxxxxxx] On Behalf Of
>> kgoodier@xxxxxxxxxxx
>> Sent: Monday, November 03, 2008 4:53 PM
>> To: bebargmeyer@xxxxxxx; oor-nsf07601
>> Subject: Re: [oor-nsf07601] Contact Spreadsheet
>>
>>
>> [ *** This list is for use by the OOR nsf-07061 team only - please do
>> not share or forward message without consent from the team! *** ]
>>
>>
>> _________________________________________________________________
>> Message Archives: http://ontolog.cim3.net/forum/oor-nsf07601/
>> Shared Files:
>> http://ontolog.cim3.net/file/community/project/OOR/nsf07601/
>> Wiki:
>>
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_Proposal
>> /Nsf_07601
>>
>> _________________________________________________________________
>> Message Archives: http://ontolog.cim3.net/forum/oor-nsf07601/
>> Shared Files:
> http://ontolog.cim3.net/file/community/project/OOR/nsf07601/
>> Wiki:
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_Proposal
> /Nsf_07601
>>
>
> _________________________________________________________________
> Message Archives: http://ontolog.cim3.net/forum/oor-nsf07601/
> Shared Files:
> http://ontolog.cim3.net/file/community/project/OOR/nsf07601/
> Wiki:
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_Proposal
> /Nsf_07601
>
> _________________________________________________________________
> Message Archives: http://ontolog.cim3.net/forum/oor-nsf07601/
> Shared Files: http://ontolog.cim3.net/file/community/project/OOR/nsf07601/
> Wiki:
>http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_Proposal/Nsf_07601
> (04)
roles.pdf
Description: Adobe PDF document
summary.pdf
Description: Adobe PDF document
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/oor-nsf07601/
Shared Files: http://ontolog.cim3.net/file/community/project/OOR/nsf07601/
Wiki:
http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_Proposal/Nsf_07601 (01)
|