[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [office] OpenDocument TC Work-Call Meeting Minutes 2006-03-13
Attendees --------------------------------------------------------------------------- Nathaniel Borenstein, IBM Robert Weir, IBM Patrick Durusau, Individual Yue Ma, IBM David Faure, KDE Jody Goldberg, Novell Michael Brauer, Sun Microsystems Lars Oppermann, Sun Microsystems Florian Reuter, Sun Microsystems Daniel Carrera, OpenDocument Foundation Gary Edwards, OpenDocument Foundation David Wheeler, OpenDocument Foundation Observers: Paul Langille, Corel Acceptance of Minutes from Last Call --------------------------------------------------------------------------- The attending TC members unanimously accepted the minutes from the last work call Action Items --------------------------------------------------------------------------- Michael, David: work on settings interop/spec - ongoing Lars: mimetype-registration - posted new version to list Topics Discussed --------------------------------------------------------------------------- Mimetypes: It was unclear whether Macintosh file type codes should be included in the registration. Since these are no longer officially supported by Apple, it was decided to proceed with the registration. http://developer.apple.com/faq/datatype.html SC Minutes: The minutes for the first formula SC meeting are now available on the SC's mailing list In the future, SC minutes will be CC'ed to the TC list to make it easier for all TC members to track progress of the SCs Table cell templates: alternatives: a) ref paragraph style directly from cell element b) ref para style from cell style c) new template style family for now, we will recommend option (a) to the TC coordination call, since this is most consistent with the current specification and only adds a new attribute to the cell template element. If the style system is to be reevaluated for a future version, it should be taken into consideration to find a more elegant solution for this issue. Style name uniquness. A style currently is uniquely identified by its family and its name. It would be easier for implementors, if there was a single information item, by which a style can be identified within a document. Requiring uniqueness of style:name might render existing documents invalid and applications assuming uniqueness will get problems when reading files that don't assure uniqueness of style names. Florian proposed to at least establish something like a 'best practice' to use unique style name in order to ease implementation. Style ordering: The order in which styles are defined is not relevant. Is legal for a style to reference a parent style that has not been defined when the style is read, as long as the parent style is defined in the document. New Action Items --------------------------------------------------------------------------- Lars: send mimetype registration to IANA Next conference call --------------------------------------------------------------------------- TC coordination call: 2006-03-20 4PM GMT – 5:00PM GMT TC work call: 2006-03-27 4PM GMT – 5:00PM GMT
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]