Ticket #1 (task)
Opened 6 years ago
Last modified 6 years ago
naming convention for CDL
Status: closed (fixed)
| Reported by: | cbc | Assigned to: | haines |
|---|---|---|---|
| Priority: | critical | Milestone: | 2006 SECOORA documentation contract |
| Component: | docs | Version: | 3.0 |
| Keywords: | CDL standards naming convention | Cc: | |
Decide on a naming convention for SEACOOS CDL.
e.g.: SEACOOS-CDL-v3.0 = SEACOOS-v2.0 + SEACOOS-QC-v1.0
Change History
07/11/06 11:40:35: Modified by cbc
- type changed from defect to task.
07/11/06 12:34:33: Modified by cbc
- component changed from qaqc to docs.
07/11/06 12:35:34: Modified by cbc
- keywords set to CDL standards naming convention.
07/11/06 12:41:29: Modified by cbc
- milestone set to 2006 SECOORA documentation contract.
07/11/06 14:39:19: Modified by cbc
- version set to 3.0.
07/11/06 16:40:06: Modified by cbc
- status changed from new to assigned.
- owner changed from somebody to cbc.
07/11/06 16:44:04: Modified by cbc
07/11/06 16:45:57: Modified by cbc
v2.0 is here
07/12/06 11:16:55: Modified by cbc
- status changed from assigned to new.
- owner changed from cbc to haines.
07/12/06 14:32:30: Modified by cbc
- status changed from new to closed.
- resolution set to fixed.
The string in NetCDF for the CF for this version of the CDL is:
SEACOOS-CDL-v3.0
A NetCDF with this string in it contains our first version of QAQC.

Checked version 2 into SVN. Created a tag called v2.0. That names the document. But what we want is to name the CDL itself so that when a NetCDF comes over the wire in this CDL, there is a convention for what metadata and naming recognizes the CDL version of the NetCDF file.