Property:skos:note
From TDWG Terms Wiki
Label | note |
---|---|
Has type |
Text Type “Text”
See also types defined by Semantic MediaWiki and Special:Properties for all properties. |
Imported from | http://www.w3.org/2004/02/skos/core#note (Simple Knowledge Organization System (SKOS)) See also import page MediaWiki:Smw_import_skos |
Editor tools …
The SMW-import-page (MediaWiki:Smw import skos) defines a name space prefix “skos” and the following pages (=concepts or concept collections “”):
altLabel │ broader │ broaderTransitive │ broadMatch │ changeNote │ closeMatch │ Collection │ Concept │ ConceptScheme │ definition │ editorialNote │ exactMatch │ example │ hasTopConcept │ hiddenLabel │ historyNote │ inScheme │ mappingRelation │ member │ memberList │ narrower │ narrowerTransitive │ narrowMatch │ notation │ note │ OrderedCollection │ prefLabel │ related │ relatedMatch │ scopeNote │ semanticRelation │ topConceptOf
A concept page is supposed to be in the article name space holding more detailed definitions, notes, relations etc. than the basic settings here on the property page.
The SMW-import-page (MediaWiki:Smw import skos) defines a name space prefix “skos” and the following pages (=concepts or concept collections “”):
altLabel │ broader │ broaderTransitive │ broadMatch │ changeNote │ closeMatch │ Collection │ Concept │ ConceptScheme │ definition │ editorialNote │ exactMatch │ example │ hasTopConcept │ hiddenLabel │ historyNote │ inScheme │ mappingRelation │ member │ memberList │ narrower │ narrowerTransitive │ narrowMatch │ notation │ note │ OrderedCollection │ prefLabel │ related │ relatedMatch │ scopeNote │ semanticRelation │ topConceptOf
Warning: improper values detected. See also property: Has improper value for.
Improper values detected, please do check:- Audubon Core Geography Vocabulary
- Iptc4xmpExt:CVterm
- Iptc4xmpExt:CountryName
- ac:digitizationDate
- ac:metadataLanguage
- ac:subtype
- ac:taxonCoverage
- dcterms:type
- ft:architecture
- ft:arrangement
- ft:behavior
- ft:character
- ft:coating
- ft:coloration
- ft:condition
- ft:course
- ft:dehiscence
- ft:density
- ft:depth
- ft:derivation
- ft:development
- ft:distribution
- ft:duration
- ft:fixation
- ft:fragility
- ft:function
- ft:fusion
- ft:germination
- ft:growth form
- ft:growth order
- ft:habitat
- ft:height
- ft:length
- ft:life cycle
- ft:location
- ft:maturation
- ft:nutrition
- ft:odor
- ft:orientation
- ft:ploidy
- ft:position
- ft:postion relational
- ft:prominence
- ft:pubescence
- ft:quantity
- ft:reflectance
- ft:relief
- ft:reproduction
- ft:season
- ft:shape
- ... further results
Subproperties
This property has the following 5 subproperties:
S
s
Pages using the property "skos:note"
Showing 25 pages using this property.
(previous 25) (next 25)A | |
---|---|
ABCD 2 + | A comprehensive mapping table of all ABCD 2 XPaths to the new short names can be found at [[ABCD 2 XPath to Short Name Mapping]] + |
ABCD EFG + | A comprehensive mapping table of all ABCD EFG XPaths to the new short names can be found at [[ABCD EFG XPath to Short Name Mapping]] + |
Audubon Core Development + | An Audubon Core (AC) record is a description, using the Audubon Core vocabularies, of a multimedia resource. Two kinds of terms are specified by this document: record-level terms and access-level terms. Terms under the Record-level Terms section apply to the whole Audubon Core record regardless of the record type. Almost all terms are record-level terms. One such term, hasServiceAccessPoint plays a special role in helping to retrieve the resource that the record describes. Its value is an identifier of a set of more metadata about services that may provide web or other access to a file containing the media. A multimedia resource may describe more than one such service, each of which is described by values of one or more access-level terms, telling such things as a web address at which the resource from which a digital representation of the resource can be retrieved, the size of such a retrieved object, etc. This document is not a normative document, but a functional document automatically listing the up-to date (and perhaps with respect to the normative document slightly corrected as well as translated) term definitions. The static, normative versions are linked below. <b>See also:</b> * [[Audubon Core]] * <b>[[Audubon Core Term List]]</b> (the normative version as of 2013, not reflecting the ongoing improvements added since then) * [[Audubon Core dynamic term list]] (the equivalent to the static [[Audubon Core Term List]], but reflecting dynamically all changes that occurred in the individual concept pages) * [[Audubon Core FAQ]] + |
B | |
Biorelations + | The RO URIs do not resolve to proper definitions. For comparing biorel definition with original definitions, http://www.ontobee.org/browser/index.php?o=RO is useful, using the label rather than then URI. At the time of this writing, several terms could not be compared, the definitions were not shown and the status indicated as “pending final vetting”. + |
D | |
Darwin Core GeologicalContext + | For discussion see http://code.google.com/p/darwincore/wiki/GeologicalContext + |
Darwin Core Location + | For discussion see http://code.google.com/p/darwincore/wiki/Location + |
Darwin Core Measurement or Fact + | For discussion see http://code.google.com/p/darwincore/wiki/MeasurementOrFact + |
Darwin Core Occurrence + | For discussion see http://code.google.com/p/darwincore/wiki/Occurrence + |
Darwin Core Organism + | Instances of the Organism class are intended to facilitate linking of one or more Identification instances to one or more Occurrence instances. Therefore, things that are typically assigned scientific names (such as viruses, hybrids, and lichens) and aggregates whose occurrences are typically recorded (such as packs, clones, and colonies) are included in the scope of this class. + |
Darwin Core Resource Relationship + | Resources can be thought of as identifiable records and may include, but need not be limited to Occurrences, Locations, Events, Identifications, or Taxon records. For discussion see http://code.google.com/p/darwincore/wiki/ResourceRelationship + |
Darwin Core Taxon + | For discussion see http://code.google.com/p/darwincore/wiki/Taxon + |
E | |
Extensible Metadata Platform (XMP) + | Visit [http://www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/XMPSpecificationPart1.pdf XMP Specification Part 1] for further documentation. + |
G | |
GGBN Loan Vocabulary + | From the perspective of the owner of materials, loans can be characterized as incoming (also can be called “borrows”) or outgoing. The party providing access is thus the lender, and the party receiving access is the borrower. Lenders send outgoing loans, borrowers receive incoming loans. + |
I | |
IPTC Extension schema (1.1) specifications + | Although the recommended namespace URI is given the complete URI does not resolve to a page. + |
IPTC Photo Metadata + | Visit [http://www.iptc.org/std/photometadata/specification/IPTC-PhotoMetadata-201007_1.pdf IPTC Standard Photo Metadata (July 2010)] for further documentation. + |
Iptc4xmpExt:City + | en:<b>Audubon Core:</b> Optionally, the name of a city or place commonly found in gazetteers (such as a mountain or national park) in which the subjects (e. g., species, habitats, or events) were located. 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. + |
Iptc4xmpExt:CountryCode + | en:<b>Audubon Core:</b> The geographic location of the specific entity or entities documented by the media item, expressed through a constrained vocabulary of countries using 2-letter ISO country code (e. g. "it, si"). Accepted exceptions to be used instead of ISO codes are: "Global", "Marine", "Europe", “N-America”, “C-America”, “S-America”, "Africa", “Asia”, “Oceania”, ATA = "Antarctica", XEU = "European Union", XAR = "Arctic", "ZZZ" = "Unknown country" (3 letter abbreviations from IPTC codes). This list may be extended as necessary. 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. + |
Iptc4xmpExt:LocationCreated + | en:<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. + |
Iptc4xmpExt:LocationShown + | en:<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. + |
Iptc4xmpExt:ProvinceState + | en:<b>Audubon Core:</b> Optionally, the geographic unit immediately below the country level (individual states in federal countries, provinces, or other administrative units) in which the subject of the media resource (e. g., species, habitats, or events) were located (if such information is available in separate fields). 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. + |
Iptc4xmpExt:Sublocation + | en:<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. + |
Iptc4xmpExt:WorldRegion + | en:<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. + |
N | |
Natural Collections Description + | NCD creates multiple namespaces, not a single one, it thus has not single Preferred namespace prefix/uri. + |
P | |
Photoshop Schema + | The resulting URIs do not resolve to a definition page although they are defined by the Photoshop Schema itself. + |
R | |
Resource Description Framework + | RDF does not assume that a namespace URI identifies a retrievable Web resource, see [http://www.w3.org/TR/rdf-primer/ RDF primer]. + |