> From: Dave Pawson <[EMAIL PROTECTED]>
>
> >Then authors (editors, etc) might have this content model:
> >
> > author ::=
> > ((personname, personblurb, affiliation+, email+, address+))
>
>
> Sounds about right, though what of 'person's without
> affiliations? i.e. the great unemployed / s
At 21:12 13/11/2001 -0500, Norman Walsh wrote:
>Then authors (editors, etc) might have this content model:
>
> author ::=
> ((personname, personblurb, affiliation+, email+, address+))
Sounds about right, though what of 'person's without
affiliations? i.e. the great unemployed / self employe
On Tue, Nov 13, 2001 at 09:12:20PM -0500, Norman Walsh wrote:
> I have a long standing action item to revisit name and address markup.
> I think we can break "personname" out of this:
That looks good to me.
One thing that already puzzled me was the lack of a "middlename"
element, that would all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 18:12 13-11-2001, Norman Walsh wrote:
>I think we can break "personname" out of this:
Please - the lack of a name container has long troubled me.
~Chris
- --
Christopher R. Maden, Principal Consultant, HMM Consulting Int'l, Inc.
DTDs/schemas -
Looks fine to me.
> -Original Message-
> I think we can break "personname" out of this:
>
> personname ::=
> ((honorific|firstname|surname|lineage|othername)+)
>
> Then authors (editors, etc) might have this content model:
>
> author ::=
> ((personname, personblurb, affiliation
I have a long standing action item to revisit name and address markup.
The most often reported problem with the current markup is that there's
no way to associate an email address with a person independent of their
organizational affiliation.
No obvious right answer is occurring to me, so I thoug
