[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [office] Open Office XML Format TC Meeting Minutes 18/19 Feb 2003
At 16:17 2003 02 26 +0100, Michael Brauer wrote: >MINUTES OF THE OASIS OPEN OFFICE XML FORMAT TC MEETING >FEBRUARY, THE 18TH/19TH, 2003, MENLO PARK, CA >The TC decided to use the term "_should_" for specifying application behavior that is strongly recommended, but not required to conform to the Open Office XML format specification, and the term "_may_" for application behavior that is considered to be useful (and wherefor recommended, too), but is considered to be less important than "_should_" behavior. More generally, I believe we should plan to reference and follow the IETF Best Practice document "Key words for use in RFCs to Indicate Requirement Levels" at: http://www.ietf.org/rfc/rfc2119.txt This has become common practice in W3C documents; see for example: http://www.w3.org/TR/xlink/#conformance http://www.w3.org/TR/2002/CR-xinclude-20020917/#terminology http://www.w3.org/TR/xmldsig-filter2/#sec-Terminology http://www.w3.org/TR/xmlenc-core/#sec-Editorial >C) Attributes for paragraphs/character runs >------------------------------------------- >The TC agreed that styles are suitable and sufficient to further markup paragraphs and character runs (but also other object types like drawing objects), provided that >- attributes and elements that are contained in a style but are not specified in the Open Office XML schema are preserved, and >- multiple styles can be assigned to a paragraph, character run, etc. >Since current office suite implementations support only single styles, and since supporting multiple styles seems not to be easy to implement, the TC unanimously agreed to the following: >- A "class" attribute will be added to all elements that reference a style already. The value of this class attribute is a space separated list of styles that are applied to the object additionally to the style referenced by the "style-name" attribute. In fact, I believe we said that the class attribute would be of XML type IDREFS: http://www.w3.org/TR/REC-xml#idref That is, each token must match the "name" production (prod [5]) of XML: http://www.w3.org/TR/REC-xml#NT-Name >- To be usable in a list, styles referenced by a "class" attribute must not contain space characters. More specifically, see my comment above. > For this reason, a "display-name" has to be added to styles. A description is also considered to be useful by the TC. The schema details of classes will be discussed by e-mail on the TC's mailing list. paul
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC