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: Updating our charter - 21 March 2021 - Possible discussion date? Asking, not setting it.


Greetings!

A 4 Year Review of our charter is required by Section 1.10 TC Vitality
of the TC Process
(https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#tcVitality)


TC's are now required by OASIS to review their charters every four years
to "ensure the TC charter continues to align with the activities of the
TC."

I hadn't looked at our charter in a very long time and must confess that
it could be updated to reflect our progress and current goals.

I have pasted the relevant part of our charter below for your review.
(our full charter is here:
https://www.oasis-open.org/committees/office/charter.php)

I'd like to take the charter revision discussion up on 21 March 2021. If
you think we need more time, please reply to the list.

I'll make a straw man revision for people to throw rocks at, perhaps
over the weekend. Easier to reply to something than nothing.

Thanks!

Hope everyone is having a great week!

Patrick

PS: OASIS process and terminology has changed since that charter was
approved. ;-)

*****

Statement of Purpose

The purpose of this TC is to create an open, XML-based file format
specification for office applications.

The resulting file format must meet the following requirements:

1. it must be suitable for office documents containing text,
spreadsheets, charts, and graphical documents,

2. it must be compatible with the W3C Extensible Markup Language (XML)
v1.0 and W3C Namespaces in XML v1.0 specifications,

3. it must retain high-level information suitable for editing the document,

4. it must be friendly to transformations using XSLT or similar
XML-based languages or tools,

5. it should keep the document's content and layout information separate
such that they can be processed independently of each other, and

6. it should 'borrow' from similar, existing standards wherever possible
and permitted.

Scope

Since the OpenOffice.org XML format specification was developed to meet
these criteria and has proven its value in real life, this TC will use
it as the basis for its work.

A standard for office document processing and interchange will be of
great utility to many users and software companies developing
applications, and should be made available as soon as possible.

Thus, the work of this TC has been divided in two phases:

1. In the first phase, this TC has used proven and established
constructs so that the resulting standard can satisfy the immediate
needs of many users, as well as serve as a base for future, less
restricted development. The work of this TC in the first phase has
concentrated on the following areas:

1. establishing a mechanism and policy for extensions, preferably
relying on XML namespaces,

2. establishing a set of 'core' elements and attributes to be supported
by all implementations,

3. incorporating feedback from early adopters of the base specification
and fixing technical problems that may have been uncovered,

4. ensuring that the resulting specification and documentation are
consistent and of high quality.

The first phase was completed by delivering the OASIS Open Office
Specification Committee Draft 1 on 20 March, 2004.

2. In the second phase, this TC will maintain the specification
delivered in phase 1 and will extend it to encompass additional areas of
applications or users, which may also include adapting the specification
to recent developments in office applications.

The work of this TC in the second phase will additionally allow for the
following areas:

1. enabling additional areas of application,

2. exploring new or experimental ideas for office document
representation, and

3. extending the expressiveness of the format.

The TC intends to submit completed and approved work to other
organizations in accordance with the OASIS Liaison Policy, and when
doing so intends to continue responsibility for the maintenance of its
specifications.

List of Deliverables

Each of the TC's phases will result in a Committee Specification that
includes:

* a set of XML DTDs/schemas setting the vocabulary, constraints and
semantics of the file format in question, and

* a set of written specifications that describe the elements and
attributes of the DTDs/schemas in plain English.

The TC has delivered a first Committee Draft on 20 March, 2004.

The TC aims to deliver a second Committee Draft in November 2004 and
aims to submit this Committee Draft for balloting by OASIS membership
for OASIS standard status.

The TC aims to deliver additional Committee Drafts throughout the second
phase every six months in March/September. If one of these Committee
Drafts contains substantial changes from the last Committee Draft that
has OASIS standard status, the TC shall submit this Committee Draft for
balloting by OASIS membership for OASIS standard status.

**********

-- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau 



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