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


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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

Subject: Re: [office] The Rule of Least Power

On Thursday 12. February 2009 11:49:33 ext robert_weir@us.ibm.com wrote:
> > I've asked in another mail for your reason to drive this proposal.
> > Please give
> > a usecase where the current ODF conformity clause will give us headaces.
> > I don't see them and I will never be convinced to take away useful and
> > good features unless I see a good reason where it ends up hurting more.
> Sorry, we must have missed each other's messages in the traffic.  I
> addressed the specific kinds of problems caused by the general mechanism
> in this note:
> http://lists.oasis-open.org/archives/office/200902/msg00070.html

That mail just posts some anonymous element; thats not a usecase.
I can't even argue that the "foo:bar" is or is not a loss if an implementation 
ignores it since you don't give a realistic usecase to argue from.

> Now, you might very well say, "But here are N specific examples where this
> is not a problem".  But that proves my point.

I'd rather call a real usecase where things go really wrong 'proof' ;)

> If those N specific 
> examples can be written using a more targeted extension mechanism, then we
> can get the benefits without the liabilities.

Hmm, there is an assumption in there where we can properly create an extension 
mechanism for all usecases.
I notice that in the linked mail you were under the impression that nobody 
uses this feature in the first place. Which turns out to be a 
misunderstanding, KOffice has used it for years.

I have given 4 examples where we currently use namespaced extensions in my 
mail 2 days ago.  One is legal, one *may* be made into an extention if we see 
an advantage to that, and two proper and current usecases are not even 
addressed. Meaning that if we forbid their usage KOffice might have to look 
at not using pure ODF as its native fileformat. That can't be the intention.

Can I ask you to reconsider your proposal based on the new information that we 
use extentions using namespaces in more than one implementation (I named 3) 
already and in a variety of places in the XML tree which defies a clean 
extention mechanism ?

Thomas Zander

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