Ontologies Classes Object Properties Data Properties Annotation Properties Individuals Datatypes Clouds

Annotation Property: note

Annotations (4)

Usage (53)

  • 'alpha-2 code' note "This part of IS0 3166 establishes an alphabetic 2-character (alpha-2) code which is generally recommended to represent country names and which is the basis for the codes laid down in IS0 3166-2 and IS0 3166-3 and for other international standards and recommendations. The alpha-2 code uses combinations, in upper case, of two letters of the 26-character Roman alphabet (ignoring diacritic signs) from the range AA to ZZ."(xsd:string
  • 'alpha-3 code' note "This part of IS0 3166 also provides an alphabetic 3-character (alpha-3) code, based on the alpha-2 code, and using combinations, in upper case, of three letters of the 26-character Roman alphabet (ignoring diacritic signs) from the range AAA to ZZZ, for use in cases where a specific need has been identified.

    Attention is drawn to the fact that other 3-letter codes for some country names are used in other contexts (e.g., US MARC standard)."
    (xsd:string
  • country note "Countries are named using the English short country names officially used by the ISO. The ISO uses country names from United Nations sources and hence, names such as Palestinian Territory, Occupied and Taiwan, Province of China reflect political status within the UN."(xsd:string
  • 'has territory' note "The isIndependent flag indicates whether or not a 'country' is in fact independent, but does not indicate whether or not it is self-governing. The UN FAO ontology distinguishes between these two cases, which can be added as an extension if required in a subsequent version of this specification."(xsd:string
  • 'alpha-2 code' note "In the ISO 639-1 language code, each language identifier is composed of two letters (lower case letters from the Latin alphabet, corresponding to characters 97 through 122 of the UTF-8 encoding), without diacritical marks or other encodings of any kind."(xsd:string
  • 'alpha-3 code' note "In the ISO 639-2 language code, each language identifier is composed of three letters (lower case letters from the Latin alphabet, corresponding to characters 97 through 122 of the UTF-8 encoding), without diacritical marks or other encodings of any kind."(xsd:string
  • 'alpha-3 code' note "Two code sets are provided in ISO 639-2, one for bibliographic applications and one for terminology applications. Some of these are considered collective language codes, referring to a family of languages, and there are a few special purpose codes for use in various applications. ISO 639-3 provides a single, three character code for each individual language or macrolanguage. Additional codes for language families and groups are specified in other parts of the standard."(xsd:string
  • 'ancient language' note "Ancient languages may have either individual or collective language codes. See section 4.1.5, ISO 639-2, for an explanation of the latter case."(xsd:string
  • 'artificial language' note "Artificial languages do not include reconstructed languages or computer programming languages."(xsd:string
  • 'collective language code' note "See section 4.1.1, ISO 639-2, for an explanation of the usage of such codes, and section 4.1.3 to gain understanding of the distinction between collective language and macrolanguage codes."(xsd:string
  • dialect note "Dialects are typically represented via the same language code as the code for the primary language, with a few exceptions for well-known dialects. See sections 4.1.3 and 4.1.4, ISO 639-2 for additional details on the treatment of dialects in the standard."(xsd:string
  • 'individual language' note "Identifiers in Parts 1, 2, and 3 of ISO 639 are assumed to denote distinct individual languages, unless the language name explicitly refers to a language group. See section 4.2 in ISO 639-4 for a detailed explanation of the definition of individual language in the context of the ISO 639 standard."(xsd:string
  • 'language group' note "See section 4.6 in ISO 639-4 for additional explanatory material for language groups."(xsd:string
  • 'language variation' note "Language variation may include change over time, space, cultural affiliation, etc."(xsd:string
  • macrolanguage note "See sections 4.1 and 4.3 of ISO 639-4 for an extensive description of macrolanguages and how they are different from language groups."(xsd:string
  • orthography note "The orthographic rules for a given language may include rules of spelling, hyphenation, capitalization, word breaks, emphasis, and punctuation. Languages that have multiple writing systems may have distinct orthographies and scripts."(xsd:string
  • script note "Use of multiple writing systems does not mean that multiple language identifiers are necessary for a language. ISO 639 language identifiers may be combined with script identifiers from ISO 15924 (e.g., BCP 47)."(xsd:string
  • transcription note "The resulting text is also referred to as a transcription."(xsd:string
  • transliteration note "The resulting text is also referred to as a transliteration."(xsd:string
  • 'base list' note "A base list is usually subject to further terminology work (3.6.1)."(xsd:string
  • 'concept harmonization' note "Concept harmonization is an integral part of standardization"(xsd:string
  • glossary note "In English common language usage, glossary can refer to a unilingual list of designations (3.4.1) and definitions (3.3.1) in a particular subject field (3.1.2)."(xsd:string
  • nomenclature note "Nomenclatures have been elaborated in various fields, such as biology, medicine, physics and chemistry"(xsd:string
  • 'term excerption' note "Term excerption involves identifying concepts (3.2.1) and their designations (3.4.1) and noting any relevant information about a concept such as definitions (3.3.1), contexts (3.6.10) and usage labels."(xsd:string
  • terminography note "Terminological data (3.8.1) may be presented in the form of term banks (3.7.4), glossaries (3.7.3), thesauri or other publications."(xsd:string
  • 'terminological data' note "The more common terminological data include entry term (3.8.4), definition (3.3.1), note (3.8.5), grammatical label (3.8.6), subject label (3.8.7), language identifier (3.8.8), country identifier (3.8.9) and source identifier (3.8.10)."(xsd:string
  • 'terminological entry' note "Adapted from ISO 1087-2:2000."(xsd:string
  • 'terminology planning' note "Terminology planning involves all aspects of terminology work (3.6.1) and has among other objectives the objective of achieving vocabulary control through such normative documents as thesauri and terminology standards."(xsd:string
  • vocabulary note "The vocabulary may be monolingual, bilingual or multilingual."(xsd:string
  • 'has term' note "The entry term usually corresponds to the preferred term (3.4.15)"(xsd:string
  • includes note "Note that something can be comprised of something(s) that may or may not be understood as separable parts, and thus is not defined as being explicitly transitive."(xsd:string
  • 'abbreviated form' note "The original long term is called the full or expanded form in ISO 704."(xsd:string
  • 'classification scheme' note "A classification scheme may be a taxonomy, a network, an ontology, or any other terminological system. The classification may also be just a list of controlled vocabulary of property words (or terms). The list might be taken from the 'leaf level' of a taxonomy."(xsd:string
  • classifier note "In ISO 1087, classifiers form categories of characteristics (3.2.4) that serve as the criterion of subdivision when establishing concept systems (3.2.11)."(xsd:string
  • concept note "Concepts are not necessarily bound to particular languages. They are, however, influenced by the social or cultural background which often leads to different categorizations."(xsd:string
  • 'concept field' note "Concept fields may be used as a starting point for establishing concept systems (3.2.11)."(xsd:string
  • designation note "In terminology work (3.6.1) three types of designations are distinguished: symbols, appellations (3.4.2) and terms (3.4.3)."(xsd:string
  • homonymy note "The designations (3.4.1) in the relation of homonymy are called homonyms."(xsd:string
  • 'individual concept' note "Individual concepts are usually represented by appellations."(xsd:short
  • mononymy note "The designations (3.4.1) in the relation of mononymy are called mononyms."(xsd:string
  • monosemy note "The designations (3.4.1) in the relation of monosemy are called monosemes."(xsd:string
  • object note "objects may be material (e.g. an engine, a sheet of paper, a diamond), immaterial (e.g. conversion ratio, a project plan) or imagined (e.g. a unicorn)."(xsd:string
  • polysemy note "The designations (3.4.1) in the relation of polysemy are called polysemes."(xsd:string
  • symbol note "Not explicitly defined in the standard but referenced in ISO 704, designations (terms, appellations or symbols) designate or represent a concept, or are attributed to a concept. From section 7.5, ISO 704, symbols are an important aid to international communication because their visual representation of concepts functions independently of any given language. They can communicate information directly under difficult circumstances (e.g., traffic signs).

    Iconic symbols should bear some visual resemblance to the concept they represent. Generally their meaning should be directly apparent without explanation. In some cases, however, the visual resemblance of the symbol is less pronounced or completely lost. Its meaning may be no longer directly recognizable and may be supported only by general agreement.

    Terms using the letters of the alphabet as iconic symbols to communicate the shape of the letter itself rather than its sound shall not be considered a symbol.

    Characters that replace words or parts of words, such as mathematical symbols or currency symbols, are considered symbols."
    (xsd:string
  • term note "A term may contain symbols and can have variants, e.g. different forms of spelling."(xsd:string
  • 'consists of' note "Note that something can consist of something(s) else that may or may not be understood as separable parts, and thus is not defined as being explicitly transitive."(xsd:string
  • 'specification version status' SubPropertyOf note
  • 'change note' SubPropertyOf note
  • definition SubPropertyOf note
  • 'editorial note' SubPropertyOf note
  • example SubPropertyOf note
  • 'history note' SubPropertyOf note
  • 'scope note' SubPropertyOf note