Property:terms-internal:enNote
From TDWG Terms Wiki
| Has type |
Text Type “Text”
See also types defined by Semantic MediaWiki and Special:Properties for all properties. |
|---|---|
| Use SMW-import? | The page name with the colon (terms-internal:) suggests that this page is meant to be an SMW import defined on MediaWiki:Smw_import_terms-internal |
Editor tools … 
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.
Warning: improper values detected. See also property: Has improper value for.
Improper values detected, please do check:- Iptc4xmpExt:CVterm
- Iptc4xmpExt:CountryName
- ac:digitizationDate
- ac:metadataLanguage
- ac:subtype
- ac:taxonCoverage
- dcterms:type
- xmpRights:Owner
Pages using the property "terms-internal:enNote"
Showing 25 pages using this property.
(previous 25) (next 25)I | |
|---|---|
| Iptc4xmpExt:City + | <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 + | <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 + | <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 + | <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 + | <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 + | <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 + | <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. + |
a | |
| abcd2:Age + | Note that counts for different age classes can be provided in the Unit's {{{MeasurementsOrFacts}}} section. + |
| abcd2:Annotation + | Note that for annotation labels captured from the specimen there is the SpecimenUnit/Marks structure (AbcdConcept0561). + |
| abcd2:BotanicalGardenUnit-DonorCategory + | Note that the ITF-Donor field is found under {{{AccessionSource}}} and the Donor's Accession Number is found in the {{{PreviousUnitID}}} (the first record in the {{{UnitHistory}}}). + |
| abcd2:CultureCollectionUnit-Aerobicity + | $$Walter$$ What descriptions go here? There is nothing in the schema for this element. + |
| abcd2:CultureCollectionUnit-Applications + | $$Walter$$ What comments go here? + |
| abcd2:CultureCollectionUnit-Hazard + | $$Walter$$ What comments go here? (none in schema) + |
| abcd2:CultureCollectionUnit-Strain + | Note that if the strain name is also the unique identifier of the unit in the collection database, this name should also be entered under Unit/UnitID (AbcdConcept0140). + |
| abcd2:DataSet-DateModified + | Note that it may well be that the result of the query, i.e. the document containing this datum, does not contain the parts of the souce that have actually been changed. + |
| abcd2:EAnnotations + | >Note that for annotation labels captured from the specimen there is the {{{SpecimenUnit/Marks}}} structure (AbcdConcept0561). + |
| abcd2:Gathering-Altitude + | Note the difference from the {{{Height}}} and {{{Depth}}} elements, which are measured relative to a local surface. + |
| abcd2:Gathering-Altitude-LowerValue + | $$Walter$$ The comment about the attribute for ValueDataTpe - is that still relevant? + |
| abcd2:Gathering-Altitude-Parameter + | Is the generic description for parameter I found in the schema ok for this element? Should I take out the examples like width, circumference etc.?<br/><br/>The parameter element makes sense only where the measurmentOrFact type is used to describe "open" measurements, where the users decide what it is what is measured. Altitude etc. are a special case, the parameter is actually always altitude. A solution to this would be to exclude this from the MoF and put it into an extension, only used when general measurements are asked for. I added this to the Schema discussion page. For the time being, the above (English?) can serve as a template for similar cases (depth etc.). + |
| abcd2:Gathering-Altitude-TitleCitation + | Need to decide on whether a particular standard for citations should be adopted - such as the Council of Biology Editors 6th edition with the NLM Internet extensions?? + |
| abcd2:Gathering-ChronostratigraphicTerm-Domain + | $$Walter$$ Is this phrasing correct - "chronostratigraphic term for the gathering site"? + |
| 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] + |
| abcd2:Gathering-Country-ISO3166Code + | $$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. + |
| abcd2:Gathering-DateTime-TimeOfDayBegin + | Note that time can also be expressed in the {{{ISODateTimeElement}}}. + |
| abcd2:Gathering-GridCellCode + | 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) + |
