Changes for readonly enforcement are available; in many places, normative text was needed, not just "notes"

The changes associated with readonly enforcement have now been made to the 
editor's draft.

The root change was to the readonly MIP in Section 6.1.2.

However, this change implied changes to numerous other sections:

4.8.1 the getInstanceDocument() Method
8.1.1 Implementation requirements Common to all Form Controls
10.2 The setvalue Element
10.3 The insert Element
10.4 The delete Element
11.2 The xforms-submit Event
11.10 Replacing Data with the Submission Response

I do not think you will find the changes for readonly enforcement to be 
surprising, except that some had felt it
could be just a note.  As I got into the process, it was almost 
immediately clear that these did indeed need
to be normative changes.  For example, the handling of readonly occurs in 
a particular place in the insert
 and delete processing models and implies a no-op.  The handling of 
readonly on submission occurs in
a particular place in its model and is associated with a kind of target 
attribute error, implying an xforms-submit-error.

John M. Boyer, Ph.D.
STSM: Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer