TriDaS specified controlled vocabulary for the type of dating. When type is specified
as 'relative', all dating suffixes should also be set to 'relative'. Otherwise,
dating suffixes should be set to the appropriate calendar scheme
TriDaS specified controlled vocabulary for the method of measurement
TriDaS specified controlled vocabulary element shape adapted from dictionary created by BIAX Consult, Zaandam (NL).
TriDaS specified controlled vocabulary for the type of location
TRiDaS specified controlled vocabulary for the measurementSeries variable
TRiDaS specified controlled vocabulary for the units in which data are stored
TRiDaS specified controlled vocabulary for remarks attached to rings
A controlled vocabulary is used to limit users to a pick list of values.
Programmers note that if using controlled vocabularies, then normal, normalId and normalStd should all be
present. There is no way to describe optionality of attribute groups in xsd schemas so this must be done by you!
The name of the standard used to control this vocabulary
The ID value in the standard dictionary corresponding to this entry
The normalised name for this entry
The language this term is in. Default is EN if not specified.
Suffix to add to a year number. The suffix 'relative' should
be used when the dating type is set to 'relative'
Simple presence/absence data type
Complex presence/absence data type with additional possibilities
Simple certainty data type
An extension to the basic dateTime type which includes an optional 'certainty' attribute.
Field containing date and time when this record was created.
Field containing date and time when this records was last updated.
An extension to the basic date type which includes an optional 'certainty' attribute.
Data type for storing year. Includes a separate suffix attribute and optional certainty value.
The actual data value should be a positive integer if suffix BC, AD or BP is used
Base data type inherited by all TRiDaS entities. Contains the fields common to all TRiDaS data entities.
The type of entity this is. Preferrably derived from a controlled vocabulary.
General description of this entity.
Title or name of this entity. This should be a 'human readable' name by which the entity is referred.
Identifier for this entity which in combination with the domain should be unique. This is typically a computer generated code such as a database primary key.
The domain which this identifier is applicable to. Could be the URL of the organisation's server or the
name of the organisation as long as it is not ambiguous.
Details about the geographical location of this entity.
GML representation of a location. Can be either a point to
represent a particular location or a polygon to represent
an area or a geographical extent / bounding box.
The type of location that the geometry field represents taken from the TRiDaS controlled vocabulary.
Stores potential difference; number of meters difference, so 0 is exact.
Additional information about the location, for example, point taken from center or corner of area, which corner
Address information about this location
Filename of a file associated with this entity.
Generic field for storing key/value pairs for data not currently supported in the TRiDaS standard
Name of the field.
The data type that this field contains.
A project is defined by a laboratory and encompasses dendrochronological
research of a particular object or group of objects. Examples include: the dating of
a building; the research of forest dynamics in a stand of living trees; the dating of
all Rembrandt paintings in a museum. What is considered a 'project' is up to the
laboratory performing the research. It could be the dating of a group of objects,
but the laboratory can also decide to define a separate project for each object.
Therefore, a project can have one or more objects associated with it.
The dendrochronological research laboratory where this work was done.
Identifier for the laboratory.
Name of the laboratory.
Acronym of the laboratory.
Category of research this project falls into. Preferably from a controlled vocabulary.
Principal investigator of this project.
When the dendrochronological project took place. Could consist of a start- and end-date. If unknown it should be estimated.
Date of the request for dendrochronology. If unknown it should be estimated.
The person/organisation who commissioned the project.
Citations of publications relating to this project.
National/International system in which the research project is registered.
An object is the item to be investigated. Examples include: violin; excavation site;
painting on a wooden panel; water well; church; carving; ship; forest. An object could
also be more specific, for example: mast of a ship; roof of a church. Depending on the
object type various descriptions are made possible. An object can have one or more
elements and can also refer to another (sub) object. For instance a single file
may contain three objects: an archaeological site object, within which there is a
building object, within which there is a beam object. The list of possible object
types is extensible and is thus flexible enough to incorporate the diversity of data
required by the dendro community. Only information that is essential for
dendrochronological research is recorded here. Other related data may be provided in the
form of a link to an external database such as a museum catalogue.
Name of creator, place of the workshop/wharf etc.
Name of the owner of the physical object.
Details on the time period this object covers.
If the date is already known in more or less detail: historical period (broad). Equivalent to Dublin Core term 'temporal'.
Method of dating support (e.g. archive sources, inscriptions,
stratigraphic context, associated finds, typology, stylistic aspects,
carpenter marks, radiocarbon, OSL, other methods).
An element is a piece of wood originating from a single tree. Examples include:
one plank of a water well; a single wooden panel in a painting; the left-hand back
plate of a violin; one beam in a roof; a tree trunk preserved in the soil; a
living tree. The element is a specific part of exactly one object or sub object.
An object will often consist of more than one element, e.g., when dealing with the
staves (elements) of a barrel (object). One or more samples can be taken from an
element and an element may be dated using one or more derivedSeries.
The most detailed taxonomic name known for this element (species, genus, family etc).
Preferably from the Catalogue of Life (www.catalogueoflife.org) controlled vocabulary.
The shape of this element, as a free text description, an entry from a specificed
controlled vocabulary, or perferably from the TRiDaS controlled vocabulary.
Physical dimensions of this element, either height and diameter, or height, width and depth. The units of these measurements must also be specified.
Height of this element. Should be used in combination with either diameter, or width and depth.
Diameter of this element. Used in combination with height when the element is a tree.
Width of the element.
Depth of the element.
Whether this element is original, a repair or later addition etc.
Processing (carved, sawn etc.) rafting marks etc.
Carpenter marks, inscriptions etc
Altitude in metres if this element is a standing tree in situ.
Only relevant if this element is a standing tree. Contains details about the slope this tree was growing on.
Angle of slope from horizontal in degrees
Angle in degrees from north along which the slope lies
Only relevant if this element is a standing tree. Contains details of the soil the tree was growing in.
General description of the soil type
Depth of soil in centimetres
Only relevant if this element is a standing tree. Contains details of the bedrock below where the tree was growing.
General description of the underlying bedrock
A sample is a physical specimen or non-physical representation of an element.
Examples include: core from a living tree; core from a rafter in a church roof;
piece of charcoal from an archaeological trench; slice from a pile used in a
pile foundation; wax imprint of the outer end of a plank; photo of a back plate
of a string instrument. Note that a sample always exists and that it can either
be physical (e.g. a core) or representative (e.g. a picture). A sample is taken
from exactly one element and can be represented by one or more radii.
Date the sample was taken
Description of the position in the element where this sample was taken from
State of the material (dry/wet/conserved/burned, woodworm, rot, cracks) things that indicate the quality of the measurements.
Are knots present in the sample?
Details of the pith, heartwood, sapwood and last ring under the bark. This is included under the radius or
measurementSeries entities. If present in both, the measurementSeries details
supercede those of the radius.
Convenience field for recording the total number of rings measured. If there is a disparity between this field and the actual number of 'values' tags, then the number of 'values' tags should be taken as definitive.
Convenience field for recording the average ring width of rings measured. If there is a disparity between this field and the actual 'values' tags, then the average of the 'values' tags should be taken as definitive.
Field for recording whether there are any rings at the inner (i.e. towards pith) edge of the sample that have not been measured. Typically used to note when rings are too damaged to measure.
Field for recording whether there are any rings at the outer (i.e. towards bark) edge of the sample that have not been measured. Typically used to note when rings are too damaged to measure.
Whether the pith is present or absent
This field records whether the outer (youngest) heartwood is present and if so whether it is complete. If the sample includes the last heartwood ring before the sapwood then it is 'complete' otherwise it is 'incomplete' or 'absent'.
Estimated number of missing heartwood rings to the pith
Description of the way the estimation of how many heartwood rings are missing was made and what the certainty is.
Details about the sapwood
Whether the sapwood is present or not
Number of sapwood rings measured
Information about the last rings under the bark. If the last ring is under
the bark is present, include information about the completeness of this ring
and/or season of felling.
Estimated number of missing sapwood rings to the bark
Description of the way the estimation of how many sapwood rings are missing was made and what the certainty is.
Bark is present or absent
A radius is a line from pith to bark along which the measurements are taken.
A radius is derived from exactly one sample. It can be measured more than once
resulting in multiple measurementSeries.
Angle in degrees from north along which this radius lies.
A base type inherited by measurementSeries and derivedSeries.
A measurementSeries is a series of direct, raw measurements along a radius. A
single measurementSeries can be standardised or a collection of
measurementSeries can be combined into a derivedSeries. The measurements
themselves are stored separately as values.
Date that the measurements where made.
Name of the analyst that made the series
Name of the dendrochronologist that oversaw the analyst
Method that was used to measure this measurementSeries, preferably from the TRiDaS controlled vocabulary.
TRiDaS controlled vocabulary for the method of measuring.
More information about this entity.
Contains either the 'interpretation' of the series or an 'interpretationUnsolved' placeholder
Information interpreted from the series
Information about dating
Field to denote dating type
Chronology used to interpret the series
Year of the first measured ring. This is derived from the chronology that
was used to date this series. It is not to be confused with sproutYear.
Year of the last measured ring. It is not to be confused with deathYear which might also include unmeasured or hypothetical rings
Container for fields that describe the statistical method used for crossdating
Statistical value used to support match with chronology
Significance of the statistical match with the chronology
Software used to perform the statistical match with the chronology
Estimated year that the tree sprouted
Estimated year of death of the tree
Estimated provenance derived from the matching chronology
A derivedSeries is a calculated series of values and is a minor modification of the
'v-series' concept proposed by Brewer et al (2009). Examples include: index; average
of a collection of measurementSeries such as a chronology. A derivedSeries is derived
from one or more measurementSeries and has multiple values associated with it.
The date that this derivedSeries was created.
The reason/rationale why this series was made
Numerical method used to standardise the series
Name of the person that created this derivedSeries
Version number of this derivedSeries
This is a container for a group of actual measurement values. When appropriate this container
includes details on the variable being represented as well as the units used. If the values
are unitless, then the special <unitless> field is used.
Measured variable (ring width, earlywood, latewood etc) preferrably
taken from the TRiDaS controlled vocabulary
Measurement units used for these value, preferrably taken from the
TRiDaS controlled vocabulary
Presence of this field denotes that hte associated values have no
units. Not to be used to denote *unknown* units.
A value is the result of a single ring measurement. The type of measurement this is along with
the units used are recorded in the 'values' container in the associated measurement- or derviedSeries.
Optional field to denote how many underlying values went to create this value in a derivedSeries
Remark about this value. Remarks can be standardised to consistantly
record important features like 'frost damage' - preferrably using the
TRiDaS controlled vocabulary.
TRiDaS controlled vocabulary for specific remarks.
In derivedSeries this shows the number of constituent measurementSeries that this remark is found in.
Collection of one or more vocabulary dictionaries