Terminology Reference System Content Characterization

Linda Spencer (EPA)
2005-03-15

I. Introduction and Usage

II. Core Content Characterization

Title*

Terminology Reference System

Acronym

TRS

One of the following (Web page(s), Identifier, or Contact Information) is mandatory:

Web page(s)

http://www.epa.gov/trs/

Contact Information

Linda H. Spencer

2822T

USEPA Headquarters

Ariel Rios Building

1200 Pennsylvania Avenue, N. W

Washington, DC 20460

202-566-1651

spencer.linda@epa.gov



Inclusion Rationale*

The Terminology Reference System (TRS) has been created as a single resource of environmental terminology for the Agency by compiling collections of terms from EPA, Agency program offices, information systems, state collections and other sources. The TRS stores and displays hierarchical term collections. The content of the TRS supports the Agency's Data Standardization Process.

TRS is one of the terminology structures related to the extension of ISO-11179 to cover complex terminology structures.

Environmental Protection Agency is one of the interested sponsoring organizations of XMDR.

Subject*

Environmental data

Environmental terminology

Kind of Metadata*

Size statistics (estimated)*

Number of Environmental Terms in TRS = 11977

Number of groups = 255

Size in bytes of internal representation = 11 MB

Initial Submitter*

On behalf of Linda Spencer, EPA:

Toni Ogungbaige (toni.ogungbaigbe@lmco.com)

Date of Initial Survey*

2005-01-20

III. Supplementary Content Characterization

The following attributes of the content characterization will be completed by XMDR staff. These attributes will be collected for those content collections which are considered to be high priority for inclusion in the prototype.

Attributes marked with an asterisk (*) are considered mandatory.

Date*

Publication date of most recent version of the metadata resource in ISO 8601 Date Format: YYYY-MM-DD. Taken from Dublin Core Metadata Element Set, Version 1.1: Reference Description.

Creator

Organization or person(s) responsible for the creation (authoring) of the metadata resource. Taken from Dublin Core Metadata Element Set, Version 1.1: Reference Description.

Publisher*

Organization or person(s) responsible for publishing / distributing the metadata resource. Note that we do not differentiate here between publishers and distributors. Taken from Dublin Core Metadata Element Set, Version 1.1: Reference Description.

Description*

Additional textual description of the metadata resource.

Language(s)*

Language(s) of the content of the metadata resource. Is the metadata resource multi-lingual (e.g., thesauri)? Taken from the Dublin Core Metadata Element Set, Version 1.1: Reference Description.

Graph-theoretic Classification*

Indicate type of metadata according to the following graph-theoretic classification scheme:

Format / Schemas(s)*

What file formats (ASN.1, XML, RDF, KIF, HDF5, netCDF, ... ) can the metadata resource be had in? What schemas are used (e.g., for XML, RDF, ...)

Media / Download*

Is the metadata resource available for download? What are the principal / mirror download sites ? What media types (CDROM, DVD, ...) are available (if any)?

Constraint Specifications

Does the metadata resource include constraints? What kinds of constraints (keys, foreign keys, ....)? How are constraints specified (SQL, logic, RuleML, SWRL, Object Constraint Language, ...) ?

Protocol(s)

What protocols does the metadata publisher support for download, other access, e.g., FTP, HTTP, REST, SOAP, UDDI, LDAP, etc.

Licensing Issues*

Open source, public domain, academic use, proprietary license, .... License agreement required ? Cost of license? Can content be redistributed or posted to the web?

Export restrictions

Restrictions on export / distribution ?

Subsets

Is there some subset of the metadata resource which would be of interest? Can we request / extract / query this subset for the originating site or will we have to obtain the complete metadata resource content and then perform the subset extraction query processing on our system?

Versions, Updates

What is the current version number of the metadata resource? How often is the metadata resource updated? How are updates named / distributed / propagated ?

Documentation

What documentation is available? Where / how to obtain documentation ? Format of documentation ?

Character Set Encoding*

Is the data set encoded in ASCII, Unicode (and if so what character encoding UTF-8, UTF-16, ...), or other?

Measurement units

What system of measurement units (e.g., SI, cgs, US customary, ... ) is used (if any)? How are they encoded ?

Dataset / Standards Dependencies

Indicate any dependencies of this metadata resource on other metadata resources or standards, e.g., country codes, terminologies, chemical or biological nomenclature standards, etc.

Related Datasets

Other similar or related metadata resources.

Software tools

What software tools are available to parse, load, convert, browse, edit, .... this metadata resource (type)?

Audience(s)

Who is the primary intended audience for this data set? Expert researchers, DBAs, scientific users, agency staffers, librarians, statisticians, teachers, general public, college students, high school students, ...

Citation

How should the metadata resource be cited in publications, etc. ? Note that the preferred bibliographic citation is often a publication rather than the web site for a resource.

Surveyor*

Person who filled out this section of the survey for this metadata resource. Contact info also.

Date of Survey*

Date this survey was completed / updated for this metadata resource.

IV. Content Characterization by XMDR Staff

The following data elements are to be supplied by XMDR project staff/collaborators.

Attributes marked with an asterisk (*) are considered mandatory.

XMDR Participant Expertise

Names of persons (if any) on XMDR project (and contact info) who are familiar with this data set. XMDR participant organizations who have copies of this metadata resource.

XMDR Evaluator*

Names of persons on XMDR project (and contact info) who evaluated this metadata resource for inclusion (e.g., if the content survey was completed by someone at the content repository).

Inclusion Priority*

Priority suggested for acquisition and ingestion of this metadata resource.



Maintained by Frank Olken at Lawrence Berkeley National Laboratory. olken@lbl.gov Last updated: 2004-08-31, Tuesday