I propose that we add bf:Microform as a Class, specifically a bf:Instance subclass. However, since all the Work types are aligned with the LDR types, bf:Microform might end up as a Work subclass.
In MARC21, the 007 field allows a cataloger to code different physical formats represented in the same record. The 007 types mostly match the ldr types which are now aligned with the bf:Work types, except for Globe 'd', Remote-sensing image 'r' and Microform 'h'. I assume globe and remote-sensing image might also need separate classes in BIBFRAME but I don't know the use case for those types.
Because of the way this is done in MARC (see the CONSER editing guide in Cataloger's Desktop for more info), a microfilm record would have a LDR/06 type of 'language material', a LDR/07 blvl which is one of the continuing resource options (aka 's'), a microfilm 007 starting with hd, and a 338 carrier code (also hd). This turns into a bf:Text, bf:Serial work with a bf:Print instance with a bunch of microfilm physical properties from the 007 bytes.
MARC21 compresses a lot of information so in a microfilm record you end up describing the print resource as well as the microfilm of that print resource. Adding an instance subclass would allow the specifics of the microfilm to be described, such as the generation, film base, polarity, reduction ratio, etc. as bf:Microfilm properties not bf:Print properties. And the Serial work could hasInstance to its print and microfilm instances since they should share the same Work properties. If we want to align with current MARC-based rules (again see the CONSER guidelines), you would have separate records for print, microform and electronic so you would have a bf:Text, bf:Microform and bf:Electronic works.
Finally, outside of continuing resources, microform is used with books, manuscripts and other rare materials, images, maps, notated music, etc. Having a separate type would allow distinguishing these physical manifestations as well.
I propose that we add bf:Microform as a Class, specifically a bf:Instance subclass. However, since all the Work types are aligned with the LDR types, bf:Microform might end up as a Work subclass.
In MARC21, the 007 field allows a cataloger to code different physical formats represented in the same record. The 007 types mostly match the ldr types which are now aligned with the bf:Work types, except for Globe 'd', Remote-sensing image 'r' and Microform 'h'. I assume globe and remote-sensing image might also need separate classes in BIBFRAME but I don't know the use case for those types.
Because of the way this is done in MARC (see the CONSER editing guide in Cataloger's Desktop for more info), a microfilm record would have a LDR/06 type of 'language material', a LDR/07 blvl which is one of the continuing resource options (aka 's'), a microfilm 007 starting with hd, and a 338 carrier code (also hd). This turns into a bf:Text, bf:Serial work with a bf:Print instance with a bunch of microfilm physical properties from the 007 bytes.
MARC21 compresses a lot of information so in a microfilm record you end up describing the print resource as well as the microfilm of that print resource. Adding an instance subclass would allow the specifics of the microfilm to be described, such as the generation, film base, polarity, reduction ratio, etc. as bf:Microfilm properties not bf:Print properties. And the Serial work could hasInstance to its print and microfilm instances since they should share the same Work properties. If we want to align with current MARC-based rules (again see the CONSER guidelines), you would have separate records for print, microform and electronic so you would have a bf:Text, bf:Microform and bf:Electronic works.
Finally, outside of continuing resources, microform is used with books, manuscripts and other rare materials, images, maps, notated music, etc. Having a separate type would allow distinguishing these physical manifestations as well.