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


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

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

Subject: Re: [chairs] Unique OASIS document identifiers

I can live with Eve's suggestion.  Among other things, it reflects the
consensus this group already achieved, it is reasonable, it gets the job
done and, perhaps best of all, it has the advantage of almost certainly
assuring closure on a range of debate that has stretched beyond the point of
diminishing returns.

 - Dan

|  Daniel J. Greenwood, Esq.
|  Director, E-Commerce Architecture Program
|  MIT School of Architecture and Planning
|  77 Massachusetts Avenue, Room 7-231
|  Cambridge, MA 02139
|     http://ecitizen.mit.edu
|     or http://www.civics.com
|     dang@mit.edu

----- Original Message -----
From: "Eve L. Maler" <eve.maler@sun.com>
To: "'Chairs (E-mail)'" <chairs@lists.oasis-open.org>
Sent: Monday, March 10, 2003 3:13 PM
Subject: Re: [chairs] Unique OASIS document identifiers

> (Unfortunately, as of right now I have ever-more-limited time for
> further updates to the writeup and the discussion it entails.  But I'm
> very happy for someone else to pick up the next round of editing if the
> chairs community wants to change the proposal.  Any takers?  I can send
> you the DocBook source...)
> The current proposal has charter / draft / cs / oasis.  If we're opening
> this up again, and especially if we're reopening the lowercase thing,
> that's a lot of variables.  For just the third position in that list
> alone, there's cs, CS, spec, Spec, cttespec, CtteSpec, tcspec, TCspec,
> TCSpec, ...
> But I believe that we already had consensus around "cs" (seeing as the
> proposal went out in its supposedly-final form on 25 Feb, having been
> reviewed starting on 11 Feb), so rather than asking if people can't live
> with "TC Spec" (which has a space and so isn't quite in the right
> formulation yet), I think it's more appropriate to ask if people can't
> live with "cs".
> Eve
> jkeane wrote:
> > The term "spec" conveys meaning. "cs" has at least 146 meanings as an
> > acronym, but not 'committee spec". (See below)
> >
> > Think of a newcomer to the site, puzzling over the name of one of our
> > important documents. Or someone conducting search.
> >
> > Are the other official document types "charter" and "standard"? If so
> > or "TC Spec" (as proposed) seems preferable.
> >
> > Does everyone agree with just deleting the reference to all lower case
> > the deleting the reference to "underscores."
> >
> > If so, we are very close to a wrap.  In LegalXML we have closed
> > by asking: "Can anyone not live with this?"
> >
> > Can any one not live with "TC Spec" and deleting the references to all
> > case and to underscores. Can we leave it Eve to balance out the
> > to different TC's rather than using OdrXML as the only example?.
> >
> > Jim Keane
> --
> Eve Maler                                        +1 781 442 3190
> Sun Microsystems                            cell +1 781 354 9441
> Web Technologies and Standards               eve.maler @ sun.com
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

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