Search by property

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

List of results

• dcterms:rights  + (<b>Dublin Core:</b> Typically, …
  <b>Dublin Core:</b> Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights. <b>Audubon Core:</b> Copyright Statement contains information about rights held in and over the resource. A full-text, readable copyright statement, as required by the national legislation of the copyright holder. On collections, this applies to all contained objects, unless the object itself has a different statement. Do not place just the name of the copyright holder(s) here! That belongs in a list in the xmpRights:Owner field, which should be supplied if dcterms:rights is not 'Public Domain', appropriate only if the resource is known to be not under copyright.
  source is known to be not under copyright.)
• dcterms:references  + (<b>Dublin Core</b> This term i …
  <b>Dublin Core</b> This term is intended to be used with non-literal values as defined in the DCMI Abstract Model (http://dublincore.org/documents/abstract-model/). As of December 2007, the DCMI Usage Board is seeking a way to express this intention with a formal range declaration.
  intention with a formal range declaration.)
• xmpRights:WebStatement  + (<b>Extensible Metadata Platform (XMP …
  <b>Extensible Metadata Platform (XMP):</b> This is a normal (non-URI) simple value because of historical usage. <b>Audubon Core:</b> A URL defining or further elaborating on the license statement (e. g., a web page explaining the precise terms of use). The value of this field may provide a complete definition of the terms of use. For Creative Commons, the appropriate value is the URL of the defining Web page for the license. Where different quality variants (e. g. resolutions of images) are published under different licenses, the AC term “Licensing Exception Statement” supports variant-specific licenses. Note: URIs of Adobe XMP terms are not resolvable. Visit [http://www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/XMPSpecificationPart1.pdf XMP Specification Part 1, Sec 8.5] for further documentation. XMP Schema is defined in RDF, not w3c schema.
  Schema is defined in RDF, not w3c schema.)
• Iptc4xmpExt:LocationCreated  + (<b>IPTC Photo Metadata:</b> If …
  <b>IPTC Photo Metadata:</b> If the location in the image is different from the location the photo was taken the [[Iptc4xmpExt:LocationShown|IPTC Extension property Location Shown]] in the Image should be used. <b>Audubon Core:</b> The location at which the media recording instrument was placed when the media was created. The distinction between location shown and created is often irrelevant, and metadata may be assumed to be referring to location shown. It is recommended that the Location Shown field above always be used when known. However, in the case of position data automatically recorded by the instrument (e. g. EXIF GPS data) Location Created should be used to maintain information accuracy. When one but not both of Location Shown and Location Created are present, AC is silent about whether the provided one entails the other. A best practices document for a particular AC implementation might address this. Note: URIs of IPTC terms for Adobe XMP terms are not resolvable. Visit [http://www.iptc.org/std/photometadata/specification/IPTC-PhotoMetadata-201007_1.pdf IPTC Standard Photo Metadata (July 2010)] for further documentation.
  ta (July 2010)] for further documentation.)
• Iptc4xmpExt:LocationShown  + (<b>IPTC Photo Metadata:</b> If …
  <b>IPTC Photo Metadata:</b> If the location the image was taken in is different from this location the [[Iptc4xmpExt:LocationCreated|property Location Created]] should be used too. <b>Audubon Core:</b> The location that is depicted the media content, irrespective of the location at which the resource has been created.
  on at which the resource has been created.)
• ac:variant  + (<br/> * Thumbnail: ServiceAccessPoin …
  <br/> * Thumbnail: ServiceAccessPoint provides a thumbnail image, short sound clip, or short movie clip that can be used in addition to the resource to represent the media object, typically at lower quality and higher compression than the preview object. A typical size for a tiny thumbnail image may be 50-100 pixels in the longer dimension. * Trailer: ServiceAccessPoint provides video clip preview, in the form of a specifically authored "Trailer", which may provide somewhat different content than the original resource. * Lower Quality: ServiceAccessPoint provides a lower quality version of the media resource, suitable e. g. for web sites. * Medium Quality: ServiceAccessPoint provides a medium quality version of the media resource, e. g. shortened in duration, or reduced size, using lower resolution or higher compression causing moderate artifacts. * Good Quality: ServiceAccessPoint provides a good quality version of the media resource intended for resources displayed as primary information; e. g. an image between 800 and 1600 px in width or height. * Best Quality: ServiceAccessPoint provides the highest available quality of the media resource, whatever its resolution or quality level. * Offline: ServiceAccessPoint provides data about an offline resource.
  t provides data about an offline resource.)
• abcd2:EAnnotations  + (>Note that for annotation labels captured from the specimen there is the {{{SpecimenUnit/Marks}}} structure (AbcdConcept0561).)
• tp:nomenclature-citation  + (A citation can be very detailed including …
  A citation can be very detailed including all the elements of a nomenclatorial event, that is the original combination of the name, the original publication including often the page of publication, type specimen and its depository institution and current status. The citation can also be complemented by the indication that this particular taxon is being synonymized with the nominate taxon, its status is being changed, its being a homonym, or all of this happened in an earlier publication which is then followed by a complementary bibliographic reference. A citation can also be a reference to a so far unknown life form (eg. male, larvae), karyotype or chance of the status of type, such as the selection of a neotype or a lectotype.
  the selection of a neotype or a lectotype.)
• rdfs:domain  + (A domain of the subject property.)
• skos:notation  + (A notation is different from a lexical label in that a notation is not normally recognizable as a word or sequence of words in any natural language. By convention, skos:notation is used with a typed literal in the object position of the triple.)
• dcterms:contributor  + (A person, an organization, or a service.)
• rdfs:range  + (A range of the subject property.)
• dc:title  + (A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.)
• tp:taxon-treatment  + (A treatment can be anything from very shor …
  A treatment can be anything from very short to very long.<br /> A treatment must have a nomenclature element and at least one of the following:<br /> * a citation list (<[[taxpub:nomenclature-citation-list | tp:nomenclature-citation-list]]>) * a citation of a nomencaltorial act or an earlier published record (<[[taxpub:nomenclature-citation | tp:nomenclature-citation]]>) * a text, commentary or key on the particular taxon (<[[taxpub:treatment-sec | tp:treatment-sec]]>)
  ub:treatment-sec | tp:treatment-sec]]>))
