o the full grant proposal, so there's no
guessing about the project :-)
Cheers,
-hilmar
P.S. Apologies if this is inappropriate for this list. There are few
ways that I've been able to come up with to reach those who could be
qualified for this job. Pointers would be welcome.
This is an opening at Merck. I have known Mark personally for well over
a decade. He's truly great to work with, and he's building a team.
-hilmar
Original Message
Subject:Position open: Knowledge Integration Engineer
Date: Fri, 13 Feb 2015 10:00:18 -0500
From: Mar
Kim, Nanyang Technological University, Singapore
* Hiroaki Kitano, Okinawa Institute of Science and Technology Graduate
University, Japan
* Sebastian Koehler, Charite Medical University Berlin, Germany
* Hilmar Lapp, National Evolutionary Synthesis Center (NESCent), US
* Suzanna Lewis, Berkeley Lab
uate
University, Japan
* Sebastian Koehler, Charite Medical University Berlin, Germany
* Hilmar Lapp, National Evolutionary Synthesis Center (NESCent), US
* Suzanna Lewis, Berkeley Lab, US
* Yves Lussier, The University of Chicago, US
* Jong Park , KAIST, Korea
* Paul N. Schofield, University of Cambridge
Durham, NC, under the supervision of Hilmar Lapp and Todd Vision. The
postdoc will have the opportunity to take advantage of the expertise of a large
interdisciplinary team, including Dr. Paula Mabee (University of South Dakota),
Dr. Chris Mungall (Lawrence Berkeley National Lab) and Dr. Hong Cui
Carolina at Chapel Hill (UNC-CH) under the
supervision of Hilmar Lapp at NESCent and Dr. Todd Vision at UNC-CH.
The research will be in collaboration with Dr. Chris Mungall at
Lawrence Berkeley National Lab and Dr. Hong Cui at the University of
Arizona. The project also includes
ilmar
--
===
: Hilmar Lapp -:- Durham, NC -:- hlapp at drycafe dot net :
===
tute)
Nico Cellinese (University of Florida)
Karen Cranston (Field Museum of Natural History)
Hilmar Lapp (NESCent)
Sheldon McKay (Cold Spring Harbor Laboratory, iPlant Collaborative)
Enrico Pontelli (New Mexico State University)
* This announcement was sent to the following lists: evoldir, TDWG,
esult some of the BOSC
attendees might be interested in a life sciences semweb BOF, so
holding it one of the two days of BOSC is maybe worth considering.
-hilmar
--
===
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
hnology" stuff seems to attract
plenty of attention (maybe not as main talks, but as SIGs, BOFs,
posters and demos, plus of course there are all the technology
vendors with their booths)...
--
=======
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
IPNI, uBio, to name a few.
-hilmar
--
===
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
ral proxy server advertised to work in perpetuity.
We're pretty close to the latter.
-hilmar
--
=======
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
On Aug 25, 2007, at 1:02 PM, Eric Jain wrote:
Hilmar Lapp wrote:
Sure. But what about it should be in the LSID spec?
For the same reason the entire SOAP-based resolution stack is in
the spec?
That's part of the LSID resolution protocol. It's what the HTTP proxy
does unde
On Aug 25, 2007, at 12:44 PM, Eric Jain wrote:
Hilmar Lapp wrote:
This has nothing to do with the LSID spec, but with exposing
content in RDF. I'm not sure what you mean?
Sorry, I'm talking about the HTTP LSID proxying, this alternative
resolution mechanism would be very u
osing content
in RDF. I'm not sure what you mean?
-hilmar
--
===
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
s, are they?
-hilmar
--
===
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
P
transportation protocol.
This makes a lot of sense. I think it will need to be understood
though that any such mapping may be temporary (on the scale of
years), but that's probably not an issue at all.
-hilmar
--
=======
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
mpt this area) then there
ought to be clear recommendations and informatics infrastructure for
digital archives to serve their holdings on the semantic web, and
those semantic web documents should not be archived for a long time.
Does that make sense?
-hilmar
--
===
these here ...).
-hilmar
--
=======
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
s will all need to use opaque identifiers to track
relationships, provenance, versions, and other metadata.
-hilmar
--
===
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
e, or to a digital archive.
-hilmar
--
===
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
t to maintain any of those, or worse,
reassign them to something else.
What am I missing?
-hilmar
--
===
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===
On Aug 21, 2007, at 1:39 PM, Eric Jain wrote:
Hilmar Lapp wrote:
It seems to me that domain-specific resolution systems are rather
a fact and we deal with them all the time.
We try to deal with it, but it's a pain, even though the number of
different systems I need to deal wi
23 matches
Mail list logo
