(SDD schema version: SDD 0.9.030, 1. Dec. 2003)
TDWG working group: Structure of Descriptive Data (SDD)
See the "Overview of available documentation" for further information.
The character '@' is used inside schema annotations to mark problem or places that need further discussion. The table is sorted by order of occurrence in the schema.
| Annotation | Parent | |
|---|---|---|
| 1. | This provides a combined key for states (local or generic references, compare CharacterStateKey) and statistical measure references. @@ Further discussion on the utility of doing this may be required. It is intended to simplify implementations that treat all state or measure objects within the character as a single supertype. | key = CombinedCharStateOrMeasureKey |
| 2. | @@ To be discussed. The idea is that a project may point to a web resource that informs about details about the history of the data (previous versions or a detailed log of changes). | ProjectDefinitionSectionType/ HistoryWebAddress/ |
| 3. | @@This whole sequence is not functional, just a bunch of ideas for discussion! @@ The extra Wording element is used to clarify that this is for natural language wordings (similar to Wording in Label types). Currently the only other Language rule is the dir attribute, but more language rules may follow. | ProjectDefinitionSectionType/ __LanguageRules/ LanguageRule/ Wording/ |
| 4. | @@This whole sequence is not functional, just a bunch of ideas for discussion! @@ | ProjectDefinitionSectionType/ __LanguageRules/ LanguageRule/ Wording/ |
| 5. | @@ Should for each of Or, And, etc. an entire delimiter group be defined? @@ Should only Or be defined and and etc. left to the override mechanism available anyways in the concept trees? | ProjectDefinitionSectionType/ __LanguageRules/ LanguageRule/ Wording/ OrDelimiters/ |
| 6. | @@ unclear whether used. DeltaAccess defines on the character level whether states are combined with or, and, to, or with. This has not yet been worked out for SDD! Instead originally SDD attempts to succeed just with delimiters. Combining delimiter rules with conditionally different operators is a problem, however!@@ | ProjectDefinitionSectionType/ __LanguageRules/ LanguageRule/ Wording/ And/ |
| 7. | @@ unclear whether this would be used | ProjectDefinitionSectionType/ __LanguageRules/ LanguageRule/ Wording/ With/ |
| 8. | The Glossary entry for a single concept (object, method, property, state, etc.), which may be expressed in multiple audience-specific representations. [ATTR: key] @@unusually, in Glossary authors and revision status are given for EACH translation. This may be appropriate given complex material is presented in each Representation, but it is also inconsistent with the rest of the SDD schema. Please comment whether to move RevisionData here, and if so what to call the collection of Representation elements: Representations?? @@ | TerminologySectionType/ Glossary/ GlossaryEntry/ |
| 9. | @@ Necessary? To be discussed! See short doc. on SDD site. | TerminologySectionType/ Modifiers/ __Approximation/ |
| 10. | @@ Should we add this?@@ A list of additional character that are defined as templates for new characters, to provide combinations of statistical measures, modifiers, and other settings. Or should character have a boolean attribute whether it is a template or not? | TerminologySectionType/ __TemplateCharacters/ |
| 11. | @@DISCUSS: should concept tree hierarchies be recursively definable, as long as the resulting tree is acyclical?@@ [ATTR: key] | TerminologySectionType/ ConceptTrees/ ConceptTree/ |
| 12. | @@@ This is just a preliminary sketch that should probably be synchronized with TDWG ABCD! [ATTR: key] | ResourcesSectionType/ Agents/ Agent/ |
| 13. | - cardinal data scale = integer (incl. negative values, although these are extremely rare in descriptive biological data; DELTA: type 'IN') - interval = real numeric = floating point values (DELTA: type 'RN') - nominal = unordered categorical states (DELTA: type 'UM') - ordinal-discrete = ordered categorical states (DELTA: type 'OM') @@ Should we make a distinction between ordinal-discrete and ordinal-interval [= ordered categorical states (DELTA: type 'OM'). Like ordinal-discrete but states can intergrade. Example: no / few / many hairs, ovate / ellipsoid. However, also intergrade without order: - Color @@ introduce a separate datatype for color? Exact value are not very practical, but polygons in color space would be very usefull! | CharacterDefType/ Type/ |
| 14. | @@ Methods should ideally be defined in Glossary entries. Or should this become free-form text? [ATTR: ref] | CharacterDefType/ Numerical/ __MeasurementMethod/ |
| 15. | Free-form information about accuracy of measurement. @@ free-form is language and audience dependent and can not be included in analysis. Currently this is rather a specific InternalNote. Any way to improve this? Ideally a numeric value for a confidence interval of measurements would be desirable! | CharacterDefType/ Numerical/ __MeasurementAccuracy/ |
| 16. | MinimumExpertiseLevel: the designer of the subset expects the user to have a certain minimum expertise level. @@@ Needs discussion! @@@ | ConceptTreeDefType/ __MinimumExpertiseLevel/ |
| 17. | @@ Was present as attribute in previous version and overlooked, needs discussion! On states or on set? If present should be made required! Enumeration: Local/ Generic/ Special/ Computed | CharacterStateDefType/ __Type/ |
| 18. | @@ This or a format string ?@@ | CharacterStatMeasureDefType/ __OrThisInstead/ __LeadingZero/ |
| 19. | @@ This or a format string ?@@ | CharacterStatMeasureDefType/ __OrThisInstead/ __DecimalSeparator/ |
| 20. | @@ This or a format string ?@@ Note: How can we handle measures as well as values from repeated observations with the same mechanism? | CharacterStatMeasureDefType/ __OrThisInstead/ __DecimalPlaces/ |
| 21. | @@ Both proposals need elaboration and discussion! | CodingStatusDefType/ Generalization/ |
| 22. | For StatisticalMeasures. Can not be derived from StateDefBaseType by extension, since the nat. language wording requires TextBefore and TextAfter the value instead of only a single Text. @@ Does it makes sense to derive this by restriction as it is currently done? @@ | StatisticalMeasureDefType/ |
| 23. | Classification of statistical measures into predefined categories like CentralValue, VarianceMeasure, Min, Max, Lower/UpperRangeLimit, etc. @@ add enumeration to finalize schema! | StatisticalMeasureDefType/ Generalization/ ReportingClass/ |
| 24. | Classification of statistical measures according to method, e. g. ConfInterval, Percentile @@ add enumeration to finalize schema! | StatisticalMeasureDefType/ Generalization/ Method/ |
| 25. | Refers to arbitrary key nodes within the current or other keys, to allow building reticulations into the key. @@ This may need further discussion and testing! Allowing to jump into other keys requires the leads (=node) key to be unique across all keys, not only within a key!@@ [ATTR: ref] | DesignedKeyNodeType/ KeyNode/ |
| 26. | @@Should we define additional scopes for the description, e. g. host plants for pathogens, or should be simply provide a free-form text element like this? | DescriptionBaseType/ __OtherScope/ |
| 27. | Contains multiple resources (e. g. images). @@ In previous versions, a description may consist of resources alone, this is not possible after Paris - may need discussions! @@ @@ Also, it is no longer clear whether the images are also created by Creators, or who has the IPR to them! @@ | DescriptionBaseType/ MediaResources/ |
| 28. | Abstract base type for character data in coded descriptions. It primarily contains a reference to a Character definition key, plus a set of references to character state definition keys. @@This base type may be redundant. Is Sequence really relevant both in coded synthetical data as well as in raw data?@@ | CharacterData_BaseType/ |
| 29. | If a new description is created as a child of the current description (in the class hierarchy or through an object identification), the current state will be inserted. This may be a normal state or a coding status. The inserting mechanism is available in addition to the dataless inheritance mechanism in the class hierarchy. @@ Open issue: Name for this element needs to be decided@@ | CharacterStateData_BaseType/ IsTemplateForChildDescription/ |
| 30. | @@ To be discussed. Is a given state a cached result of an inference or deduction process in the class hierarchy, a calculated character, or is it an original statement? This could also be defined as an attribute, currently as element to avoid being overlooked! | CharacterStateData_BaseType/ __Origin/ |
| 31. | Similar to CharacterStateDataType, this one is intended for statistical measures. The ref attribute points to a statistical measure definition inside a character definition. @@Note: the necessity of Note inside statistical measures needs to be discussed. On measures like min, max, mean this will be difficult to support during natural language reporting! However, on measures like sample size they may be valuable. | CharacterMeasureDataType/ |
| 32. | Similar to CharacterStateDataType, this one is intended for CodingStatus references. The ref attribute points to the key of Terminology/CodingStatusValues/CodingStatus @@Is it ok to inherit the ref attribute from the state base type, even though it points elsewhere? | CharacterCodingStatusDataType/ |
| 33. | Human readable representation; this may be the only data item if no machine readable ID exists. Example in the case of a publication resource: "Smith 1998. Flora of Erehwon, Fingers Publishers." If an external ID exists, this is considered cached information and required to be present. @@ Should this be multilingual? Difficult if external source does not inform about language! @@ Should this be called Label instead? | ResourceConnectorBaseType/ FreeFormDescription/ |
| 34. | @@ For biological taxonomic names: order, family, species Needs discussion: should this be constrained vocabulary, or in any language? | ClassNameConnectorType/ RankLevel/ |
| 35. | Type of medium @ To be discussed! @ | MediaResourceConnectorType/ Type/ |
| 36. | An optional caption for a resource, esp. if it will be presented embedded in another document. Captions can be provided for multiple audiences. @@ Issue: captions, even in multiple languages, may be obtained from the service provider. Even then it may be desirable to override them! Do we need two collections: InheritedCaption and CaptionOverride? This seems to be awkward whenever there is no ServiceProvider! Also, FreeFormDescription can contain a "title" only in a single language! @@ | MediaResourceConnectorType/ Caption/ |
| 37. | Defines an element with a ref attribute pointing to a Specimen defined in Resources @GH@: Discuss whether to add a separate element for collection abbreviation (cached information form provider or from | DescribedObjectRefType/ |
| 38. | In addition to authors/editors, several people may have translated audience- specific texts. @@Request for discussion: Translators are currently not listed on individual Representation elements. Only a general general statement about all translations together can be made. Should this be changed? Also: should one Representation be marked as 'Original/SourceForTranslation'? Will we have something like a 'normative' version? @@ | CreatorsType/ Translators/ |
| 39. | In addition to authors/editors, several people may have translated audience- specific texts. @@Request for discussion: These are currently not listed in the Representation elements, but could a single one could be easily (however, not several!). Also: should one Representation be marked as Original/SourceForTranslation/Etc.? @@ | __OptionalCreatorsType/ Translators/ |
| 40. | [Unused!] Colors defined as HSV (hue-saturation-value (? value correct?)). @@ Unclear whether we should offer this@@ | simpleType = __ColorHSV |
| 41. | @@ needs discussion:@@ ordinal-discrete = ordered categorical states (DELTA: type 'OM') | simpleType = CharacterTypeEnumenumeration |
| 42. | @@ needs discussion:@@ ordinal-interval = ordered categorical states (DELTA: type 'OM'). Like ordinal-discrete but states can intergrade. Example: colors. | simpleType = CharacterTypeEnumenumeration |
| 43. | Proposal to add color as a special color type, to provide special support for RGB/HSV polygons of color values, and to support special interaction. @@ The special data structures required for this are not yet supported in other areas of the schema and need further discussion! @@ | simpleType = CharacterTypeEnumenumeration |
| 44. | Categorizing characters into basic property types (e. g. color, 2-dim. shape, 3-dim. shape, surface texture, taste, smell, behavior, physiology, measurements, etc.) greatly improves the analysis and management of larger character sets and is therefore recommended. [@ Note: Only a single concept tree should have this hierarchy type. (not enforced in schema, how can it be enforced? Other types occur multiple, i. e. one cannot make a UNIQUE statement on attribute! @] | simpleType = ConceptTreeTypeEnumenumeration |
| 45. | @@ To be discussed, see Paris 2003 minutes. Information about whether the range is a rough estimate about frequency or probability values that has been guessed after coding occurred, or whether it is rather a normative definition that was known at the time of coding. | ProbabilityRangeType/ attribute = __IsEstimate |
| 46. | Verbatim name as it appears in citation. @@ Do we need this? @@ | CitationType/ __TaxonNameInSource/ |
| 47. | @@ Probably this does not work yet, since the type extension itself is not a choice but a sequence!!! | __FormattedInlineTextType/ |
| 48. | @@ check later whether still necessary! | |
| 49. | @@ To be discussed: Do we need both adjacent and connected? Example: The thumb is adjacent to the index finger, connected to the palm of the hand, and part of the hand | GlossaryEntryRepresentationType/ AdjacentTo/ |
(Generated on 3. Dec. 2003 by DiversitySchemaTools Version 0.2. Copyright (c) G. Hagedorn 2003.)