Difference: FreeFormat (1 vs. 2)

Revision 22011-02-28 - MireilleLouys

 
META TOPICPARENT name="ObsDMCoreComponents"
+ Free Format data model fields and extensibility mechanism

When a data provider cannot use the proposed value fields (for instance in data product type), how can he/she still provide some information to characterise his/her data sets?

  1. How could we allow for extensibility?
Changed:
<
<
If we need to consider new science data product , not yet defined in the Obs/tap fields , how should we proceed?
>
>
If we need to consider new kinds of science data product , not yet defined in the Obs/tap fields , how should we proceed?
 
  1. Description of a data set - obs_title

In Obs/Tap , it is not a mandatory field, it could become important in future releases if its usage is well-defined. At the moment it is just free-format, and that could be an issue.


<--  
-->

Revision 12011-02-28 - MireilleLouys

 
META TOPICPARENT name="ObsDMCoreComponents"
+ Free Format data model fields and extensibility mechanism

When a data provider cannot use the proposed value fields (for instance in data product type), how can he/she still provide some information to characterise his/her data sets?

  1. How could we allow for extensibility? If we need to consider new science data product , not yet defined in the Obs/tap fields , how should we proceed?
  2. Description of a data set - obs_title

In Obs/Tap , it is not a mandatory field, it could become important in future releases if its usage is well-defined. At the moment it is just free-format, and that could be an issue.


<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback