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] One strictly conforming document?


Michael,

Michael Brauer - Sun Germany - ham02 - Hamburg wrote:
> Hi Patrick,
>
> On 02/02/09 15:46, Patrick Durusau wrote:
>> Greetings!
>>
>> Granted that I fully support Michael's notion that the ODF TC should 
>> in the future be able to more routinely produce standard extensions 
>> to the format, but I also realize there maybe custom uses where there 
>> is no desire or need for an standardized extension. Or at least I 
>> would prefer to keep that open as a possibility and not to deny 
>> applications that substantially rely on ODF 1.2 from being able to 
>> claim that they conform to ODF 1.2 (as does their output, to the 
>> extent that it does).
>
> I think it is important that users know whether an application that 
> claims to be ODF 1.2 compliant is able to store documents without 
> extensions, or only documents that contain such extensions. So, if we 
> would give up the requirement that all ODF producers are able to 
> produce strict conforming documents, we at least would need an 
> additional conformance class for producers, so that one can differ 
> between a producer that is able to create strictly conforming 
> documents, and one that isn't. This may be an option, but it doesn't 
> make it easier to understand what the various conformance levels 
> actually mean.
>
> What do you think?
>
Well, but the difficulty may be in your statement: "I think it is 
important that users know whether an application that claims to be ODF 
1.2 compliant is able to store documents without extensions, or only 
documents that contain such extensions." That really isn't the purpose 
of a conformance clause. A conformance clause is supposed to define what 
a conforming application must or must not do. It is not a guide to or 
restriction on what a conforming application must inform a potential 
user about its conformance.

In other words I would like to distinguish between our 1) defining of 
conformance for ODF documents and the applications that process them 
from 2) defining what any conforming application (that is one that meets 
our conformance requirements) says about its conformance.

The former is a proper concern of this TC, the latter (at least in my 
opinion) is not. The latter strays into marketing strategies and other 
concerns.

Hope you are having a great day!

Patrick



> Best regards
>
> Michael
>>
>> Hope everyone is at the start of a great week!
>>
>> Patrick
>>
>>
>>
>>
>>
>>
>>
>>
>
>

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)



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