Meta-data about data creation, modification, etc. It may apply to objects but also parts of the object (e.g. assignments).
Mata-data only apply to successful operations. That is obvious for create, but it also applies to modify. For obvious reasons there are no metadata about delete. We keep no metadata about reading. That would be a huge performance hit.
These data are informational only. They should not be used for security purposes (use auditing subsystem for that). But presence of metadata simplifies system administration and may provide some basic information "at the glance" which may be later confirmed by the audit logs.
Meta-data are also supposed to be searchable. Therefore they may be used to quickly find "candidate" objects for a closer examination.
Name | Type | Multiplicity | Description |
---|---|---|---|
createTimestamp |
property dateTime |
[0,1] | The timestamp of data creation. |
creatorRef |
reference ObjectReferenceType |
[0,1] | Reference to the user that created the data. |
createApproverRef |
reference ObjectReferenceType |
[0,-1] | Reference to the user that approved the creation of the data (if there was such a user). |
createChannel |
property anyURI |
[0,1] | Channel in which the object was created. |
modifyTimestamp |
property dateTime |
[0,1] | The timestamp of last data modification. |
modifierRef |
reference ObjectReferenceType |
[0,1] | Reference to the user that modified the data. |
modifyApproverRef |
reference ObjectReferenceType |
[0,-1] | Reference to the user that approved the last modification of the data (if there was such a user). |
modifyChannel |
property anyURI |
[0,1] | Channel in which the object was last modified. |
Flags: RAM,runtime,oper,I
Multiplicity: [0,1]
Flags: RAM,oper
Multiplicity: [0,1]
Flags: RAM,oper
Multiplicity: [0,-1]
Flags: RAM,runtime,oper,I
Multiplicity: [0,1]
Flags: RAM,runtime,oper,I
Multiplicity: [0,1]
Flags: RAM,oper
Multiplicity: [0,1]
Flags: RAM,oper
Multiplicity: [0,-1]
Flags: RAM,runtime,oper,I
Multiplicity: [0,1]