Metadata

27 November 2014 20:09
Gordon Dunsire (ifla)
27 November 2014 20:09
Gordon Dunsire (ifla)

Detail

Reproduction Event
ReproductionEvent
 
This class comprises activities that consist in making copies, more or less mechanically, of an instance of E84 Information Carrier (such as an F5 Item or an F4 Manifestation Singleton which is also instance of E84 Information Carrier), preserving the expression carried by it.
This class comprises activities that consist in making copies, more or less mechanically, of an instance of E84 Information Carrier (such as an F5 Item or an F4 Manifestation Singleton which is also instance of E84 Information Carrier), preserving the expression carried by it. A Reproduction Event results in new instances of E84 Information Carrier coming into existence. In general, the copy will have different attributes from the original and they are therefore not regarded as siblings. This class makes it possible to account for the legal distinction between private copying for the purpose of "fair use", and mass production for the purpose of dissemination. It can prove difficult to determine where to draw the line between F33 Reproduction Event and F32 Carrier Production Event in cases where multiple copies are produced. In this case, the copies, but not the original, may be regarded as instances of F5 Item. It is the existence of an explicit production plan that makes the difference. As a consequence, F33 Reproduction Event and F32 Carrier Production Event are not declared as disjoint, which makes it possible to account for such situations that could be regarded as instances of both Production Event and Reproduction Event.
class
http://www.cidoc-crm.org/ci...
Published
English
A Reproduction Event results in new instances of E84 Information Carrier coming into existence. In general, the copy will have different attributes from the original and they are therefore not regarded as siblings. This class makes it possible to account for the legal distinction between private copying for the purpose of "fair use", and mass production for the purpose of dissemination. It can prove difficult to determine where to draw the line between F33 Reproduction Event and F32 Carrier Production Event in cases where multiple copies are produced. In this case, the copies, but not the original, may be regarded as instances of F5 Item. It is the existence of an explicit production plan that makes the difference. As a consequence, F33 Reproduction Event and F32 Carrier Production Event are not declared as disjoint, which makes it possible to account for such situations that could be regarded as instances of both Production Event and Reproduction Event.