Revised document conformance text

[Chris Rae]

Good morning all - I did a bit of thinking about this at the end of last week after the call. As I mentioned on the call, it was never our intent to remove the application conformance section - this was an inadvertent editorial error on my part that I corrected in future drafts. The application conformance classes should remain.

On Murata-san's second point (removal of document conformance classes that are used later in the text), this is something that Alex and I had overlooked when working on the draft and does indeed need to be corrected. Right now there are two places that go together to define document conformance classes in IS 29500. The first is in the 2.4 Document Conformance section (which defines SML/PML/WML Strict and Transitional), and the second is in the ST_Conformance simple type (which defines the enumeration values Strict and Transitional, to apply to those classes). I don't believe that the link between them is normatively clear.

I would prefer to define conformance by using only two conformance classes (Strict and Transitional). We already have document categories for the three markups, so I think the use of independent conformance classes is duplicative. These changes can be effected by:

* Adding a bullet to the revised conformance criteria (for both Parts 1 and 4) stating that the document shall be of Strict/Transitional conformance class
* Changing the various references in the later text from ".ML Strict" to just "Strict"

Those changes are in the attached text, which includes the Document Conformance sections for both Parts 1 and 4, and then several other textual changes to Part 1.

Your thoughts,

Chris

-----Original Message-----
From: MURATA Makoto (FAMILY Given) [mailto:eb2m-mrt at asahi-net.or.jp] 
Sent: 18 July 2011 18:22
To: e-SC34-WG4 at ecma-international.org
Subject: Re: Revised document conformance text

Chris,

I strongly think that we should keep WML/PML/SML strict conformance classes.

First, we need the APPLICATION conformance calss "WML strict".
This is to allow implementations to support WML without supporting PML or SML.  (We can  start to reformulate application conformance classes, but that is going to be a long and difficult battle.)  Second, WML/PML/SML strict conformance clases appear in Part1 (PML strict in page 2793, SML strict in page 1742, and WML strict in page 198) and also in Part 4 (Page 1).

Cheers,
Makoto

-------------- next part --------------
A non-text attachment was scrubbed...
Name: DR 09-0316 changes both Parts.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 66238 bytes
Desc: DR 09-0316 changes both Parts.docx
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20110801/ff7f031c/attachment-0001.bin>