MHonArc v2.5.0b2 -->

















office message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Re: [office] Action required: OpenDocument v1.0 Second Edition Draft 28 (revised)




From: robert_weir@us.ibm.com
To: OASIS Office <office@lists.oasis-open.org>
Date: Mon, 19 Jun 2006 20:23:54 -0400




If we do this, I'd like us to also write
up and adopt a formal deprecation policy for the TC -- what does it mean,
how is it decided, is support ever removed entirely, etc.  Deprecation
is a powerful thing and useful for maintaining the health of the specification.
 But like forest fires, we need to consider carefully how and when
we use them.

-Rob

Patrick Durusau <patrick@durusau.net> wrote
on 06/19/2006 07:53:48 AM:


> Michael,

>

> Your option c:

>

> > c) we correct the spelling errors in the schema, but keep the

> > misspelled attribute values/names addionaly in the schema and
declare

> > the to be deprecated by a comment.

>

> Looks like the right approach to me.

>








References:

Re: [office] Action required: OpenDocument v1.0 Second Edition Draft28 (revised)
From: Patrick Durusau <patrick@durusau.net>






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]