<dd:km kc:km3purpose>
<dd:km kc:km3ref>
5.0 Reference Documents:
10.1 timestamp: this is a yy/mm/dd HH:mm timestamp of the log entry
- this is the same in both the long and short formats for a log entry
10.2 work order: this is the work order number (<org><yynna>)
- the long format is preceded by the work order keycode "wo:"
10.3 cdid: this is the cdid id for the deliverable.
- the long format is preceded by the keycode "cdid:"
10.4 keycode: this is the data dictionary & keycode for the entry
- the keycode itself should always include the data dictionary code.
10.5 data value: this is the actual data entry for the value associated with the keycode.
- in the examples the entire cv or a link to the cv file should be included (as defined by the key code definition page for hr:hr2)
eg1 - long format: 10/05/10 08:59 wo:netdiff11a cdid:hr2 dd:hr kc:hr2
(need cv's.)
eg2 - short format: 10/05/10 08:59 netdiff11a, hr2, hr:hr2
(need cv's)
<dd:km kc:km3type>
11.0 Metadata (Data Typing)
<dd:km kc:policy>
12.0 File Handling Policy
12.1 Backup
Backup policies must be stated for time of retention
12.2 Privacy
PIPEDA (Canada), Sorbanes Oxley (USA) and equivalent privacy handling methods must be specified.
12.3 Security
Appendix:
How to create a Data Dictionary for web publication: