Heiko Jansen wrote:
The MODS specification has seen a number of revisions already where elements
and attributes have been added, removed, declared (no longer) mandatory, or
where the list of allowed values has been changed. My goal would be to
support
a number of older versions and all
Am Mittwoch, 19. Mai 2010 00:52:29 schrieb Chris Prather:
There are a few minor questions related to b) - regarding, e.g., the
handling of attributes belonging to different namespaces - which can
probably be sorted out - read: expect more mails to come ;-)
I don't know about PRANG but
On Wed, May 19, 2010 at 5:32 AM, Heiko Jansen heiko_jan...@web.de wrote:
first - but the mentioning of compile time leaves me wondering how it would
be possible to parse MODS records at runtime whose versions I don't know
beforehand (or even how to deal with MODS records in different versions
Dear Moose-icians,
I'm currently pondering on the idea of writing a Perl module for bibliographic
records using the MODS format (http://loc.gov/mods).
Basically there are two approaches I'm considering right now:
a) Using XML::Compile::Schema for parsing and writing the XML records and
On Tue, May 18, 2010 at 11:59:57PM +0200, Heiko Jansen wrote:
Dear Moose-icians,
Heh, I like that one!
But how am I supposed to tackle this problem using Moose/PRANG? Changing the
'isa' property of Moose attributes at runtime based on the value of another
attribute (holding the MODS
On Tue, May 18, 2010 at 5:59 PM, Heiko Jansen heiko_jan...@web.de wrote:
Dear Moose-icians,
I'm currently pondering on the idea of writing a Perl module for bibliographic
records using the MODS format (http://loc.gov/mods).
Basically there are two approaches I'm considering right now:
a)
