In MARC::Doc::Tutorial, it mentions: Note to the curious: the C<as_usmarc()> method is actually an alias to the MARC::File::USMARC C<encode()> method. Having separate C<encode()> methods is a design feature of the MARC class hierarchy, since it allows extensions to be built that translate MARC::Record objects into different data formats.
How far does "different data formats" apply? Only to MARC subsets? What if I wanted to make MARC::File::MODS? MARC::File::DublinCore? Would those be considered valid data formats for extension? -- Morbus Iff ( shower your women, i'm coming ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
