Search by property

Jump to: navigation, search

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.

Search by property

A list of all pages that have property "terms-internal:enNote" with value "$$Walter$$ What is the description for this??". Since there have been only a few results, also nearby values are displayed.

Showing below up to 36 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)


    

List of results

    • abcd2:MultiMediaObject-ImageColourSpace-ProfileRef  + ($$Walter$$ no comments found)
    • abcd2:Gathering-Country-ISO3166Code  + ($$Walter$$ to follow this up (needs to add
      $$Walter$$ to follow this up (needs to add the ISO numerical code).; <br/><br/>Note: The letter code identifies a country name, NOT a physical territory. For the latter, there is a ISO 3166 numerical code. For exemple, when Germany reunified, it kept DE/DEU but changed from 280 to 276, while when Southern Rhodesia was renamed Zimbabwe it stayed 716 but changed from RH/RHO to ZW/ZWE.<br/><br/>See comments under Country.
      ><br/>See comments under Country.)
    • abcd2:TaxonIdentified-HigherTaxa  + ($$Yael$$ English?; Note that if a higher taxon such as a family name is the result of the identification itself, it should (also) be noted under Full-Scientific-Name-String (mandatory) and Genus-Or-Monomial (optional).)
    • abcd2:Gathering-NamedArea-DataSource  + ($$walter$$ From your comments here...It is presently not clear, what this reference refers to [WB])
    • ac:comments  + ('''Audubon Core:''' Comments may refer to
      '''Audubon Core:''' Comments may refer to the resource itself (e. g., asserting a taxon name or location of a biological subject in an image), or to the relation between resource and associated metadata (e. g., asserting that the taxon name given in the metadata is wrong, without asserting a positive identification). There is a separate item for Reviewer Comments, which is defined more as an expert-level review.
      is defined more as an expert-level review.)
    • ac:derivedFrom  + ('''Audubon Core:''' Derivation of one reso
      '''Audubon Core:''' Derivation of one resource from another is of special interest for identification tools (e. g. a key from an unpublished data set, as in FRIDA, or a PDA key from a PC or web key) or web services (e. g. a name synonymization service being derived from a specific data set). It may very rarely also be known where one image or sound recording is derived from another (but compare the separate mechanism to be used for quality/resolution levels). – Human readable, or doi number, or URL. Simple name of parent for human readable. Can be repeated if a montage of images.
      e. Can be repeated if a montage of images.)
    • ac:attributionLogoURL  + ('''Audubon Core:''' Entering this URL into a browser should only result in the icon (not in a webpage including the icon).)
    • ac:resourceCreationTechnique  + ('''Audubon Core:''' Examples: Encoding met
      '''Audubon Core:''' Examples: Encoding method or settings, numbers of channels, lighting, audio sampling rate, frames per second, data rate, interlaced or progressive, multiflash lighting, remote control, automatic interval exposure. Annotating whether and how a resource has been modified or edited significantly in ways that are not immediately obvious or expected to consumers is of special significance. Examples for images are: Removing a distracting twig from a picture, moving an object to a different surrounding, changing the color in parts of the image, or blurring the background of an image. Modifications that are standard practice and expected or obvious to users are not necessary to document; examples of such practices include changing resolution, cropping, minor sharpening or overall color correction, and clearly perceptible modifications (e.g. addition of arrows or labels, or the placement of multiple pictures into a table.) If it is only known that significant modifications were made, but no details are known, a general statement like “Media may have been manipulated to improve appearance” may be appropriate. See also Subject Preparation Technique.
      . See also Subject Preparation Technique.)
    • ac:providerManagedID  + ('''Audubon Core:''' Ideally, this would be
      '''Audubon Core:''' Ideally, this would be a globally unique identifier (GUID), but the provider is encouraged to supply any form of identifier that simplifies communications on resources within their project and helps to locate individual data items in the provider's data repositories. It is the provider's decision whether to expose this value or not.
      ision whether to expose this value or not.)
    • ac:caption  + ('''Audubon Core:''' If both description an
      '''Audubon Core:''' If both description and caption are present in the metadata, a description is typically displayed instead of the resource, a caption together with the resource. Often only one of description or caption is present; choose the concept most appropriate for your metadata.
      oncept most appropriate for your metadata.)
    • ac:captureDevice  + ('''Audubon Core:''' It is best practice to record the device; this may include a combination such as camera plus lens, or camera plus microscope.)
    • ac:metadataProvider  + ('''Audubon Core:''' Media items and Metadata may be served from different institutions, e. g. in the case of aggregators adding user annotations, taxon identifications, or ratings. Compare Provider.)
    • ac:provider  + ('''Audubon Core:''' Media items and Metadata may be served from different institutions, e. g. in the case of aggregators adding user annotations, taxon identifications, or ratings.)
    • ac:providerLiteral  + ('''Audubon Core:''' Media items and Metadata may be served from different institutions, e. g. in the case of aggregators adding user annotations, taxon identifications, or ratings.)
    • ac:physicalSetting  + ('''Audubon Core:''' Multiple values may be needed for movies or montages.)
    • ac:subjectOrientation  + ('''Audubon Core:''' No formal encoding scheme as yet exists. The term is repeatable e.g. in the case of a composite image, consisting of a combination of different view orientations.)
    • ac:subjectPart  + ('''Audubon Core:''' No formal encoding scheme as yet exists.)
    • ac:providerID  + ('''Audubon Core:''' Only to be used if the
      '''Audubon Core:''' Only to be used if the annotated resource is not a provider itself - this item is for relating the resource to a provider, using an arbitrary code that is unique for a provider, contributing partner, or aggregator, or other roles (potentially defined by MARC, OAI) and by which the media resources are linked to the provider.
      edia resources are linked to the provider.)
    • ac:taxonCount  + ('''Audubon Core:''' Primarily intended for
      '''Audubon Core:''' Primarily intended for resource collections and singular resources dealing with sets of taxa (e. g., identification tools, videos). It is recommended to give an exact or estimated number of specific taxa when a complete list of taxa is not available or practical. The count should contain only the taxa covered fully or primarily by the resource. For a taxon page and most images this will be “1”, i. e. other taxa mentioned on the side or in the background should not be counted. However, sometimes a resource may illustrate an ecological or behavioral entity with multiple species, e. g., a host-pathogen interaction; taxon count would then indicate the known number of species in this interaction. This should be a single integer number. Leave the field empty if you cannot estimate the information (do not enter 0). Additional taxon counts at higher levels (e. g. how many families are covered by a digital Fauna) should be given verbatim in the resource description, not here.
      tim in the resource description, not here.)
    • ac:reviewer  + ('''Audubon Core:''' Provider is asserting they accept this review as competent.)
    • ac:IDofContainingCollection  + ('''Audubon Core:''' Repeatable: A media resource may be member of multiple collections)
    • ac:licensingException  + ('''Audubon Core:''' Required only if this version has different licensing than that of the media resource. For example, the highest resolution version may be more restricted than lower resolution versions)
    • ac:reviewerComments  + ('''Audubon Core:''' Reviewer Comments may
      '''Audubon Core:''' Reviewer Comments may refer to the resource itself (e. g., asserting a taxon name or location of a biological subject in an image), or to the relation between resource and associated metadata (e. g., asserting that the taxon name given in the metadata is wrong, without asserting a positive identification). There is a separate item “Comments” for text from commenters of unrecorded expertise.
      t from commenters of unrecorded expertise.)
    • ac:hasServiceAccessPoint  + ('''Audubon Core:''' Some serializations ma
      '''Audubon Core:''' Some serializations may flatten the model of service-access points by (a) dropping ac:hasServiceAccessPoint, ac:variant and ac:variantDescription, (b) repeating the properties of the Service Access Point Vocabulary and prefixing them with values of ac:variant. If such a flat serialization is necessary for services, we recommend to select from among terms of the form "AB" where "A" is one of thumbnail, trailer, lowerQuality, mediumQuality, goodQuality, bestQuality, offline and "B" is one of AccessURI, Format, Extent, FurtherInformationURL, LicensingException, ServiceExpectation (example: thumbnailAccessURI). Implementers in specific constraint languages such as XML Schema or RDF may wish to make Access URI and perhaps dcterms:format mandatory on instances of the service access point.
      on instances of the service access point.)
    • ac:associatedSpecimenReference  + ('''Audubon Core:''' Supports to find a spe
      '''Audubon Core:''' Supports to find a specimen resource, where additional information is available. If several resources relate to the same specimen, these are implicitly related. Examples: for NHM “BM 23974324” for a barcoded or “BM Smith 32” for a non-barcoded specimen; for UNITS: “TSB 28637”; for PMSL: “PMSL-Lepidoptera-2534781”. Ideally this could be a URI identifying a specimen record that is available online.
      specimen record that is available online.)
    • ac:tag  + ('''Audubon Core:''' Tags may be multi-worded phrases. Where scientific names, common names, geographic locations, etc. are separable, those should go into the more specific coverage metadata items provided further below.)
    • ac:subjectCategoryVocabulary  + ('''Audubon Core:''' The AC recommended voc
      '''Audubon Core:''' The AC recommended vocabularies do not need to be cited here. There is no linkage between individual Subject Category terms and the vocabulary; the mechanism is intended to support discovery of the normative URI for a term, but not guarantee it.
      tive URI for a term, but not guarantee it.)
    • ac:licenseLogoURL  + ('''Audubon Core:''' The originating metada
      '''Audubon Core:''' The originating metadata provider is strongly urged to choose a suitable logo as a graphical representation of the license. Failure to do so may leave downstream aggregators in a difficult position to supply a logo that adequately represents the professional, legal, or social aims of the licensors (license givers).
      al aims of the licensors (license givers).)
    • ac:scientificNameSynonym  + ('''Audubon Core:''' The primary purpose of
      '''Audubon Core:''' The primary purpose of this is in support of resource discovery, not developing a taxonomic synonymy. Misidentification or misspellings may thus be of interest.<br/>Where multiple taxa are present in a resource and multiple Scientific Taxon Names are given, the association between synonyms and names may not be deducible from the AC record alone.
      not be deducible from the AC record alone.)
    • ac:attributionLinkURL  + ('''Audubon Core:''' This URL may be used i
      '''Audubon Core:''' This URL may be used in creating a clickable logo. Providers should consider making this link as specific and useful to consumers as possible, e. g., linking to a metadata page of the specific image resource rather than to a generic page describing the owner or provider of a resource.
      ibing the owner or provider of a resource.)
    • xmp:Rating  + (<b>Audubon Core:</b> A rating
      <b>Audubon Core:</b> A rating of the media resources, provided by users or editors, with -1 defining “rejected”, “0” defining “unrated”, and “1” (worst) to “5” (best). The origin of the rating is not communicated. It may, e. g., be based on user feedback or on editorial ratings. If Rating is not present, a value of 0 may be assumed. 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.4] for further documentation. XMP Schema is defined in RDF, not w3c schema.
      Schema is defined in RDF, not w3c schema.)
    • photoshop:Credit  + (<b>Audubon Core:</b> Free text
      <b>Audubon Core:</b> Free text for "Please cite this as…" 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:Sublocation  + (<b>Audubon Core:</b> Free-form
      <b>Audubon Core:</b> Free-form text location details of the location of the subjects, down to the village, forest, or geographic feature etc., below the city or other place name, especially information that could not be found in a gazetteer. Audubon Core distinguishes Locality in the sense of Darwin Core ( = a complete description of a locality, with the possible exception of country names etc., which can be separated into dwc:HigherGeography), and Sublocation in the sense of IPTC/XMP, i.e. the further details below a city or other place name, of a free-form text location within a fully hierarchically arranged grouping (earlier IPTC versions used “Location”, but this has been renamed as of 2008). 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.)
    • dcterms:language  + (<b>Audubon Core:</b> Language(
      <b>Audubon Core:</b> Language(s) of resource itself represented in ISO639-1 or -3 An image may contain language such as superimposed labels. If an image is of a natural scene or organism, without any language included, the resource is language-neutral (ISO code “zxx”). Resources with present but unknown language are to be coded as undetermined (ISO code “und”). Resources only containing scientific organism names should be coded as "zxx-taxon" (do not use the incorrect “la” for Latin). For regional dialects or other special cases, conform to the [http://tools.ietf.org/html/rfc5646 IETF Best Practices for Tags Identifying Languages]. As of 2012-04-11, the Dublin Core metadata Initiative recommends the use of a controlled vocabulary such as RFC 4646. For '''Darwin Core''', the latest RFC for ISO 639-1 is the recommended version (RFC 5646 as of 2012-04-11). Further documentation on the Internet Engineering Task Force (IETF) language codes can be found at http://en.wikipedia.org/wiki/IETF_language_tag. A list of language codes can be found at http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes.
      ikipedia.org/wiki/List_of_ISO_639-1_codes.)
    • Iptc4xmpExt:WorldRegion  + (<b>Audubon Core:</b> Name of a
      <b>Audubon Core:</b> Name of a world region in some high level classification, such as names for continents, waterbodies, or island groups, whichever is most appropriate. The terms preferably are derived from a controlled vocabulary. The equivalent Darwin Core fields here forces primary metadata providers to classify world region terms into separate properties for “continent” “waterbody”, “IslandGroup”. By contrast, the Iptc4xmpExt vocabulary only specifies that a World Region is something at the top of a hierarchy of locations. 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.)