About NZOR‎ > ‎

Glossary

TFBIS Programme – The Terrestrial Freshwater Biodiversity Information System Programme which is funded by the Government to help to achieve the goals of the New Zealand Biodiversity Strategy through facilitating and funding data management systems and processes. It is administered by the Department of Conservation.

TFBIS Contract 214 – the contract between TFBIS and Landcare Research to run the first year (and possible second and third years) of the project to develop NZOR

Stakeholder – A person or group with an interest in NZOR.  This will include data providers, users and funders.

Data provider – An individual or organisation who provides nomenclatural, taxonomic and biostatus data (and associated metadata) to NZOR

End user – An individual or organisation who uses NZOR to obtain data on organism names

Contractor – a person(s) or organisation that has received funding to develop, enhance or maintain NZOR

Project Leader – the leader of any contracted project that is active in the development, enhancement or maintenance of the NZOR platform

Technical Leader – the technical leader of any contracted project that is active in the development enhancement or maintenance of the NZOR platform

Information system – a computer system including descriptive schema, such as database designs, XML schema and software architecture.

Provider Data – nomenclatural, taxonomic and biostatus data (and associated metadata) that are made available to NZOR by participating agencies. Any data generated by end user agencies and managed within the NZOR platform

NZOR Data – data generated within or by the NZOR platform (for example, consensus records, statistical analyses, and taxonomic management hierarchies)

NZOR Platform – the information systems which receives Provider Data and delivers NZOR.

Metadata – documentation that describes the data and information.

Data Provision and Use Agreement – a single document establishing an agreement between NZOR and a data provider and/or data consumer, establishing the terms, conditions, responsibilities and expectations regarding limitation of liability, intellectual property rights, standards, quality, and service levels.

Creative Commons – aims to establish a fair middle way between extremes of copyright control and the uncontrolled uses of intellectual property.  It provides a range of copyright licences, available to the public, which allow those owning or creating intellectual property – including organisations and individuals – to mark their work with the freedoms they want it to carry.

International Initiatives:
  • ITIS - Integrated Taxonomic Information System (www.itis.gov)
  • EOL - Encyclopedia of Life (www.eol.org)
  • GBIF - Global Biodiversity Information Facility – (www.gbif.org)
  • ECAT - The electronic catalogue of names of known organisms, part of the GBIF programme (www.gbif.org/informatics/name-services/)
  • GNA - Global Names Architecture, an effort to coordinate multiple interests in developing common solutions for creating a complete and integrated taxonomic framework for all names (www.gbif.org/informatics/name-services/global-names-architecture/)
  • TDWG - Taxonomic Databases Working Group, now known as Biodiversity Information Standards, an organisation focused on the development of standards for the exchange of biological/biodiversity data (www.tdwg.org)
  • eBiosphere - An International Conference on Biodiversity Informatics (www.e-biosphere09.org)
  • 4D4Life - Distributed Dynamic Diversity Databases for Life, An EU Framework 7 project (www.4d4life.eu)
  • ALA - The Atlas of Living Australia, a project to develop a biodiversity data management system which will link Australia’s biological knowledge with its scientific and agricultural reference collections and other custodians of biological information. (www.ala.org.au)
  • APNI - Australian Plant Name Index (www.anbg.gov.au/apni/)
Standards:
  • XML Extensible Markup Language a W3C-recommended general-purpose markup used for describing many different kinds of data. XML contains both the data and the description of the data.
  • RDFThe Resource Description Framework (RDF) is a family of World Wide Web Consortium (W3C) specifications originally designed as a metadata data model. It has come to be used as a general method for conceptual description or modeling of information that is implemented in web resources; using a variety of syntax formats.
  • SOAP originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on Extensible Markup Language (XML) as its message format, and usually relies on other Application Layer protocols (most notably Remote Procedure Call (RPC) and HTTP) for message negotiation and transmission. SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built.
  • WCF Windows Communication Foundation is an application programming interface in the .NET Framework for building connected, service-oriented applications.
  • REST Representational state transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. The term Representational State Transfer (REST) was introduced and defined in 2000 by the doctoral dissertation of Roy Fielding, one of the principal authors of the Hypertext Transfer Protocol (HTTP) specification versions 1.0 and 1.1.
  • URI  a Uniform Resource Identifier consists of a string of characters used to identify or name a resource on the Internet. Such identification enables interaction with representations of the resource over a network (typically the World Wide Web) using specific protocols. Computer scientists may classify a URI as a locator (URL), or a name (URN), or both. A Uniform Resource Name (URN) functions like a person's name, while a Uniform Resource Locator (URL) resembles that person's street-address. In other words: the URN defines an item's identity, while the URL provides a method for finding it.
  • Linked Data - a sub-topic of the Semantic Web. The term Linked Data is used to describe a method of exposing, sharing, and connecting data via dereferenceable URIs on the Web. See linkeddata.org.
  • GUIDglobally unique identifier is a special type of identifier used in software applications to provide a reference number which is unique in any context (hence, "globally"), for example, in defining the internal reference for a type of access point in a software application, or for creating unique keys in a database. While each generated GUID is not guaranteed to be unique, the total number of unique keys (2128 or 3.4×1038) is so large that the probability of the same number being generated twice is extremely small.
  • LSID Life Science Identifiers are persistent, location-independent, resource identifiers for uniquely naming biologically significant resources including species names, concepts, occurrences, genes or proteins, or data objects that encode information about them. To put it simply, LSIDs are a way to identify and locate pieces of biological information on the web.
  • TAPIR - the TDWG Access Protocol for Information Retrieval, a Web Service protocol to perform queries on biodiversity data across distributed databases of varied physical and logical structure.
  • TCS The TCS schema was conceived to allow the representation of taxonomic concepts as defined in published taxonomic classifications, revisions and databases. As such, it specifies the structure for XML documents to be used for the transfer of defined concepts. Valid transfer documents may either explicitly detail the defining components of taxon concepts, transfer GUIDs referring to defined taxon concepts (if and when these are available) or a mixture of the two.
  • IPT - the Integrated Publishing Toolkit is a software platform to facilitate the efficient publishing of biodiversity data on the Internet, using the GBIF network.
  • OAI-PMHOpen Archives Initiative Protocol for Metadata Harvesting is a protocol developed by the Open Archives Initiative. It is used to harvest (or collect) the metadata descriptions of the records in an archive so that services can be built using metadata from many archives. An implementation of OAI-PMH must support representing metadata in Dublin Core, but may also support additional representations.