[This local archive copy mirrored from the canonical site: http://www.erin.gov.au/database/metadata/anzmeta/anzmeta-1.1.html; links may not have complete integrity, so use the canonical document at this URL if possible.]

ANZMETA DTD Version 1.1

The Australia New Zealand Land Information Council - ANZLIC Working Group on Metadata
19th January 1998

Contents

1 A Guide to Elements in the DTD
  1.1 Overall Structure
  1.2 Text Elements
  1.3 New Leaf Elements
2 XML Conformance
3 General Considerations in Writing Data Records
4 Changes from V1.0
5 Detailed Element Descriptions


1 A Guide to Elements in the DTD

1.1 Overall Structure

The DTD structures the elements of the ANZLIC Metadata Guidelines beyond what is given in the Guidelines. This is necessary to provide a framework in which additional thematic or agency-specific elements can later be added, according to ANZLIC "higher pages" concept.

Table 1 shows the hierachial structure of the DTD, and indicates where the information for each of the named metadata elements is stored. The short names used in the DTD correspond to equivalent element names in the FGDC Metadata Content Standards. Clicking on an element name in Table 1 will display detailed information about that element (links to the Metadata Guidelines are under construction).

Table 1: Structure of the ANZLIC DTD v1.1, showing mappings from the ANZLIC Metadata Guideline Elements.
ANZLIC ElementDTD Element
anzmeta
Datasetciteinfo
ANZLIC Unique IDuniqueid
Titletitle
origin
Custodiancustodian
Jurisdictionjurisdic
keyword
Descriptiondescript
Abstractabstract
Search Word(s)theme
keyword
spdom
place
Geographic Extent Namekeyword
Geographic Extent Polygondsgpolyo
long
lat
bounding
North Bounding Coordinatenorthbc
South Bounding Coordinatesouthbc
East Bounding Coordinateeastbc
West Bounding Coordinatewestbc
Data Currencytimeperd
Beginning Datebegdate
date
keyword
Ending Dateenddate
date
keyword
Dataset Statusstatus
Progressprogress
keyword
Maintenance & Update Frequencyupdate
keyword
Accessdistinfo
Stored Data Formatnative
nondig
formname
digform
formname
Available Format Typeavlform
nondig
formname
digform
formname
Access Constraintsaccconst
Data Qualitydataqual
Lineagelineage
Positional Accuracyposacc
Attribute Accuracyattracc
Logical Consistencylogic
Completenesscomplete
Contact Informationcntinfo
Contact Organisationcntorg
Contact Positioncntpos
Mail Address 1
Mail Address 2
address
Suburb or Citycity
Statestate
Countrycountry
Postcodepostal
Telephonecntvoice
Facsimilecntfax
Electronic Mail Addresscntemail
metainfo
Metadata Datemetd
date
Additional Metadatasupplinf

1.2 Text Elements

The DTD contains definitions for a number of text-markup elements borrowed from the HTML standard. There are two types of elements - Inline and Block, and are described in Table 2 and Table 3. Although the DTD does not treat these elements differently from metadata elements, they were omitted from Table 1 for simplicity.

While the defined text elements appear the same as HTML, there are a number of restrictions on their use in data records:

Table 2: Inline Text Elements. These elements can be used in all metadata elements except those with a specific format (eg. date).
Inline Text ElementDescription
ttmonospaced type
iitalic type
bbold type
bigbigger type
smallsmaller type
ememphasised type (normally italic)
alink to Internet resource
brforced line break
subsubscript
supsuperscript

Inline Text Elements can be used within the text of any metadata element, except:

		uniqueid (ANZLIC unique ID)
		long (used in Geographic Extent Polygon)
		lat (used in Geographic Extent Polygon)
		northbc (North Bounding Coordinate)
		southbc (South Bounding Coordinate)
		eastbc (East Bounding Coordinate)
		westbc (West Bounding Coordinate)
		date (used in Beginning Date, Ending Date, Metadata Date)
Table 3: Block Text Elements. These elements can be used withing abstract, accconst, supplinf and any of the dataqual subelements.
Block Text ElementsDescription
pparagraph start
prepreformatted text (monospaced)
ulunordered list
olordered list
lilist item
dldescriptive list
dtdescriptive list term
dddescriptive list definition

Block elements can only be used in the following SGML elements:

		abstract (Abstract)
		accconst (Access Constraints)
		lineage (Lineage)
		posacc (Positional Accuracy)
		attracc (Attribute Accuracy)
		logic (Logical Consistency)
		complete (Completeness)
		supplinf (Additional Metadata)

1.3 New Leaf Elements

The DTD makes use of leaf elements that describe a type of content:

Use of these leaf elements allows an application to treat each occurrence of these leaf elements in the same way. For example, although the date element appears in three different contexts,

		timeperd - begdate - date,
		timeperd - enddate - date and
		metainfo - metd - date,
in each case, the content of the date field is in the same format, ISO8601 (see notes on the date element), and can be presented by an application in the same way (eg. "01 January 1970").

The keyword leaf element strengthens the notion that the text content is one of a finite list of allowable values.

2 XML Conformance

This DTD has been written to conform to the requirements of XML 1.0. To ensure that Metadata documents conform, pay attention to the following points:

3 General Considerations in Writing Data Records

4 Changes from V1.0

The major changes from V1.0 to V1.1 have been to make the DTD compatible with recent developments such as XML, to allow higher page elements (thematic or agency specific) to be incorporated simply, and to clarify the document structure thus reducing interpretation problems.

Changes from Version 1.0 to Version 1.1 by:

Benjamin Hatton
Live Content Engineering & Design
http://www.livecontent.com.au/
under contract to Environmental Resources Information Network (ERIN)

5 Detailed Element Descriptions

citeinfo

Example:

<citeinfo>
	<uniqueid>
		ANZCW00000000
	</uniqueid>
	<title>
		Possible Scenarios for the Spread of Rabbit
		Calicivirus Disease (RCD) to December 1995
	</title>
	<origin>
		<custod>
			Bureau of Resource Sciences (BRS)
		</custod>
		<jurisdic>
			Australia
		</jurisdic>
	</origin>
</citeinfo>

jurisdic

Allowable Jurisdiction keywords under the default thesaurus are (as defined in the ANZLIC Metadata Guidelines):

     Australia
     Australian Captial Territory
     New South Wales
     New Zealand
     Northern Territory
     Queensland
     South Australia
     Tasmania
     Victoria
     Western Australia
     Other

See also the general discussion of keywords.

descript

Example:

<descript>
	<abstract>
		<p>This is the abstract.  This data was
		collected to:
		</p>
		<ul>
		<li>reason 1</li>
		<li>another point</li>
		</ul>
	</abstract>
	<theme>
		<keyword qualifier="monitoring">SOIL</keyword>
		<keyword>AQUACULTURE</keyword>
	</theme>
	<spdom>
		<place>
			<dsgpolyo>
				<long>134.0</long>
				<lat>-11.0</lat>
				<long>133.5</long>
				<lat>-11.0</lat>
				<long>133.5</long>
				<lat>-12.0</lat>
				<long>134.0</long>
				<lat>-12.0</lat>
			</dsgpolyo>
		</place>
		<place>
			<keyword thesaurus="auslig_topo250k_names">
				Wessel Islands
			</keyword>
		</place>
		<bounding>
			<northbc>-11.0</northbc>
			<southbc>-12.0</southbc>
			<eastbc>136.5.0</eastbc>
			<westbc>133.5</westbc>
		</bounding>
	</spdom>
</descript>

abstract

Can make use of block text elements (<p>, <ul>, etc).</dd>

theme

The theme of the dataset may be described using a number of keywords. In addition, data and/or attributes may be simultaneously collected for a number of different themes, hence multiple <theme> elements are possible. Refer to the ANZLIC Metadata Guidelines for the list of possible keywords.

spdom

The spatial domain consists of a detailed specification of places, plus an encompassing bounding box. This element is optional, since some datasets and/or projects may not be related to a specific spatial area. For example, a laboratory study may collect information generally relevent to a theme, but not specifically relevent to a spatial area.

place

A place is defined by a keyword, or by one or more polygons (eg. "Australia", or polygons covering the mainland and Tasmania). A polygon should not be given in addition to a name which describes that polygon, since this repeats the same information. The <place> element has been moved to within the <spdom> element to indicate its relevance to the spatial domain. A dataset which covers multiple distinct places or areas will have multiple <place> elements defined (eg. A study of 5 beaches in scattered locations). The place element is optional, because data may be available for a large area, eg. the southern hemisphere, for which the <bounding> element is a complete description of its spatial domain. Refer to the ANZLIC Metadata Guidelines for a list of possible keywords.

long,lat

The <dsgpolyo> element contains structured information, being a stream of points, but this structure was not specified in the previous DTD. Including the <long> and <lat> tags has made the structure available. Combining the pairs of <long> and <lat> elements into "coordinate" elements is not necessary, since the alternation between long and lat is fixed, and hence the structure is fully specified.

bounding

The <bounding> element contains an overall bounding box for the dataset, which indicate the outermost extent covering each listed <place>.

keyword

Keywords can have a qualifier and/or thesaurus defined as attributes. Qualifiers are additional attributes which could apply to any valid keyword. The thesaurus attribute is included to allow future definitions of keyword lists specific to themes, applications or agencies. It is envisaged that ANZLIC will maintain a list of valid thesauri. Thesaurus content can be delegated to the relevant agencies. For example, AUSLIG maintain a list of names and codes used to specify mapsheets in the Topographic Map Series.

There is an implied thesaurus with the name "anzlic" which applies to any keyword element that does not specify a thesaurus. This default thesaurus contains the keyword lists which appear in the ANZLIC Metadata Guidelines.

place - keyword

The default keyword thesaurus includes each of the place names listed in the ANZLIC Metadata Guidelines under the section "Geographic Extent Name". See also the general discussion of keywords.

theme - keyword

The default keyword thesaurus includes each of the theme Search Words listed in the ANZLIC Metadata Guidelines under the section "Search Word(s)". Any of the qualifiers listed in that section may also be used with the default thesaurus. See also the general discussion of keywords.

timeperd

Example:

<timeperd>
	<begdate>
		<date>
			1770-01-01
		</date>
	</begdate>
	<enddate>
		<keyword>
			current
		</keyword>
	</enddate>
</timeperd>

begdate, enddate

Prior to this DTD, these elements were declared as PCDATA, making it difficult for indexing programs to handle both numeric dates and keywords. These elements now must use one of two subelements, date or keyword, to clarify how the time information is being represented.

Allowable keywords for the begdate under the default thesaurus are:

	not known

Allowable keywords for the enddate under the default thesaurus are:

	current
	not known

See also the general discussion of dates and keywords.

date

Dates must be presented according to a subset of ISO 8601:

	Full date:	1993-02-14
	Month only:	1993-02
	Year only:	1993

status

Example:

<status>
	<progress>
		<keyword>
			complete
		</keyword>
	</progress>
	<update>
		<keyword>
			not planned
		</keyword>
	</update>
</status>

progress

Progress keywords for the default thesaurus:

	complete
	in progress
	planned
	not known

See also the general discussion of keywords.

update

Update / Maintenance Frequency keywords for the default thesaurus:

	continual
	daily
	weekly
	monthly
	quarterly
	bi-annually
	annually
	as required
	irregular
	not planned
	not known

See also the general discussion of keywords.

distinfo

Example:

<distinfo>
	<native>
		<nondig>
			<formname>
				Hardcopy maps drawn by ...
			</formname>
		</nondig>
	</native>
	<avlform>
		<digform>
			<formname>
				Arc/Info Export, Double
				Precision.  Single precision
				available on request.
			</formname>
		</digform>
		<digform>
			<formname>
				Raster Image in GIF or TIF
				format.
			</formname>
		</digform>
		<nondig>
			<formname>
				Assorted printed maps - Visit
				service center for samples.
			</formname>
		</nondig>
	</avlform>
	<accconst>
		Internal use in government at cost of transfer
		and restricted access licence for non
		government at negotiable price.
	</accconst>
</distinfo>

nondig,digform

These elements have been created to appear under <native> and <avlform> to allow nondigital and digital forms to have different structures at higher page levels.

avlform

Optional, as there may not be standard available forms for the information. For example, the data may be stored in a proprietary database system, or the dataset may not currently be available due to loss, damage or contractual obligations.

accconst

Can make use of block text elements (<p>, <ul>, etc - see the discussion at the top of this file).

dataqual

Example:

<dataqual>
	<lineage>
		<p>These are the basic datasets received from
		Marine laboratories.</p>
	</lineage>
	<posacc>
		<p>Positional error should not exceed 1km for
		the vast majority of pixel centres.</p>
	</posacc>
	<attracc>
		<p>As determined by CSIRO processing of
		spectral response and computation of NDVI, see
		'AVHRR DOCUMENTATION' held by Neil Freeman
		(ERIN).</p>
	</attracc>
	<logic>
		<p>The method of aggregation employed selects
		the maximum fortnightly value for output to
		each monthly pixel, so as to minimize
		atmospheric contamination - thus the monthly
		pixel values are cloud free.</p>
	 </logic>
	<complete>
		<p>All datasets are spatially complete - there
		are no missing sections. The data is
		temporally incomplete - March to November 1994
		are missing.</p>
	</complete>
</dataqual>

All subelements of dataqual can use block text elements (<p>, <ul>, etc - see the discussion at the top of this file).

cntinfo

Example:

<cntinfo>
	<cntorg>
		Environmental Resources Information Network
		(ERIN), Environment Australia 
	</cntorg>
	<cntpos>
		Scientific Coordinator - Remote Sensing
	</cntpos>
	<address>GPO Box 787</address>
	<city>Canberra</city>
	<state>ACT</state>
	<country>Australia</country>
	<postal>2620</postal>
	<cntvoice>+61 2 6274 1203</cntvoice>
	<cntfax>+61 2 6274 1333</cntfax>
	<cntemail>shane@erin.gov.au</cntemail>
</cntinfo>

Voice, fax and email address are optional depending on the how the agency prefers to be contacted.

metainfo

Example:

<metainfo>
	<metd>
		<date>
			1998-01-01
		</date>
	</metd>
</metainfo>

supplinf

Example:

<supplinf>
	<p>This dataset is available through any or our <a
	href="http://mydomain.com.au/resellers.html">resellers</a>.
	</p>
</supplinf>

This field has no metadata subelements, and can make use of block text elements (<p>, <ul>, etc).



URL: http://www.environment.gov.au/database/metadata/anzmeta/anzmeta-1.1.html
Last modified: 4 February 1998