Message-Id: <9407112205.AA15021@ulua.hal.com>
To: ccoprmm@oit.gatech.edu (Michael Mealling)
Subject: Re: URC-Authors section
In-Reply-To: Your message of "Mon, 11 Jul 1994 14:15:27 EDT."
<199407111815.AA05834@oit.gatech.edu>
Date: Mon, 11 Jul 1994 17:05:05 -0500
From: "Daniel W. Connolly" <connolly@hal.com>
In message <199407111815.AA05834@oit.gatech.edu>, Michael Mealling writes:
>> 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.
First, list separate authors on separate lines. There is no "parsing"
beyond separating the header name from the value, and separating
values from each other.
Then, tell folks that the Author: field is likely to be passed to
strcmp() [or some analagous routine, if multibyte characters are
involved]
So I suggest:
Author: Hambridge, Sally
Author: International Business Machines
Author: Hambridge, Sally
Author: Doe, Jane
Author: Stanford University. Dept of Computer Science.
Author: Baines, Herbert III
Dan