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: ODF 1.2: Next steps


Dear TC members,

with draft 8 of ODF 1.2 part 1, the first complete draft for this part
of ODF 1.2 is available, as well as the schemas that belong to it. Also
the restructuring of the document itself is nearly completed. The only
outstanding change here is a division of chapter 18 (attributes) into
one that describes formatting properties, and one that describes other
attributes. A draft that includes these changes may be completed in the
2nd week of February, and I would like to suggest that we approve this
draft and its schemas as a first ODF 1.2 part 1 Committee Draft.

It may take us about four weeks to further clean up the draft (that
includes for instance work on the editorial notes), so that we starting
with the 2nd week of March, may consider to send out the draft for a
public review. Please note that a public review requires a vote by the
TC and a previously approved Committee Draft. This means the decision to 
actually submit the draft for a public review is not a decision we can 
and have to make now, but only when the draft is actually available.

A few more tasks need to be completed before we actually can start
a public review, but I think it is realistic to aim to complete them
until the 2nd week of March, too.

Among these tasks are:

- Someone has to check the correctness of the examples.
- Someone has to check the correctness of the EBNF grammars.
- A list of changes has to be compiled.
My suggestion here is that someone goes through the list of integrated
proposals that we have in the Wiki, and extracts the information which
elements and attributes have been added, together with a very short
description. If a proposal adds an element, I would mention only that
element, but no child elements or attributes. If a proposal adds an
attribute, I would only mention the attribute. Patrick may amend this
list then by items that are not related toňõproposals.
- A list of the contributors has to be compiled. This is just a list of
the current TC membership + former TC members.
- The bibliographic references need to be checked for accuracy. That is,
it needs be checked whether URIs are valid, whether there are successors
for some specifications, and so on.

I would be glad if anyone of you volunteers to take over one of these
tasks, where the anticipated completion date is the 2nd week of March.
If we manage to complete all these tasks by that date, we at least
formally would meet all requirements for a public review.

There is another area where we have to work on during the next weeks.
That's the registry of public comments. Since we have no proposals on
our agenda before ODF 1.2 is completed, we should be able to make some
good progress here. I would however suggest that we during our
discussion focus on those comments that may have an influence on either
ODF 1.2, or an ODF 1.0 errata.

Best regards

Michael

-- 
Michael Brauer, Technical Architect Software Engineering
StarOffice/OpenOffice.org
Sun Microsystems GmbH             Nagelsweg 55
D-20097 Hamburg, Germany          michael.brauer@sun.com
http://sun.com/staroffice         +49 40 23646 500
http://blogs.sun.com/GullFOSS

Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1,
	   D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering





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