Re: MARC structure (Was: Re: Ceci n'est pas un catalogue)

From: Alexander Johannesen <alexander.johannesen_at_nyob>
Date: Mon, 27 Aug 2007 17:09:39 +1000
To: NGC4LIB_at_listserv.nd.edu
On 8/27/07, Bernhard Eversberg <ev_at_biblio.tu-bs.de> wrote:
> [...] what ideas, concepts, models,
> prototypes are there for a better implementation?
> Frankly, I'm still sure XML will eventually wither away because
> of its ugly bulk and its ensuing clumsyness.

Huh? XML wither away as an exchange format, or modeling tool? No to
both, really. I suspect that the limitations of MARC21 exist plentiful
in various vendors and our own software.

> There _must_ be better
> ways of handling things, more elegant ways. In the long run,
> elegance must win. Standards, however, tend to make the run towards
> elegance longer rather than shorter.

Hmm. What about XML as a standard is not elegant? Or are you referring
to people using elegant tools to make crap (which indeed happens all
the time)?

What, exactly, is the difference between ;

<record>
    <datafield tag="245" ind1="1" ind2="0">
      <subfield code="a">[Interview with Keith McCance&#93;</subfield>
      <subfield code="h">[sound recording&#93; /</subfield>
      <subfield code="c">[Interviewer : Bronwyn Benn&#93;.</subfield>
    </datafield>
</record>

and ;

<record>
    <title>
      <main>Interview with Keith McCance</main>
      <media>sound recording</media>
      <responsible>Interviewer : Bronwyn Benn</responsible>
    </title>
</record>

and ;

<record>
   <title>Interview with Keith McCance</title>
   <media>sound recording</media>
   <made_by>Bronwyn Benn</made_by>
</record>

and ;

<record>
   <title lang="en">Interview with Keith McCance</title>
   <type psi="http://library.net/resource_types/sound" />
   <relationship of-type="http://library.net/media/creation">
      <identity
psi="http://library.net/identity/person/Bronwyn_Benn(b_1987_Sydney)"
/>
   </relationship>
</record>

or even ;

  record:
     title: 'Interview with Keith McCance'
     type: http://library.net/resource_types/sound
     relationship:
        type: http://library.net/media/creation
        identity: http://library.net/identity/person/Bronwyn_Benn(b_1987_Sydney)


There's many ways in which to implement metadata, with or without
schemas, ontologies and metadata format specials. In the two last
examples I'm using identity control which our tools must understand
(or at least, understand to resolve). When I exchange this data with
anyone, which one will most people understand, and a) which one will
they use to create their own tools, and b) what limitations (perceived
or otherwise) in the selected format can sneak into the tool?

As most systems and tools have got MARC21 as their basis, how much of
the limitations of that format is inherit in those systems and tools?
What will be the cost to break out of it? Will it even ever happen?


Alex
--
 ---------------------------------------------------------------------------
 Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps
------------------------------------------ http://shelter.nu/blog/ --------
Received on Mon Aug 27 2007 - 03:09:39 EDT