This wiki has undergone a migration to Confluence found Here
Difference between revisions of "OO CRLOI-011 - ORC-9 (Date/Time of Transaction )"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
== Recommendation == | == Recommendation == | ||
| − | Add "For unknown transaction date/time use | + | Add "For unknown transaction date/time use '0000'." to comment or change data type to TS_5 and remove TS-4 from IG since this is the only place it is used |
== Rationale == | == Rationale == | ||
Revision as of 19:16, 23 January 2014
Return to OO Change Requests page.
| Submitted by: Eric Haas | Revision date: Jan 23 2014 |
| Submitted date: Jan 23 2014 | Change request ID: OO CRLOI-011 |
| Standard/IG: Implementation Guide | Artifact ID, Name: ORC-9 (Date/Time of Transaction ) |
Issue
Using the TS_4 datatype in ORC-9 (Date/Time of Transaction ) but no guidance on when to use "0000".
Would the date and time of the event that initiated the current transaction ever be unknown by the orderer?
Recommendation
Add "For unknown transaction date/time use '0000'." to comment or change data type to TS_5 and remove TS-4 from IG since this is the only place it is used
Rationale
Verify and clarify usage of TS_4 datatype in ORC-9
