SDD Part 0: Introduction and Primer to the SDD Standard

3.2 Technical metadata

Each SDD instance document must include some metadata about the document. The <TechnicalMetadata> element provides information about the processor that created the SDD document.

technicalmetadata.jpg

Example 3.2.1 - Technical Metadata for an SDD document

<?xml version="1.0" encoding="UTF-8"?>
<Datasets xmlns="http://ns.tdwg.org/UBIF/2006" 
    xmlns:sea="http://www.bgbm.org/biodivinf/Schema/sea" 
   xmlns:html="http://www.w3.org/1999/xhtml" 
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
   xsi:schemaLocation="http://ns.tdwg.org/UBIF/2006">
  <TechnicalMetadata created="2003-07-18T22:16:38">
    <Generator name="Lucid3 Builder" version="3.2.0"/>
    <TechnicalContact label="tech1" name="Principal Lucid Programmer" 
   email="support@lucid.org" phone="+62 7 66553333" 
   address="5164 Silicon Boulevard, Sunset Hills, Mytopia 30665"/>
    <AdministrativeContact label="admin1" 
   name="The Manager, IT Services" 
   email="support@lucid.org" phone="+62 7 66553333" 
   address="5164 Silicon Boulevard, Sunset Hills, Mytopia 30665"/>
  </TechnicalMetadata>
    <Dataset xml:lang="en">
      <Representation>
        <Label>Technical metadata example</Label>
      </Representation>
    </Dataset>
</Datasets>

<TechnicalMetadata> includes a date and time stamp for the creation of the document.

The <Generator> element provides a name, version number and routine for the program that generated the SDD document. In the rare instance that a document is authored by hand, the name of the generator should read 'By Hand'.

<TechnicalContact> and <AdministrativeContact> are used to provide names and contact details for people responsible for the generating application. Note that SDD documents are long-lived, so transient staff should not be named here. The purpose of these is to allow a recipient of the document to contact support staff for the generating application with technical or administrative queries. Note that these contacts are responsible for the generating application, not necessarily for the data generated by the application.

-- DonovanSharp - 01 Jun 2006