Graphical design component

r7 - 03 Nov 2008 - 15:11:33 - RogerHyamYou are here: TWiki >  TAG Web > SpeciesPages > SpeciesPagesMetaTags
These ideas are still under discussion.

SpeciesPagesMetaTags

This page describes how you can improve the metatags in a species page so that it works well with species page indexers (see SpeciesPages). It will probably improve performance of any indexer.

Introduction

HTML pages have a <head> section that contains information about the page that isn't normally displayed. Two of the elements that can occur in the head section are the <meta> element and the <link> element.

Dublin Core (DC) is the most common metadata vocabulary for describing all sorts of objects. The Dublin Core Metadata Initiative describes how to express DC in HTML using these two elements. Using DC and one metadata term from the TDWG ontology it is possible to provide rich information in the page header that enable indexers to bind species pages to nomenclatural and other kinds of data thus making your species page part of a global system.

This page provides simple information on what to include in the <head> section of your species pages. You should not need to read other documents to get your pages marked up correctly but you can if you want to of course.

Complete Example

The content to include is simple so it is best to start with a complete example and then explain the different parts.

<head>
   ...
   <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
   <meta name="DCTERMS.title" content="Lythrum salicaria L." >
   <meta name="DCTERMS.subject" content="SpeciesPage Plantae Lythrum salicaria Purple-loosestrife" >
   <meta name="DCTERMS.coverage" content="GB IE 155 British Isles and Western Europe" >
   <link rel="schema.TDWG" href="http://rs.tdwg.org/ontology/voc/TaxonConcept#" >
   <link rel="TDWG.hasName" href="urn:lsid:ipni.org:names:103757-3:1.1" >
   ...
</head>

schema.DCTERMS

The first line is not specific to SpeciesPages. It just defines the namespace for the Dublin Core metadata vocabulary that is used in the next three lines. Further explanation is given here.

DCTERMS.title

The second line gives the 'title' of the resource. The content attribute of this line should contain the full name of the species including any authorship string and dates. Here it is used in an equivalent sense to the Darwin Core ScientificName field.

DCTERMS.subject

The third line gives the 'subject' of the resource. The Dublin Core Metadata Initiative makes the following comment "Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary."

The content attribute of this line should start with the key word 'SpeciesPage' followed by the Kingdom of the species, followed by the genus of the species followed by the specific epithet of the species with a space between each word. Further key words can be added after the specific epithet.

The Kingdom should be one of: Eukaryota, Animalia, Plantae, Fungi, Chromista or Protozoa.

DCTERMS.coverage

The fourth line gives the 'coverage' of the resource. The Dublin Core Metadata Initiative suggests the use of a controlled vocabulary for this field. Because species accounts are typically applicable at quite a high geographic level two controlled vocabularies are suggested.

The content attribute of this element should contain a combination of two letter alphabetic codes for countries from the ISO-3166-1 standard and/or three digit numeric United Nations geographical region codes.

A SpeciesPage? indexer can digest the contents of this attribute and interpret two letter and three digit codes appropriately but ignore any other words that may be useful for other indexers.

schema.TDWG

The fifth line is like the first line in that it defines a namespace. The namespace defined is for the TDWG TaxonConcept? vocabulary that is used in the next line. Both this and the next line give a degree of precision that is desirable but optional.

TDWG.hasName

The sixth and final line enables indexers to unambiguously link the species page with a name as defined by one of the major nomenclators; IPNI, IndexFungorum? or ZooBank?.

The href attribute of this line should contain the LSID of a name from one of these recognized nomenclators.

Expressing Taxonomic Relationships

You can express valuable taxonomic relationships by adding other lines. If the page represents a taxon that you do not think should be used (e.g. you consider it a synonymous taxon) then you should state specifically in the text of the page that another taxon should be used and you should add this line in the header (below the schema.DCTERMS line).

   <link rel="DCTERMS.isReplacedBy" href="http://link_to_other_species_page" >
In the accepted taxon page you could include this line in the header
   <link rel="DCTERMS.replaces" href="http://link_to_other_species_page" >
You can indicate that this page represents a taxon that is a child of another taxon (e.g. a species of a genus) by including a line like this:
   <link rel="DCTERMS.isPartOf" href="http://link_to_other_species_page" >
In the enclosing taxon page (e.g. the genus of a species) you can include a link like this:
   <link rel="DCTERMS.hasPart" href="http://link_to_other_species_page" >

Other Dublin Core Terms

The above recommendation is only concerned with the Dublin Core metadata terms to include for the specific benefit of Species Page indexes. You are encourage to follow best practice in including as many other Dublin Core terms as are relevant to your situation. Terms of particular importance are: created, modified, publisher, creator and license. The terms are documented here and examples of expressing them are documented here.

HTML or XHTML?

There are broadly two types of HTML used today (though several subtypes). If HTML documents are valid XML documents they are referred to as XHTML and begin with an declaration that looks like this:

<?xml version="1.0" encoding="utf-8" ?>

they also have XHTML mentioned in their DOCTYPE declaration. Regular HTML documents are not valid XML they don't start with a XML declaration or mention XHTML in their DOCTYPE declaration. Regular HTML pages are far more common that XHTML pages.

The examples given above are for regular HTML pages. They can be adapted for XHTML pages simply by adding a / (forward slash) before the closing > of the link or meta elements for example this:

<link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >

would become this:

<link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />


Linking Topics
Edit | Attach | Printable | Backlinks: Web, All Webs | History: r7 < r6 < r5 < r4 < r3 | More topic actions
 
Back to TDWG Homepage TDWG Wiki > TAG
This site is powered by the TWiki collaboration platform

Valid XHTML 1.0 Transitional
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
http://wiki.tdwg.org/twiki/bin/view/TAG/SpeciesPagesMetaTags
wiki.tdwg.org
crawl=CC-MAIN-2014-23
27090
application/http; msgtype=response
sha1:Q72JDVN7NDQBRDUTOZB6UUUJ52GQT5QZ
<urn:uuid:4cc4caa5-df7c-403b-941b-a7fa349d2afa>
2014-07-24T19:24:32Z
192.38.28.106
sha1:YJ5TPCFZ6PZZ3ZWVGZZUWXRW2CFWO6XK
<urn:uuid:5783d12f-756d-41b9-b7f1-ac443f6696cb>
http://wiki.tdwg.org/twiki/bin/view/TAG/SpeciesPagesMetaTags
response
<urn:uuid:3fb2f891-c64a-4da5-8cc5-5f50414b7569>
robots: classic
hostname: ip-10-33-131-23.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2014-23
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for July 2014
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf