SCR 3-1117 – PDS Engineering

SCR 3-1117: Bad formation rule in *_DATE keywords (Was “Bad formation rule in MISSION_START/STOP_DATE description”)

Priority: medium

Problem Summary

The MISSION_START/STOP_DATE keywords have a general data type of DATE, which implies a formation like YYYY-MM-DD – specifically, without a time component. The DESCRIPTIONs for these keywords, however, both contain this line: Formation rule: YYYY-MM-DDThh:mm:ss[.fff]

Working Group

A. Raugh (lead) S. Hughes, E. Rye

Originator: Anne Raugh

Standards Change Request

Version	Date	Author(s)	Format	Note
1	2007-05-07	A. Raugh	DOC PDF
2	2008-05-30	E. Rye	DOC PDF

Discussion

Discussion Blog
Telecons: 2007-05-30 (WAV), 2007-07-25 (WAV), 2008-06-04 (HTML)

Supplementary Material

Status

Status	Date	Task	Responsible Party	Response
SUBMITTED	2007-05-07	Submit issue.	ORIG	Issue submitted through online interface 05/07/07.
		Form working group.	EN-SEORIG	Working group consists of A. Raugh.
Update status to IN_PROGRESS.		EN-SE	Status updated to IN_PROGRESS by E. Rye on 05/07/07.
IN_PROGRESS	2007-05-07	Update queue to Disposition.	EN-SE	Queue updated to Disposition by E. Rye on 05/07/07.
		Submit draft SCR.	WG	Draft SCR submitted to E. Rye and R. Joyner by A. Raugh on 05/07/07.
Update status to DRAFT.		EN-SE	Status updated to DRAFT by E. Rye on 05/07/07.
DRAFT	2007-05-07	Distribute SCR to tech group.	EN-SE	E. Rye sent email to S. Hughes on 05/21/07 asking him if he would be on working group and would verify impact section of SCR.
				S. Hughes sent email to E. Rye on 05/22/07 agreeing to work on SCR.
				E. Rye added S. Hughes to working group on 05/22/07.
				E. Rye sent email to A. Raugh on 05/22/07 informing her of Steve’s addition to working group and asking about clarification of FORMATION_RULE attribute in SCR.

Votes

Node	Representative	Version 1
GEO^a	Susie Slavney	yes, implementation, if Dick’s
RS^b	Dick Simpson	no

• End the description after the word “mission”, and
• Add YYYY-DDD to the formation rule.
I have a mild curiosity about how formation rules are implemented, but not enough to delay this while we talk about it.

RS votes “no” pending resolution of a couple of questions (sorry to miss discussion yesterday; I had a competing telecon and thought this SCR would be straightforward).
• YYYY-DDD is a legal DATE; so the proposed “solution” is incomplete.
• DESCRIPTION will continue to refer to “UTC format”, which seems irrelevant, at best, once the hh:mm:ss[.fff] is gone.
Suggest that DESCRIPTION be edited to remove everything after “…of a mission.”

In a web vote ending 06/13/08, the Tech Group voted 6-2-1 (yes-no-absent) to approve version 2 of this SCR.

Node	Representative	Version 2
EN	Steve Hughes	yes
GEO	Susie Slavney	yes
IMG	Patty Garcia	yes
NAIF	Boris Semenov	yes
PPI^a	Todd King	no
RINGS	Mitch Gordon	yes
RS	Dick Simpson	yes
SBN^b	Anne Raugh	no

While this is a worthwhile how change does it impact existing descriptions? We’ve always had the concern that “valid” labels will now become “invalid” with changes like this. It’s not addressed in the SCR.

SBN votes NO on this SCR3-1117 because we should not be wasting any more time on PDS3.

In a web vote ending 06/13/08, the Tech Group voted 6-1-2 (no MC-MC-absent) that an MC vote was unwarranted for this SCR. It’s status has been upgraded to TG_APPROVED.

Node	Representative	Version 2
EN	Steve Hughes	MC vote unwarranted
GEO	Susie Slavney	MC vote unwarranted
IMG	Patty Garcia	MC vote unwarranted
NAIF	Boris Semenov	MC vote unwarranted
PPI	Todd King	submit to MC for vote
RINGS	Mitch Gordon	MC vote unwarranted
RS	Dick Simpson	MC vote unwarranted