<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:st = "" XMLNS:Z =
"urn:schemas-microsoft-com:" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
xmlns:pptsl = "http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/"
xmlns:ex12m = "http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:ex12t = "http://schemas.microsoft.com/exchange/services/2006/types"
xmlns:spwp = "http://microsoft.com/sharepoint/webpartpages" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:udcp2p =
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcs =
"http://schemas.microsoft.com/data/udc/soap" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:mt =
"http://schemas.microsoft.com/sharepoint/soap/meetings/" XMLNS:D = "DAV:"
xmlns:q = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:odc =
"urn:schemas-microsoft-com:office:odc" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:z = "#RowsetSchema" xmlns:rs
= "urn:schemas-microsoft-com:rowset" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:v =
"urn:schemas-microsoft-com:vml"><HEAD><!--[if !mso]>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<META content="MSHTML 6.00.2900.5726" name=GENERATOR></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=033264513-06042009><FONT face=Arial
color=#0000ff size=2>Well that's a revelation ...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=033264513-06042009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=033264513-06042009><FONT face=Arial
color=#0000ff size=2>At the ECAT SSC meeting during GB8 in Oaxaca in
2004 I recall saying that in the absence of a publishing tool to mobilize
checklist data we should use DwC and DIGIR and alias some of the fields if
required. I further recall the lack of enthusiasm by the 'IT' people present. It
looks like this has partly happened just 4.5 years later. But how do we keep all
this simply mobilized data sychronized unless this publishing tool (sorry, I've
not looked at it in detail ... yet) has some 'services' associated with it so
that a consumer can see what's been added and what's
changed?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=033264513-06042009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=033264513-06042009><FONT face=Arial
color=#0000ff size=2>Paul</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> tdwg-bounces@lists.tdwg.org
[mailto:tdwg-bounces@lists.tdwg.org] <B>On Behalf Of </B>Eamonn O Tuama
(GBIF)<BR><B>Sent:</B> 06 April 2009 14:18<BR><B>To:</B>
tdwg@lists.tdwg.org<BR><B>Subject:</B> Re: [tdwg] Consolidating TDWG
work<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>Dear Donald, TDWG Members and
Friends,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>GBIF supports your drive to use the GISIN community's
requirements as a test bed to demonstrate how the various TDWG standards can be
applied to solve their informatics issues. Last January, we convened a three day
workshop for the main Darwin Core (DwC) developers to enable them to make the
final push before submitting their work to the TDWG standards ratification
process. The proposed DwC standard, now submitted, provides a mechanism for
extending its base capabilities by adding new terms to the DwC vocabulary. The
basic technical solution for developing an extensible data encoding / transfer
schema is thus in place for invasive species data. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>In addition, GBIF has just released the first public
version of the Integrated Publishing Toolkit (IPT) v1.0
(http://www.gbif.org/News/NEWS1238568696) which was demonstrated to great
interest at the last TDWG Conference in Perth. The goal of the IPT is to remove
constraints to the publishing and flow across networks of biodiversity data. It
provides simple interfaces to transfer complete data stores efficiently in order
to simplify the publishing process and reduce the latency between data
publication and discoverability through the GBIF indexes. Accommodating three
main data types - taxon primary occurrence data, taxonomic checklists and
resource metadata - the IPT enables users to publish data residing in local
databases, upload existing files, and access central services to make use of
standardised controlled vocabularies. The IPT uses a "star schema", i.e., a
one-to-many schema in which a core record (expressed as DwC) can be linked to
many additional descriptors. The DwC record in IPT does not need to be an
occurrence. For checklist publishing we use the same DwC elements, but the
record in that case represents a species name, not an occurrence, and any star
schema extensions would be linking to species. For GISIN, those extensions can
cover relevant areas such as management, impact, descriptions, images, related
documents, distributions, dispersal, etc. The challenge for us is therefore to
help the GISIN community to define extensions to DwC and to develop customized
(thematic) portals that process and present the invasive species data according
to their particular requirements, e.g. tracking species movements.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>The IPT allows the sharing and use of specialist
extensions amongst the IPT-user community. It can also act as an outreach tool
for the GISIN community as it includes a web application that allows browsing
and searching of published data, along with basic mapping services including
Open Geospatial Consortium Web Map Service and Web Feature Service.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>We support the idea of a "cook book" that helps
communities use and, where required, extend standards to enable sharing of
biodiversity data. GBIF, through its Training portfolio will be able to
contribute documentation and training materials on many topics, e.g., the IPT,
metadata, web services.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>With regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>Éamonn <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>_______________________________________________<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>Éamonn Ó Tuama, M.Sc., Ph.D. (<A
href="mailto:eotuama@gbif.org"><SPAN
style="COLOR: blue">eotuama@gbif.org</SPAN></A>), <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>Senior Programme Officer, Inventory, Discovery, Access
(IDA), <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>Global Biodiversity Information</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: " Calibri?,?sans-serif?;color:#1F497D?>
</SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Calibri?,?sans-serif?;color:#1F497D?>Facility Secretariat,
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>Universitetsparken 15, DK-2100 Copenhagen Ø,
DENMARK</SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: "
Calibri?,?sans-serif?;color:#1F497D?> <BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>Phone: +45 3532 1494; Fax: +45 3532
1480</SPAN><SPAN lang=EN-IE style="FONT-SIZE: 11pt; FONT-FAMILY: "
color:#1F497D? Calibri?,?sans-serif?;><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Tahoma?,?sans-serif??>From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: " Tahoma?,?sans-serif??>
tdwg-bounces@lists.tdwg.org [mailto:tdwg-bounces@lists.tdwg.org] <B>On Behalf Of
</B>Donald.Hobern@csiro.au<BR><B>Sent:</B> 25 March 2009 00:43<BR><B>To:</B>
tdwg@lists.tdwg.org<BR><B>Subject:</B> [tdwg] Consolidating TDWG
work<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>Dear TDWG Members and Friends,</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>Those of you who attended the conference in Perth last year
will remember Annie Simpson's explanation of how hard it still is for a group
like the Global Invasive Species Information Network (GISIN) to take TDWG's work
and apply it directly to solve data integration issues in their
community.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>As I have previously suggested, I believe we should look
closely at GISIN's requirements and make sure that those in a similar situation
have all the tools and documentation required to start connecting data
easily in ways that are compatible with TDWG standards. We have most of
the pieces in place. We just need to organise and document them
better.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>Invasive species are of great significance to many
countries. This means that addressing GISIN's requirements is
directly relevant to a large number of TDWG participants. However
their scenario is also a template for data sharing in many other
biodiversity-related projects. They need to aggregate information from
many sources to populate several inter-related data models (BioStatus,
Occurrences, ProfileURLs, ImpactStatus, ManagementStatus and
DispersalStatus). Several of these are very close to existing data
models based on TDWG standards (for example, the Occurrence model can
be considered to be extended Darwin Core). Others are examples
of the kind of community-specific data which all biodiversity projects need to
share. </SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>TDWG's goal should be to ensure that GISIN and similar
groups can follow a simple set of instructions (a "cook book") and use standard
tools to build a network of this kind, and that they can do so in a way
which ensures that related communities can also benefit from the data they
share. For example, if GISIN members use the GISIN toolkit to share
data, we ought to make sure that no further steps are required for GBIF,
OBIS and others to integrate GISIN Occurrence data into their own
indexes of species occurrences, or for EOL, ALA and others to integrate GISIN
ImpactStatus, ManagementStatus and DispersalStatus data into their species
profiles.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>I am therefore writing this email as an appeal for TDWG
members to step forward and help to complete the work we have started. I
am setting a challenge for us to do whatever still needs to be done to our
standards, tools and data sharing recommendations so that we can produce such a
cook book by the end of 2009. I don't believe this is an unrealistic
goal. We can start work now on identifying and resolving issues. We
can plan activities at the 2009 TDWG conference in November to resolve any
issues still outstanding at that point and to hold hackathon activities to fill
any gaps in our tool set. This work also aligns well with the e-Biosphere
conference's plan to develop a roadmap for biodiversity informatics for the next
10 years.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>We have added a page to the TDWG Invasive Species wiki to
seed discussion of what we need to do - <A
href="http://wiki.tdwg.org/twiki/bin/view/InvasiveSpecies/GisinRequirements">http://wiki.tdwg.org/twiki/bin/view/InvasiveSpecies/GisinRequirements</A>.
Please take the time to look at this page (and at the information on GISIN's
requirements at <A
href="http://wiki.tdwg.org/twiki/bin/view/InvasiveSpecies/WebHome">http://wiki.tdwg.org/twiki/bin/view/InvasiveSpecies/WebHome</A>
and <A
href="http://www.niiss.org/cwis438/websites/GISINDirectory/Tech/ProtocolSpecification.php">http://www.niiss.org/cwis438/websites/GISINDirectory/Tech/ProtocolSpecification.php</A>).
Append comments and suggestions on what else we may need to do to the wiki, or
simply reply to this message. In particular, if you are interested in
being involved with the relevant TDWG Interest Groups in addressing some of the
listed requirements, please contact me or the relevant Interest Group
leaders.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>I believe this is the most significant thing that TDWG can
do right now to support the work of biodiversity informatics worldwide.
Please consider making your own contribution to make it
happen.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>Best wishes,</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif??>Donald</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: " color:navy?
Arial?,?sans-serif?;><o:p> </o:p></SPAN></P>
<TABLE class=MsoNormalTable
style="MARGIN-LEFT: 0.45pt; MARGIN-RIGHT: 0.45pt; BORDER-COLLAPSE: collapse"
cellSpacing=0 cellPadding=0 align=left border=0>
<TBODY>
<TR>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; WIDTH: 1.5in; PADDING-TOP: 0in"
vAlign=top width=180>
<P class=MsoNormal
style="mso-element: frame; mso-element-frame-hspace: 2.25pt; mso-element-wrap: around; mso-element-anchor-vertical: paragraph; mso-element-anchor-horizontal: column; mso-height-rule: exactly"><SPAN
style="COLOR: blue"><IMG id=_x0000_i1025 height=104
src="cid:033264513@06042009-1B1C" width=129
border=0><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif?; color:blue?><o:p> </o:p></SPAN></P></TD>
<TD
style="PADDING-RIGHT: 5.4pt; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; WIDTH: 314.5pt; PADDING-TOP: 0in"
width=524>
<P class=MsoNormal
style="mso-element: frame; mso-element-frame-hspace: 2.25pt; mso-element-wrap: around; mso-element-anchor-vertical: paragraph; mso-element-anchor-horizontal: column; mso-height-rule: exactly"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif?;color:blue?>Donald Hobern, Director, Atlas of Living
Australia</SPAN><SPAN style="COLOR: navy"><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="mso-element: frame; mso-element-frame-hspace: 2.25pt; mso-element-wrap: around; mso-element-anchor-vertical: paragraph; mso-element-anchor-horizontal: column; mso-height-rule: exactly"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif?;color:blue?>CSIRO Entomology, GPO Box 1700, Canberra,
ACT 2601</SPAN><SPAN style="COLOR: navy"><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="mso-element: frame; mso-element-frame-hspace: 2.25pt; mso-element-wrap: around; mso-element-anchor-vertical: paragraph; mso-element-anchor-horizontal: column; mso-height-rule: exactly"><SPAN
lang=FR style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif?;color:blue?>Phone: (02) 62464352 Mobile: 0437990208
</SPAN><SPAN lang=FR style="COLOR: navy"><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="mso-element: frame; mso-element-frame-hspace: 2.25pt; mso-element-wrap: around; mso-element-anchor-vertical: paragraph; mso-element-anchor-horizontal: column; mso-height-rule: exactly"><SPAN
lang=FR style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif?;color:blue?>Email: </SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: " Arial?,?sans-serif?;color:blue?><A
title=mailto:Donald.Hobern@csiro.au
href="mailto:Donald.Hobern@csiro.au"><SPAN
lang=FR>Donald.Hobern@csiro.au</SPAN></A></SPAN><SPAN lang=FR
style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif?;color:blue?><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="mso-element: frame; mso-element-frame-hspace: 2.25pt; mso-element-wrap: around; mso-element-anchor-vertical: paragraph; mso-element-anchor-horizontal: column; mso-height-rule: exactly"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: "
Arial?,?sans-serif?;color:blue?>Web: <A title=http://www.ala.org.au/
href="http://www.ala.org.au/">http://www.ala.org.au/</A> </SPAN><SPAN
style="COLOR: navy"><o:p></o:p></SPAN></P></TD></TR></TBODY></TABLE>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV></DIV></p>
<a href="http://www.cabiglobalsummit.com">
<IMG SRC="cid:1114-90a240c2@59de6d58.01c9b6bf"></a>
<p> </p>
<p><span style="font-size:18.0pt;font-family:Webdings;
color:green">P</span><span style="mso-bidi-font-size:10.0pt;font-family:"Courier New";
color:#339966"> </span><font face="Arial">
<span style="font-size:8.0pt;mso-bidi-font-family:Arial;color:green;mso-bidi-font-weight:bold">Think Green -
don't print this email unless you really need to</span></font><span style="font-size:8.0pt;font-family:"Comic Sans MS";
mso-bidi-font-family:Arial;color:green;mso-bidi-font-weight:bold"><o:p>
</span>
<span style="font-size:8.0pt;font-family:"Comic Sans MS";
mso-bidi-font-family:Arial;mso-bidi-font-weight:bold">
<p><font face="Arial" size="1">
************************************************************************<br>
The information contained in this e-mail and any files transmitted with it is confidential and is for the exclusive use of the intended recipient. If you are not the intended recipient please note that any distribution, copying or use of this communication or the information in it is prohibited. <br>
<br>
Whilst CAB International trading as CABI takes steps to prevent the transmission of viruses via e-mail, we cannot guarantee that any e-mail or attachment is free from computer viruses and you are strongly advised to undertake your own anti-virus precautions.<br>
<br>
If you have received this communication in error, please notify us by e-mail at cabi@cabi.org or by telephone on +44 (0)1491 829199 and then delete the e-mail and any copies of it.<br>
<br>
CABI is an International Organization recognised by the UK Government under Statutory Instrument 1982 No. 1071.<br>
<br>
**************************************************************************</font>
</BODY></HTML>