Print

Print


Just a reminder that "roles" are often usefully considered relationships
of names to resources (the objects of concern to libraries, archives,
museums, etc.).  A person may play many "roles" relative to any given
resource (author, illustrator, composer, artist, performer, editor,
publisher, owner, etc.).  Also a person/corporate body  over their life
time may have many roles, titles, addresses, nationalities, etc., so we
want to be sure the structure accommodates those realities.
"Occupations" might be associated with a person, or fields of study and
Ed O'Neill at OCLC has done some research about useful elements to
identify entities that he built into his matching algorithms (including
dates, subjects, languages, places of publication, etc.).

Presumably, the choice of the elements to be displayed for any given
purpose, can be handled by style sheets, so I have no problem with
constructing the XML DTD to enable more than what we do now.  Has anyone
looked at the EAC DTD used for the LEAF Project to compare that with
what MADS is proposing?  I think that would be a fruitful exercise, if
someone can make the time. - Barbara Tillett

Dr. Barbara B. Tillett, Ph.D.
Chief, Cataloging Policy and Support Office
Library of Congress
101 Independence Ave., S.E.
Washington, D.C. 20540-4305
U.S.A.

tel.: +1 (202) 707-4714
fax: +1 (202) 707-6629
email: [log in to unmask]

>>> [log in to unmask] 6/10/2004 1:04:09 PM >>>
On Thu, 10 Jun 2004 12:26:35 -0400, "Ruth Bogan"
<[log in to unmask]>
said:
> When you deconstruct the heading into the biography, you make the
record
pretty much useless as an
> authority record.

Am again in a hurry, but on this: the focus in my example is on
logical
structure easily ammenable to processing. I presume some basic
scripting/xslt logic to get the data into whatever display form one
would
want (it should be easy,even for me). It would also make it more
flexible
(I think) for data searching.

> Would it be too much to ask you to "redo" one of the sample MADS
records
> at
> the MADS web site, in a way that makes sense to you. I would find it
> interesting.

No, here's two, with comments:

<?xml version="1.0" encoding="utf-8"?>
<mads xmlns="http://www.loc.gov/mads/">
  <authority>
    <organization>
      <orgName>Whatever Organization</orgName>
    </organization>
  </authority>
<!--
1) Get rid of elememts like ref and refs and replace them with what
they
really refer
to, with options of: organization, person, event, place, and work.

2) Make that wrapper element enclose the entire authority record data.
-->
  <organization>
    <name>
      <primary>
        <orgName>Federal Bureau of Investigation</orgName>
      </primary>
<!--
Following suggestion of Andy S., have variant as a full element.  MADS
and MODS rely too
much on attributes, which are inflexible. Have variant elements
enclosed
within their
referent. One cannot, after all, have a non-name acronym variant in
the
above. The above
structure makes both human reading and XML processing easier.
-->
      <variant type="acronym">
        <orgName>FBI</orgName>
      </variant>
    </name>
<!--
Remove role from name, since they are two separate pieces of metadata.
-->
    <role>
      <roleTerm>???</roleTerm>
    </role>
    <time>
<!--
It is really important for processing XML to parse data where
appropriate. Dates is a perfect
example. If I want all organizations estbalished in the United States
in
the first two decades
of the 20th century, it's simple to do this with vanilla XML tools.
Otherwise, it is not.
-->
      <temporal encoding="w3cdtf" qualifier="approximate"
      point="start">1919</temporal>
    </time>
    <place>
      <address>
        <street>123 3rd Avenue</street>
        <city>Washington</city>
        <state>DC</state>
<!--
An email is typically considered an address.
-->
        <email>[log in to unmask]</email>
      </address>
    </place>
  </organization>

And, the second:

<?xml version="1.0" encoding="utf-8"?>
<mads xmlns="http://www.loc.gov/mads/">
  <authority>
    <organization>
      <orgName>Whatever Organization</orgName>
    </organization>
  </authority>
  <person>
    <name>
      <primary>
<!--
It's hard to process names without knowing if it they are abbreviated
or
not,
and abbreviation of name parts is different than abbreviation of the
name
as a whole.
-->
        <givenName abbreviated="yes">J</givenName>
        <givenName>Edgar</givenName>
        <familyName>Hoover</familyName>
      </primary>
    </name>
    <time>
<!-- Am not sure if I like this date handling, but will keep for now
-->
      <temporal encoding="w3cdtf" qualifier="approximate"
      point="start">1900</temporal>
      <temporal encoding="w3cdtf" qualifier="approximate"
      point="end">1972</temporal>
    </time>
    <affiliation>
<!--
Not sure the details are right below, but basic idea is to be able to
represent changing
positions, and even affiliations. Think of a lawyer who becomes a
Supreme
Court Judge,
and so forth.
-->
      <organization>
        <orgName>Federal Bureau of Investigation</orgName>
        <position>
          <title>Director</title>
          <temporal encoding="w3cdtf" qualifier="approximate"
point="start">1924</temporal>
          <temporal encoding="w3cdtf" qualifier="approximate"
point="end">1972</temporal>
        </position>
        <position>
          <title>Assistant Director</title>
          <temporal encoding="w3cdtf" qualifier="approximate"
point="start">1919</temporal>
          <temporal encoding="w3cdtf" qualifier="approximate"
point="end">1924</temporal>
        </position>
      </organization>
    </affiliation>
  </person>
</mads>