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] ODF 1.2 - version info in meta inf?


After some more discussions on this:

It seems one central place for the version number is not a good idea.

Main reason: OLE objects. When having ODF OLE objects, the streams are
also listed in the manifest.xml, but the objects might use an other ODF
version.

Malte.

Malte Timmermann wrote, On 08/20/07 10:34:
> Sorry to be unclear.
>
> I didn't mean meta data. With "meta inf" I meant META-INF/manifest.xml.
>
> And yes, I also don't think that different streams should/would have
> different versions.
>
> IMHO manifest.xml. should be a central place for such information, since
> it will never become encrypted
>
> Malte.
>
>
> Dave Pawson wrote, On 08/20/07 09:58:
>   
>> On 20/08/07, Michael Brauer - Sun Germany - ham02 - Hamburg
>> <Michael.Brauer@sun.com> wrote:
>>
>>   
>>     
>>>>> Of course I can add the version info to the signatures stream, but I
>>>>> wonder if this isn't something that should be available "globally" via
>>>>> META-INF?
>>>>>         
>>>>>           
>>>> I can remember asking for the schema version to be added to an instance.
>>>> I *thought* that had been accepted.
>>>>
>>>> Isn't it available Malte? I think it was an attribute on the root element.
>>>> If missing, presume prior to 1.2
>>>>       
>>>>         
>>> The OpenDocument specification actually defines multiple schemas. The
>>> version attribute exists for the schemas used for the content.xml,
>>> styles.xml, meta.xml and settings.xml. But right now, it does not exist
>>> for the schema used by the META-INF/manifest.xml stream, and it does not
>>> exist for the schema used by the new META-INF/documentsignatures.xml stream.
>>>
>>>     
>>>       
>> Is this too complex?
>> Since the schemas are published as a group, with a single release, is it
>> likely that I will use content.xml from 1.1 and settings.xml from 1.2?
>>
>> It seems simpler to include a single  value on one file (it is metadata
>> so perhaps Malte is right to suggest it is added as metadata), rather
>> than 4 values in 4 different places?
>>
>>
>> regards
>>
>>
>>
>>
>>
>>   
>>     


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