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] 1.1 Introduction


Patrick,

Patrick Durusau wrote:
> Michael,
> 
> Michael Brauer - Sun Germany - ham02 - Hamburg wrote:
> 
>>Patrick,
>>
> <snip>
> 
>>>second paragraph reads:
>>>
>>>The schema retains high-level information suitable for editing
>>>document and is friendly to transformations using XSLT or similar
>>>XML-based languages or tools.
>>>
>>>Comment: 'The schema retains'?, seems awkward, along with 'suitable
>>>for editing document', which is true but it also supports creation of
>>>documents as well. Note number error with 'document.'
>>>
>>>Suggest:
>>>
>>>The schema defines suitable XML structures for office documents and is
>>>friendly to transformations using XSLT or similar XML-based tools.
>>
>>
>>The "The schema retains" sentence actually has been taken from our 
>>charter. Its purpose, in the spec as well as in the charter, is to 
>>clarify what the difference between our schema and for instance XSL-FO 
>>is. The later one could be used to save at least very simple office 
>>documents, but these documents cannot be edited with office applications 
>>again.
>>
>>For this reason, I think if we change the sentence so that it sounds 
>>better, we should keep the content (not the words) of the original 
>>sentence in a sub sentence or as a separate sentence.
>>
>>Do you have a suggestion for this?
>>
> 
> 
> Sure,
> 
> Suggest:
> 
> ***
> The schema provides for high-level information suitable for editing 
> documents. It defines suitable XML structures for office documents and 
> is friendly to transformations using XSLT or similar XML-based tools.
> ***
> 
> The first sentence to capture the distinction you mention and the second 
> to point out that it defines structures for office documents and is 
> 'friendly' for transformation.
> 
> Does that capture what you were looking for?

Yes, thanks. I've integrated your suggestion into the next draft.

Michael



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