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: Conformance Clauses and NVDL

Dear TC members,

one of the action items we have to address before we can complete our
work on ODF 1.2 is a rework of the conformance clause section. This is
necessary to meet the requirements of the current OASIS TC process, 
which has been revised since ODF 1.1 was approved.

I have uploaded a proposal for reworked conformance clauses here:


Actually, the document contains multiple variants. What I did was to
take the ODF 1.1 conformance clauses, that I then reworked in multiple
steps. I call these iterations in the document.

The first iteration more or less reformulates what we had so far, but
aims to change the conformance definitions itself as little as possible.

The 2nd and 3rd iterations aim to simplify the conformance definition by
defining less variants and by omitting a few (very few) requirements.

My personal favorite is the third iteration, and I would like to use
that as basis for our discussion. What I'm particular interested in is
whether you think that this goes into the right direction, and which of
the things I omitted compared to first and second iteration should be
re-introduced. A soon as I know that my proposal goes into the right 
direction, I will move it into the Wiki.

On another but not unrelated topic: I would like propose that
we use NVDL for the inclusion of the MathML and XForms schemas. This
on the one hand would improve the ability to verify these parts of ODF
documents (right now, everything is allowed within an embedded math
object or an XForms model, what means that these parts are never
validated). But using NVDL would further resolve the issues we currently
have with RNG DTD compatibility. We may create a schema that itself is
DTD compatible together with a NVDL script that processes these parts of
the schema where we currently allow any content.

I have uploaded a first NVDL script here:


It probably requires some more work, but it shows already what
using NVDL would look like.

The use of NVDL requires a few adaptations of the schema, and there is a
dependency from the conformance clauses (and vice versa): If we still
want to differ between strict and non-strict documents, then we should
define that with the help of two NVDL scripts rather than with two
schemas. For that reason, I'm interested in knowing what the revised
conformance clauses will be before working on the details of the NVDL

One last remark: NVDL is new to me. So, any support with further
developing the script is welcome.

Best regards


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

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]