• abcd2:Gathering-SpatialDatum  + (ABCD Workshop 1)
• abcd2:Gathering-GridCellCode  + (ABCD Workshop 1<br/><br/>$$Wal …
  ABCD Workshop 1<br/><br/>$$Walter$$ Please review the elements relating to coordinates when you get to it - some are missing information, and I have improvised at times (as here). (I know there are a few that are in the EURISCO doc you sent, which I still have to review)
  oc you sent, which I still have to review))
• dcterms:accessRights  + (Access Rights may include information regarding access or restrictions based on privacy, security, or other policies.)
• sandbox:accessRights  + (Access Rights may include information regarding access or restrictions based on privacy, security, or other policies.)
• abcd2:SpecimenUnit-TypifiedName  + (An alternative solution to this unstructur …
  An alternative solution to this unstructured element would be the use of the scientific name structure given under identification.<br/><br/>It has been suggested to treat the type assignation as a special case of identification. Although this is without doubt true, it would mean to introduce the entire typification structure to the identification structure (because more than on name may be directly typified by the same specimen). As nomeclatural types are only a subtype of specimens, and these are only a subtype of units, it was decided to assign the typified name in the specimen domain. If it is to be found by a normal name search, it should be repeated as an identified name under identifications.
  an identified name under identifications.)
