Yann Dirson <[EMAIL PROTECTED]> writes:
> No, it's really useful. As an example, I have several email addresses,
> some of which may one day disappear with the org/machine that provides
> them, and I am affiliated at least to my employer and Debian, and may
> want to write something as part of bo
On Thu, Nov 15, 2001 at 06:45:24AM +0100, Karl Eichwalder wrote:
> Do you really want to allow more the 1 personblurb? Also it's enough to
> have 1 affiliation, 1 email, 1 address.
No, it's really useful. As an example, I have several email addresses,
some of which may one day disappear with the
Norman Walsh <[EMAIL PROTECTED]> writes:
> Actually, I think
>
>author ::=
>((personname, (personblurb|affiliation|email|address)*))
>
> is probably right.
Sometimes you're too generous, Norm :)
Do you really want to allow more the 1 personblurb? Also it's enough to
have 1 affiliation,
/ Bob Stayton <[EMAIL PROTECTED]> was heard to say:
| > From: Dave Pawson <[EMAIL PROTECTED]>
| >
| > >Then authors (editors, etc) might have this content model:
| > >
| > > author ::=
| > > ((personname, personblurb, affiliation+, email+, address+))
| >
| >
| > Sounds about right, though w
In response to some offline comments, I suggest:
/ Norman Walsh <[EMAIL PROTECTED]> was heard to say:
[...]
| Our current tags are
|
| author ::=
| ((honorific|firstname|surname|lineage|othername|affiliation|
| authorblurb|contrib)+)
|
| affiliation ::=
| (shortaffil?,jobtitle*,orgn
