# URC-Authors section

Sally Hambridge (sallyh@Ludwig.intel.com)
Mon, 11 Jul 94 10:03:08 PDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Daniel W. Connolly: "X/Open Adopts Federated Naming (fwd)"
- Previous message: Michael Mealling: "Re: URC-Authors section"
- Next in thread: Raphael Freiwirth: "Re: URC-Authors section"
- Maybe reply: Raphael Freiwirth: "Re: URC-Authors section"
- Reply: Michael Mealling: "Re: URC-Authors section"
- Maybe reply: Alexander Dupuy: "Re: URC-Authors section"

    Date: Mon, 11 Jul 94 10:03:08 PDT

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

    Message-Id: <9407111703.AA20633@Ludwig.intel.com>

    To: ccoprmm@oit.gatech.edu, hoyman@gate.net, mark_crook@oclc.org,

    Subject: URC-Authors section

I think I might have a solution to the author's names that will
satisfy the librarians in the crowd and the people who want a stark
spec.

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.

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.

I know the prose is awkward at this point.

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.

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.

Comments?

Sally

---------------------------------------------------------------------------
|Sally Hambridge Internet: sallyh@ludwig.Intel.com |
|Intel Corp, SC3-15 Hambridge@sc.Intel.com |
|2880 Northwestern Parkway, PO Box 58119 Phone: 408/765-2931 |
|Santa Clara, CA 95052-8119 Fax: 408/765-3679 |
|-------------------------------------------------------------------------|
| "Now *here*, you see, it takes all the running *you* can do, to keep in |
| the same place. If you want to get somewhere else, you must run at |
| least twice as fast as that!" |
| The Red Queen to Alice, _Through the Looking Glass_ |
---------------------------------------------------------------------------

- Next message: Daniel W. Connolly: "X/Open Adopts Federated Naming (fwd)"
- Previous message: Michael Mealling: "Re: URC-Authors section"
- Next in thread: Raphael Freiwirth: "Re: URC-Authors section"
- Maybe reply: Raphael Freiwirth: "Re: URC-Authors section"
- Reply: Michael Mealling: "Re: URC-Authors section"
- Maybe reply: Alexander Dupuy: "Re: URC-Authors section"