Re: XForms 1.1 spec editor's drafts now available on public page

Hello John,

great work. Alas, some typos and other minor issues popped up during
fine reading. Maybe some of these are contained in XForms 1.0 editions
too, but I didn't check this.

"3.3 The XForms Core Module"

The table contains a wrong attribute definition for the submission
element. It says: "... method
("post"|"get"|"put"|delete|"form-data-post"|"urlencoded-post"|QNameButNotNCNAME)

..."

The word delete should have double quotes, since it is a fixed value
instead of a type.

"3.3.1 The model Element"

The sentence "This element is not an XForms Action, and has no
predefined behavior event-based behavior." has too many behaviors ;-)
Remove "behavior" after "predefined".

"3.3.2 The instance Element"

In the description of the resource attribute there is the sentence "If
the host language may treat failure to traverse the link as an exception
(4.5.2 The xforms-link-exception Event).", which is not really
understandable. Remove "If".

"4.5.5 The xforms-version-exception Event"

For this event's context information a property "errorinformation" is
defined. Shouldn't this be named "error-information" instead to be
consistent with the naming scheme of other event's properties (like
"resource-uri" or "error-message")?

"4.6.1 For input, secret, textarea, range, or upload Controls"

The first bullet says "... has the "incremental="true" setting ...", the
second "... does not have the "incremental=true" setting". The double
quotes for the incremental attribute have to be fixed, and it should be
set in <code>-markup.

"4.6.3 For select or select1 Controls"

Same as above.

"7.6 The XForms Function Library"

Replace "xforms-binding exception" with "xforms-binding-exception" in
the last sentence.

"7.8.5 The index() Function"

The second sentence "if the specified argument ..." should start uppercase.

"7.9.4 The digest() Function"

All three expamples for this extension function still show
"hash-encode". Replace with "digest".

"8.1.5 The output Element"

There are two Description paragraphs provided here. They are similar but
not identical. The second one seems more accurate, so please delete the
first one.

"8.3.1 The filename Element"

In the description of a then following example
"mail/attachment@filename" and "mail/attachment@mediatype" refer to
attribute nodes. The correct XPath syntax "mail/attachment/@filename"
and "mail/attachment/@mediatype" should be used.

"9.3.1 The repeat Element"

In the paragraph after the special attributes description the second
sentence "if an element of the collection ..." should start uppercase.

"9.3.5 The insert Action"

The 5th example ("Inserting into a repeat, whether or not it is empty")
refers to "repeat R". In the code snippet there is a call to index()
function in <xf:insert ... at="index('R')"/> as well as a <xf:setfocus
control="R"/>. However, the repeat is missing id="R" which might confuse
readers. Maybe it could even be renamed to something more
self-explanatory, e.g. "PurchaseOrderRepeat".

"9.3.7 The setindex Element"

In the paragraph after the special attributes description the third
sentence "if the index evaluates to NaN ..." should start uppercase.

"9.3.8 Repeat Processing"

In list item 2. the second sentence "if the initial startindex ..."
should start uppercase.

"10.10.2 Processing of the load Action"

In the second paragraph "... link between th load element and the remote
resource" replace "th " with "the ".

"10.15 Iteration of XForms Actions"

I don't speak English natively, but the sentence "Counter and Accumlator
Variables are Created in Instance Data to Sum a Selection of Values
Chosen by the User" hurts my eyes. Shouldn't this simply be "Counter and
accumlator variables are created in instance data to sum a selection of
values chosen by the user." ??

"11.2 The xforms-submit Event"

In "The response returned from the submission is applied as follows:"
list, the second bullet's second sentence "if the parse fails ..."
should start uppercase.

"11.19.3 SOAP HTTP Binding"

In the second list the first bullet "the Content-type HTTP header is
change to text/xml" should be changed to contain "changed".

Regards,
Uli.
-- 
Ulrich Nicolas Lissé

Received on Monday, 4 June 2007 22:10:59 UTC