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] Thoughts on ODF-Next


Andreas J. Guelzow wrote:
> On Mon, 2011-01-17 at 18:24 -0700, Patrick Durusau wrote:
>> Michael,
>> On Mon, 2011-01-17 at 11:59 +0100, Michael Brauer wrote:
>>> Hi Andreas,
>>> Andreas J. Guelzow wrote:
>>>> While I realize that we can't mandate that and in fact have no control
>>>> over whether a vendor calls their format ODF1.3 or whatever, I thin kwe
>>> A CSD approval is the first level of approval in the OASIS TC process.
>>> So, if we approve an ODF 1.3 draft as CSD, and if an implementor 
>>> implements this CSD, why shouldn't that be called ODF 1.3? How would you 
>>> call it instead?
>> I don't think successive CSDs would all be called ODF 1.3, without more.
>> See the Naming guidelines,
>> http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html, in
>> part:
> Patrick, we are not talking about what the TC or OASIS calls the various
> CSD but what the version string would be that is used in ODF files
> created by vendors that implement ODF1.3CSD1. I don't think the version
> string should be just "1.3"

What we are developing are OASIS standards, and the CSDs are just 
intermediate draft on our way to the OASIS standards. I'm not in favor 
of using different versions strings, since this may be misinterpreted as 
giving CSD more weight than they have.

But there are other options. We may for instance add an attribute that 
maybe used in content.xml, styles.xml, etc. and which links to the 
schema against wich the file is valid. All schemas we approve will be 
available at docs.oasis-open.org, and the name of the schema contains 
the CSD number. It therefore unambiguously identifies the CSD that has 
been used for the implementation that created a document.

The same method could be used to link extended ODF documents to a schema 
that includes the used extensions. This would allow to validate such 
documents, what is not possible right now.

Best regards


Michael Brauer | Oracle Office Development
Phone: +49 40 23646 500
Oracle Office GBU

ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Rijnzathe 6, 3454PV De Meern, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven

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