1 / 9

PDS 4 Information Model Issues

PDS 4 Information Model Issues. PDS Management Council 30 November 2011 Anne Raugh. 1. Information Model – Areas of Comment. Content Missing Details Outstanding Design Issues (Still) Contentious Design Decisions Model-to-Schema Translation Issues Additional Requests. IM - Content.

hastin
Télécharger la présentation

PDS 4 Information Model Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PDS 4 Information Model Issues PDS Management Council 30 November 2011 Anne Raugh 1

  2. Information Model – Areas of Comment • Content • Missing Details • Outstanding Design Issues • (Still) Contentious Design Decisions • Model-to-Schema Translation Issues • Additional Requests

  3. IM - Content • Preamble classes (Observation_Area, Cross_Reference, etc.) • Variations in requirements for spacecraft data and other data in the preamble • Attribute definitions • lexical definition • required vs. optional • variations with context • figurative constants not yet accommodated • Over- and under-defined classes • Nomenclature, including things like: • Standard values for, e.g., association types • Inconsistent repetition of qualifiers in names • Functionally accurate naming: “Description” vs “comment”, e.g. • Distinctions without differences • enumerations with multiple options that are equivalent • complex type extensions that neither add nor restrict 3

  4. IM – Missing Details • Instrument type • Product characterizations (wavelength regime, result type, etc.) • Target naming and classifications • Units of attributes 4

  5. IM – Outstanding Design Issues • Local Dictionaries, node interaction, and formal modeling • Inheritance of associations by products of collections and collections of bundles • Parseable byte streams and observational data • Encoded byte streams and observational data • Units for searching • ADS Interface • NSSDC Interface 5

  6. IM – (Still) Contentious Design Issues • Bit fields • PDS “root” tag • Recursive structure in “Grouped” tables • Too many data structure/format variations 6

  7. IM – Model-to-Schema Translation Issues • Order of attributes in classes • Wrapping classes (Table_Record, e.g.) • Data type patterns • Unenforceable uniqueness constraints (title, e.g.) • Inappropriate upper limits • Lack of expected constraints (Product_Array_2D_Image is not required to contain an Array_2D_Image, e.g.) 7

  8. IM – Additional Requests • User-friendly presentation of the Information Model 8

  9. Backup 9

More Related