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


Help: OASIS Mailing Lists Help | MarkMail Help

oiic-formation-discuss message

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

Subject: ODF compatibility, alt. CDRF standards (was: The importance to users of documents looking the same)


Based on your current thinking, this is clearly the wrong place for you. This is to discuss a charter for a TC to look at ODF interop. If you want to create an ODF-incompatible standard, by all means start a TC, but it is off-topic here. If you don't think ODF can work interoperably, that's a fine view to hold, but it's irrelevant to the work on the new TC. You might be right that there are limits to interop; in this instance, c'est la vie; the enemy of the good is the perfect.

Additionally, with respect to your points on CDRF:

----- Original Message ----
From: marbux <marbux@gmail.com
Subject: Re: [oiic-formation-discuss] The importance to users of documents looking the same

> CDRF, through its incorporation by references of the modal definition
> of "may" in RFC 2119, also requires that implementations of the subset
> profile be capable of processing the content of the superset profile
> even with reduced functionality.

It makes no such requirement.

It _does_ require that superset apps process subset content as if it were superset content. 

It _does not_ require that subset apps process superset content in any way.

See, e.g.., the conformance criteria of WICD Mobile, which does not even optionally suggest such a thing:



Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

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