<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Dear Fellow TAG Member,</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The TAG mailing list has been quiet recently which may give the impression that there has been little action in terms of the new standards architecture. This is far from the truth. By its nature the TAG runs across almost all of the activities in TDWG and progress has been made in many separate areas that is contributing to the implementation of the overall vision as outlined in last years roadmap document:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><A href="http://www.tdwg.org/uploads/media/TAG_Roadmap_01.doc">http://www.tdwg.org/uploads/media/TAG_Roadmap_01.doc</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>This is a (possibly one off) news letter that summarizes some of the activities. Please shout out if I have missed anything or misrepresented anything.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-style-span"><B>Ontology and LSID Vocabularies</B>.</SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>An initial high level ontology for TDWG was presented at St Louis meeting. This is a useful overview of the TDWG domain across the existing schemas and standards.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><A href="http://wiki.tdwg.org/twiki/bin/view/TAG/TDWGOntology">http://wiki.tdwg.org/twiki/bin/view/TAG/TDWGOntology</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Since that meeting the focus has been on developing application level classes within the ontology that can be used to define the metadata returned by LSID providers that are coming on line this year. These classes have been termed the LSID Vocabularies:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><A href="http://wiki.tdwg.org/twiki/bin/view/TAG/LsidVocs">http://wiki.tdwg.org/twiki/bin/view/TAG/LsidVocs</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The relationship between these 10 or so application level classes and the higher level ontology is being left somewhat vague at this point to allow the development of deployable systems now. Future changes in the ontology to more tightly integrate the LSID Vocabularies will be required to allow for inference across the data in the future but should not require significant changes of instance data (the deployed base) as the classes are insulated in their own namespaces.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The tool presented in St Louis to allow collaborative editing of the ontology has been abandoned in favor of the use of regular IDEs to produce RDF/OWL documents a Subversion repository. The need to port the ontology into many different technologies was not supported by further investigation but LSID Vocabularies will be presented in XML Schema so that they can be integrated with the TAPIR data providers - see below.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><B>LSID Adoption</B></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>By the end of the year it is planned that LSID providers will include IPNI, Index Fungorum and ZooBank for TaxonName objects. Species2000/Catalogue of Life annual checklist for TaxonConcepts, Herb IMI for Specimens. There will be a toolkit available for publishing Collections data in LSID Vocabulary format and issuing LSIDs for them. Many data sources will either be LSID enabled or in a position to deliver data as RDF based on the TDWG ontology - thanks to a combination of the TAPIR protocol/provider software and the LSID Vocabularies.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><B>Progress with TAPIR protocol and providers.</B></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The TAPIR protocol is now ready to enter the new TDWG standards track as Version 1 and two wrapper implementations are available -PyWrapper and TAPIRLink. It has been established (at a very successful TAPIR developers meeting in Copenhagen) that TAPIR will support delivery of RDF data based on the ontology. This mechanism is currently being refined through the use of avowed XML Schemas.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>TAPIR providers are being rolled out in the USA and Europe this year and with them will go the ability to map to the ontology and exchange data in RDF.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>A diagram summarizing the standards architecture is on the home page of the TAG Wiki</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><A href="http://wiki.tdwg.org/twiki/bin/view/TAG/WebHome">http://wiki.tdwg.org/twiki/bin/view/TAG/WebHome</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><B>New charter for the new organisation structure.</B></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>TDWG was re-organized at the St Louis meeting. There is now a hierarchy of subgroups consisting of Interest Groups that contain Task Groups. All subgroups were asked to re-submit their charters and this has now been done for the TAG. The new charter is on the TAG Wiki home page. There are few changes from the previous charter.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>There seems to be general agreement that the TAPIR subgroup and the GUID subgroup will become Task Groups within the TAG Interest Group but this can't happen until the executive have reviewed and accepted the TAG charter.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><B>How about a meeting?</B></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The dates have now been set for the TDWG 2007 meeting (16-23 September 2007 - Bratislava, Slovakia). By that date the TAG needs to put together a new Roadmap document describing the outlook for 2007/8. Funding may be available (from the TDWG Infrastructure Project) to hold a meeting of key individuals within the TAG at some point over the northern summer to help put that documents together. We would need to put a good case together to get it funded as we would be in competition with other groups. Whether or not we have a meeting I would like to hear opinions on how the TAG should be represented at the Bratislava meeting. Should we have a session within the main meeting? Should we have a pre-meeting?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><B>Your input required</B></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The TAG seems to be operating as a network of individuals rather than a single conversation. This is a good thing in that people don't have to spend a lot of time sifting through stuff that doesn't effect them. It is a bad thing in that it is easy for people to feel left out of the process. </DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>If you would like to be more involved or think we should be looking at something we are not please let me know, bring it up on the mailing list or start a page on the wiki.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>All the best for Easter and the coming Spring/Autumn depending on you hemisphere.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Roger</DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV> </DIV><DIV>____________________________________________________________</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV> Roger Hyam <<A href="mailto:roger@tdwg.org">roger@tdwg.org</A>></DIV><DIV> Biodiversity Information Standards: <A href="http://www.tdwg.org">http://www.tdwg.org</A>/</DIV><DIV>____________________________________________________________</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV> TDWG Standards Architecture: <A href="http://wiki.tdwg.org/twiki/bin/view/TAG">http://wiki.tdwg.org/twiki/bin/view/TAG</A></DIV><DIV> LSID RDF Vocabularies: <A href="http://wiki.tdwg.org/twiki/bin/view/TAG/LsidVocs">http://wiki.tdwg.org/twiki/bin/view/TAG/LsidVocs</A></DIV><DIV>____________________________________________________________</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR class="Apple-interchange-newline"></SPAN></SPAN> </DIV><BR></BODY></HTML>