# Re: URC-Authors section

Michael Mealling (ccoprmm@oit.gatech.edu)
Mon, 11 Jul 1994 14:15:27 -0400 (EDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Sally Hambridge: "URC-Authors section"
- Previous message: Michael Mealling: "Re: URC-Authors section"
- In reply to: Sally Hambridge: "URC-Authors section"
- Next in thread: Daniel W. Connolly: "Re: URC-Authors section"
- Reply: Daniel W. Connolly: "Re: URC-Authors section"

    From: ccoprmm@oit.gatech.edu (Michael Mealling)

    Message-Id: <199407111815.AA05834@oit.gatech.edu>

    Subject: Re: URC-Authors section

    To: sallyh@Ludwig.intel.com (Sally Hambridge)

    Date: Mon, 11 Jul 1994 14:15:27 -0400 (EDT)

    In-Reply-To: <9407111703.AA20633@Ludwig.intel.com> from "Sally Hambridge" at Jul 11, 94 10:03:08 am

Sally Hambridge said this:
> I agree that we don't want to get into a long debate about name formatting,
> since I know how long it took librarians to get to AACR2 (and yes, Mark,
> I dug out my copy over the weekend.) But I think I disagree with Dirk
> that we don't want any specification of how to do names in the draft. If
> we leave this solely to implementers, then we will lose all chance of giving
> users a unified syntax of names which will be useful for sorting.

Very well said....

> So - I suggest (and word smithing is encouraged) that we say:
>
> o Author:
> This pair will encode the name of the Author(s) of a given document or
> resource. Since many cultures have different ways of writing names,
> the standard name representation should be that the first element of
> the value should be the first element of the name to be parsed for
> sorting purposes, the second element of the name should be the
> second element to be parsed, and so on.

Sounds reasonable....

> We can have examples here of single personal authors, multiple authors,
> corporate authors, and authors with "funny" characteristics (like Van Gogh).
>
> Author: Hambridge, Sally
> Author: International Business Machines
> Author: Hambridge, Sally; Doe, Jane
> Author: Stanford University. Dept of Computer Science.

Ok. How do we deal with this name: Herbert Baines, III.

> I think what this does is allow latitude for the implementers, but specify
> a uniform (and librarian/AACR compliant) method of representing names that
> will provide a parsing mechanism for clients and servers.

It sounds reasonable. I'm not of the library community so I don't know
how they feel but it's implementable and isn't to esoteric......

    --
    ------------------------------------------------------------------------------
    <HR><A HREF="http://www.gatech.edu/michael.html">
    <ADDRESS>Michael Mealling</ADDRESS>
    <ADDRESS>michael.mealling@oit.gatech.edu</ADDRESS></A>

- Next message: Sally Hambridge: "URC-Authors section"
- Previous message: Michael Mealling: "Re: URC-Authors section"
- In reply to: Sally Hambridge: "URC-Authors section"
- Next in thread: Daniel W. Connolly: "Re: URC-Authors section"
- Reply: Daniel W. Connolly: "Re: URC-Authors section"