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 "skos:note" with value "en:$$Walter$$ What is the description for this??". Since there have been only a few results, also nearby values are displayed.

Showing below up to 26 results starting with #1.

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


    

List of results

  • dwc:taxonRank  + (en:The GBIF recommended controlled value v
    en:The GBIF recommended controlled value vocabulary can be found at http://rs.gbif.org/vocabulary/gbif/rank.xml and includes the following (English, followed by Latin in parentheses): kingdom (regnum) <br /> subkingdom (subregnum) division or phylum (divisio or phylum) <br /> subdivision or subphylum (subdivisio or subphylum) <br /> class (classis) <br /> subclass (subclassis) <br /> order (ordo) <br /> suborder (subordo) <br /> family (familia) <br /> subfamily (subfamilia) <br /> tribe (tribus) <br /> subtribe (subtribus) <br /> genus (genus) <br /> subgenus (subgenus) <br /> section (sectio) <br /> subsection (subsectio) <br /> series (series) <br /> subseries (subseries) <br /> species (species) <br /> subspecies (subspecies) <br /> variety (varietas) <br /> subvariety (subvarietas) <br /> form (forma) <br /> subform (subforma) <br /> See also the discussion at http://vocabularies.gbif.org/vocabularies/taxonomic_status.
    es.gbif.org/vocabularies/taxonomic_status.)
  • dwc:measurementType  + (en:For discussion see http://code.google.com/p/darwincore/wiki/MeasurementOrFact)
  • dwc:taxonRemarks  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Taxon)
  • dwc:measurementRemarks  + (en:For discussion see http://code.google.com/p/darwincore/wiki/MeasurementOrFact)
  • dwc:locationRemarks  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Location)
  • dwc:datasetID  + (en:For discussion see http://code.google.com/p/darwincore/wiki/RecordLevelTerms)
  • dwc:scientificNameID  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Taxon)
  • abcd2:Gathering-Depth-@datum  +
  • ac:subjectPart  + (en:'''Audubon Core:''' No formal encoding scheme as yet exists.)
  • abcd-efg:StratigraphicSectionImage-ImageColorSpace  +
  • abcd-efg:SectionUnitImage-ImageColorSpace  +
  • abcd2:SpecimenUnit-NomenclaturalReference  + (en:$$Walter$$ All it says for this is a 'published reference' - (is this a reference citing the type designation)?)
  • abcd2:Gathering-SiteImage-IPRStatements  + (en:$$Walter$$ Apropos your comments to me
    en:$$Walter$$ Apropos your comments to me in 0004, I was unsure what group to put for this element. I will group the IPR elements under this as Meta-IPRS, but this element is in the context of Gathering site images. Shall I group this page as Gathering or Media-Multimedia?
    his page as Gathering or Media-Multimedia?)
  • abcd2:Gathering-SiteImage-ImageColourSpace  + (en:$$Walter$$ Element under discussion<br/>See Bob Morris' comments under http://efgblade.cs.umb.edu/twiki/bin/view/BDEI/ColorManagement)
  • abcd2:SpecimenUnit-TypifiedName-SubgenusAuthorAndYear  + (en:$$Walter$$ I am filling in these now -I am not sure how to phrase information about nomenclatural type designation elements with brevity ...? Is there a shorter way to say these (eg 'type subgenus' etc)?)
  • abcd2:GatheringAgent-Organisation-Name  + (en:$$Walter$$ I realized I seem to have ma
    en:$$Walter$$ I realized I seem to have made an error in defining the representation element itself as container in most places. Just to double check with you - shall I change it to define the Organization/Name as a repeatable container for Representation (which I will change to Agent)?
    esentation (which I will change to Agent)?)
  • abcd2:Gathering-ChronostratigraphicTerm-Domain  + (en:$$Walter$$ Is this phrasing correct - "chronostratigraphic term for the gathering site"?)
  • abcd2:GatheringAgent-@primarycollector  + (en:$$Walter$$ Please review...I just altered the comments used for primary attributes...)
  • abcd2:Gathering-Altitude-LowerValue  + (en:$$Walter$$ The comment about the attribute for ValueDataTpe - is that still relevant?)
  • abcd2:MultiMediaObject-ImageColourSpace  + (en:$$Walter$$ The comments indicates this is an element under discussion. Do you want me to leave it blank for now?)
  • abcd2:Sequence-IDinDatabase  + (en:$$Walter$$ The elements under sequence seem to have examples but not really descriptions. Can you check the descriptions I added?)
  • abcd2:MycologicalSexualStage  + (en:$$Walter$$ What comments go here?)
  • abcd2:CultureCollectionUnit-Applications  + (en:$$Walter$$ What comments go here?)
  • abcd2:CultureCollectionUnit-Hazard  + (en:$$Walter$$ What comments go here? (none in schema))
  • abcd2:CultureCollectionUnit-Aerobicity  + (en:$$Walter$$ What descriptions go here? There is nothing in the schema for this element.)
  • abcd2:MultiMediaObject-ImageColourSpace-ProfileRef  + (en:$$Walter$$ no comments found)
  • abcd2:Gathering-Country-ISO3166Code  + (en:$$Walter$$ to follow this up (needs to
    en:$$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  + (en:$$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  + (en:$$walter$$ From your comments here...It is presently not clear, what this reference refers to [WB])
  • ac:comments  + (en:'''Audubon Core:''' Comments may refer
    en:'''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  + (en:'''Audubon Core:''' Derivation of one r
    en:'''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  + (en:'''Audubon Core:''' Entering this URL into a browser should only result in the icon (not in a webpage including the icon).)
  • ac:resourceCreationTechnique  + (en:'''Audubon Core:''' Examples: Encoding
    en:'''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  + (en:'''Audubon Core:''' Ideally, this would
    en:'''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  + (en:'''Audubon Core:''' If both description
    en:'''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  + (en:'''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  + (en:'''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  + (en:'''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  + (en:'''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  + (en:'''Audubon Core:''' Multiple values may be needed for movies or montages.)
  • ac:subjectOrientation  + (en:'''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  + (en:'''Audubon Core:''' No formal encoding scheme as yet exists.)
  • ac:providerID  + (en:'''Audubon Core:''' Only to be used if
    en:'''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  + (en:'''Audubon Core:''' Primarily intended
    en:'''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  + (en:'''Audubon Core:''' Provider is asserting they accept this review as competent.)
  • ac:IDofContainingCollection  + (en:'''Audubon Core:''' Repeatable: A media resource may be member of multiple collections)
  • ac:licensingException  + (en:'''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  + (en:'''Audubon Core:''' Reviewer Comments m
    en:'''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  + (en:'''Audubon Core:''' Some serializations
    en:'''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  + (en:'''Audubon Core:''' Supports to find a
    en:'''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.)