Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Odud (1047)

  (email not shown publicly)

Journal of Odud (1047)

Monday January 21, 2002
03:55 PM


[ #2300 ]
EDItEUR ( coordinate the development of standards for
electronic commerce for the book trade. They have created a standard called
ONIX which is closer to what I want than MARC but is still a bit too complex.
Also the terms of use seem to go against the usual free software licence in
that it seems that you can't modify it for your own use without their
permission. So in the end I've come up with my own way and what I have is
something like:

        <contributor type="03">Falkus, Christopher</contributor>
        <contributor type="01">Woodhouse, P. G.</contributor>
        <title type="01">Short Stories</title>
        <location>Folio Bookcase</location>
        <publisher>The Folio Society</publisher>

The type attribute for contributor is to distinguish between author and editor
etc. And for title it lets subtitles etc. be shown. This looks o.k. to me (in
that it lets me do the sort of searching and cataloguing that I'm interested
in) and because it is not too deep it should be easy to process with a SAX

All I need to do now is to work out how to store the XML in the database.....
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Use an OODBMS?
      ---ict / Spoon
  • The snippet you displayed completely defeats the purpose and intent of XML by adopting obfuscated type attributes.

    What about type="01" denotes the concept of "author"? Why is type="01" an author on a contributor field, but "primary title" on a title field?

    This is a classic error made time and time again since the dawn of punch cards: space is important, so let's condense the amount of space a record takes up by replacing textual values with an encoded equivalent. This problem was first brought to my a