• dwc:measurementUnit  + (An explanation of the International System of Units can be found at http://physics.nist.gov/cuu/Units/.)
• abcd2:TechnicalContact-@preferred  + (As a rule, the group of the "recommended" attribute should be set to the same as the corresponding element.)
• skos:broader  + (Broader concepts are typically rendered as parents in a concept hierarchy (tree). By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.)
• skos:broaderTransitive  + (By convention, skos:broaderTransitive is n …
  By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.
  pansion algorithm in a search application.)
• abcd2:Gathering-LocalityText  + (Clarification is needed as to whether this field includes the full locality information from the Continental level down, or just regional locality string excluding the higher level named areas or regions [JRC])
• abcd2:Gathering-Country  + (Country names and ISO codes can theoretically be part of controlled enumerations but if included within the schema would blow it out to an unacceptable level; is it possible to refer to these lists externally with physically invoking them? [JRC])

• ggbnvoc:Genetically Modified Organism  + (Currently a placeholder only, might be renamed in the future)

• dwcattributes:abcdEquivalence  + (Currently mapped to ABCD 2.06b)
• dcterms:Location  + (Darwin Core location terms can be grouped …
  Darwin Core location terms can be grouped into three subcategories - geographic terms, verbatim coordinate terms, and georeference terms. ===Geographic Terms=== Geographic terms include * [[dwc:higherGeography]] * [[dwc:continent]] * [[dwc:countryCode]] * [[dwc:stateProvince]] * [[dwc:county]] * [[dwc:municipality]] A good reference for place names is the Getty Thesaurus of Geographic Names (TGN), which can be found at http://www.getty.edu/research/conducting_research/vocabularies/tgn/. Administrative boundary files can be obtained from the Global Administrative Areas (GADM) data set at http://biogeo.berkeley.edu/gadm/. MARC records for geographic names, including URIs, can be found at http://id.loc.gov/vocabulary/geographicAreas.html. ===Verbatim Coordinate Terms=== Verbatim coordinate terms include: * [[dwc:verbatimLatitude]] * [[dwc:verbatimLongitude]] * [[dwc:verbatimCoordinateSystem]] * [[dwc:verbatimSRS]] The terms beginning with verbatim are meant to capture the original record of the coordinates of the Location. verbatimCoordinates is meant to capture coordinates that have not or cannot be separated into the verbatimLatitude and verbatimLongitude. If the coordinates can be separated, they should be, since there is less chance to misinterpret the content. The verbatimCoordinateSystem and the verbatimSRS both refer to the values in verbatimLatitude and verbatimLongitude, or to the value in verbatimCoordinates. ===Georeference Terms=== * [[dwc:decimalLatitude]] * [[dwc:decimalLongitude]] * [[dwc:geodeticDatum]] * [[dwc:georeferenceProtocol]] * [[dwc:georeferenceVerificationStatus]] * [[dwc:footprintSRS]] Further detailed explanations of the terms associated with georeferences (spatial descriptions of place using points, circles, lines, polygons, etc.) can be found in the Guide to Best Practices for Georeferencing http://www.gbif.org/prog/digit/Georeferencing.
  ://www.gbif.org/prog/digit/Georeferencing.)
• dcterms:date  + (Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].)
• dc:date  + (Date may be used to express temporal infor …
  Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF]. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• biorel:derived by descent from  + (Definition in RO: "d derived_by_descent_from a if d is specified by some genetic program that is sequence-inherited-from a genetic program that specifies a.")
• dc:description  + (Description may include but is not limited …
  Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• dwc:pointRadiusSpatialFit  + (Detailed explanations with graphical examples can be found in the "Guide to Best Practices for Georeferencing", Chapman and Wieczorek, eds. 2006.)
• biorel:participates in  + (Do not use this term for spatial "participation".)
• biorel:has participant  + (Do not use this term for spatial "participation".)
• abcd2:PlantGeneticResourcesUnit-AncestralData  + (Example for transfer of EURISCO information to ABCD documentation.)
• dc:creator  + (Examples of a Creator include a person, an …
  Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• dcterms:publisher  + (Examples of a Publisher include a person, an organization, or a service.)
• dc:publisher  + (Examples of a Publisher include a person, …
  Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• dc:format  + (Examples of dimensions include size and du …
  Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME]. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• dwc:originalNameUsage  + (For an original name usage record, the nam …
  For an original name usage record, the nameAccordingTo value should match the namePublishedIn value. * A description of basionym and basonym can be found at http://en.wikipedia.org/wiki/Basionym. * Good examples for synonyms, basionyms, replaced names, etc. can be found in http://www.peabody.yale.edu/other/PROTEM/TAXSIG/taxonomy_synonyms_examples.pdf.
  TEM/TAXSIG/taxonomy_synonyms_examples.pdf.)
• dwc:organismQuantity  + (For discussion see http://terms.tdwg.org/wiki/dwc:organismQuantity.)
• dwc:organismQuantityType  + (For discussion see http://terms.tdwg.org/wiki/dwc:organismQuantityType.)
• dwc:parentEventID  + (For discussion see http://terms.tdwg.org/wiki/dwc:parentEventID.)
• dwc:sampleSizeUnit  + (For discussion see http://terms.tdwg.org/wiki/dwc:sampleSizeUnit.)
• dwc:sampleSizeValue  + (For discussion see http://terms.tdwg.org/wiki/dwc:sampleSizeUnit.)
• dwc:relatedResourceID  + (For discussion see http://code.google.com/p/darwincore/wiki/ResourceRelationship)
• dwc:relationshipAccordingTo  + (For discussion see http://code.google.com/p/darwincore/wiki/ResourceRelationship)
• dwc:relationshipRemarks  + (For discussion see http://code.google.com/p/darwincore/wiki/ResourceRelationship)
• dwc:resourceID  + (For discussion see http://code.google.com/p/darwincore/wiki/ResourceRelationship)
• dwc:resourceRelationshipID  + (For discussion see http://code.google.com/p/darwincore/wiki/ResourceRelationship)