Legacy Issue Number: 17316
Source: KDM Analytics ( Nikolai Mansourov)
Currently the Evidence metamodel has a general class Exhibit, and one concrete class Document. However the feedback from Regulatory Compliance community is that there should be an explicit element to represent electronic records of compliance.
Suggested resolution is to add Record element as a concrete subclass of Exhibit. Resolutions in Ballot 5 are addressing the issue of moving the DocumentProperties up the inheritance chain so that these Properties are available for Records.
This is a minor semantic enhancement that will allow better differentiation between various exhibits, and will allow management of electronic records for compliance.
Reported: SACM 1.0b1 — Thu, 19 Apr 2012 04:00 GMT
Disposition: Resolved — SACM 1.0b2
Add section Record to chapter 10 as follows:
Record element represents Exhibits that are explicit records of compliance, for example
log entries. Record is different from a Document, since a Document element represents
some physical object that exists elsewhere in the physical world (even if it is an
electronic document), while a Record element exists directly in the EvidenceContainer.
name:String the name of the record
content:String the content of the record
Record is defined as "a thing constituting a piece of evidence about the past, esp. an
account of an act or occurrence kept in writing or some other permanent form". In the
Evidence Metamodel Record element is such thing. In contrast to a Document element, a
Record is not a representative of some other physical object, but the object itself. A
Record is therefore similar to an Object, however it is considered a structured element
with an informal content rather than a formal element.
Changes to Figure EvidenceElements (Figure 10.1) were illustrated in related resolutions
(e.g. 16800) and is presented below. <<diagram on p 121 of ptc/2012-06-04>>
Updated: Fri, 6 Mar 2015 20:58 GMT