OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: DOCBOOK: [ #456174 ] Req: a <YearRange> within <copyright>

> From: Norman Walsh <ndw@nwalsh.com>
> In
> http://sourceforge.net/tracker/index.php?func=detail&aid=456174&group_id=21935&atid=384107
> Yann Dirson suggests that a yearrange element be added to copyright.
> The TC considered this and admitted to a certain amount of fudging in
> practice, using <year>1999-2001</year>. This is less than ideal, but
> what have other people elected to do when faced with this problem?
> Another obvious possibility is to let the stylesheet take care of
> the collation.

Is further structure really necessary here?
Would a yearrange look something like this:


Seems like overkill, IMHO.
I like the simplicity of permitting <year>1999-2001</year>.
Its meaning is quite clear, in all languages.
I'm sure there are XML applications that may be expecting a
4-digit year, but perhaps the burden should be on those
applications to parse a range into individual years.

Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
Caldera International, Inc.                 fax:   (831) 429-1887
                                            email: bobs@caldera.com

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC