document #233

Minor Typographical Errors

Added by Michael Beckerle over 4 years ago. Updated 19 days ago.

Status:submitted Start date:10/16/2014
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:DFDL v1.0
Document Type:Proposed Recommendation

Description

(This tracker replaces 232 which was deleted by mistake.)

Section 13.6. Typos:

textNumberCheckPolicy:
On unparsing the pattern is always followed and follow the rules in 13.6.2 Converting logical numbers to/from text representation.

textStandardDecimalSeparator:
Defines the a whitespace separated ...

History

Updated by Michael Beckerle over 4 years ago

Section 23.5.4: Incorrect examples.

dfdl:hexBinary (-2084) is the hexBinary value "F7FF"
This should be "F7DC"

dfdl:hexBinary (208) is the hexBinary value "D0"
This should be "00D0" as the arg is treated as signed so xs:short.
Perhaps the two examples for 208 should become:
dfdl:hexBinary (208) is the hexBinary value "00D0"
dfdl:hexBinary (xs:unsignedByte(208)) is the hexBinary value "D0"

Updated by Steve Hanson over 4 years ago

dfdl:choiceChoiceBranchKey appears a couple of times

Updated by Steve Hanson about 4 years ago

a) Broken links in sections 6.3.1.4 and 33.1; should be to Table 2 in section 6.3.1.2.
b) Missing bullets in section 12.3.6 (endOfparent) when listing what a simple element must have one of.
c) Bullet indentation in section 22 not correct for dfdl:textNumberRounding and dfdl:calendarPatternKind

Updated by Steve Hanson about 4 years ago

Section 16.4 "Uncertaintyfor"

Updated by Steve Hanson about 4 years ago

Section 14.2. Errors in paragraph:

"However, the WSP* entity cannot appear on its own as one of the string literals in the list when determining the length of a component by scanning for delimiters, , and it is a schema definition error otherwise. delimiters"

Correct as follows - sentence is split into a bullet and a sentence that applies to all bullets, to match words for terminator:

"• The WSP* entity cannot appear on its own as one of the string literals in the list when the parser is determining the length of a component by scanning for delimiters.

If the above rules are not followed it is a schema definition error."

Updated by Michael Beckerle almost 3 years ago

Sentence: "However, many statically type-correct values will still not be convertible to the result type.It is a processing error if the supplied argument value is not convertible to the constructed type."

Space needed before "It".

Updated by Michael Beckerle almost 3 years ago

Look at the reference notes/footnotes at the end of the HTML version of the spec. You'll see some odd spacing, but also there's at least one note that uses a different font size.

Updated by Michael Beckerle over 2 years ago

dfdl:choiceKind should be dfdl:choiceLengthKind in section 12.3.6

Updated by Steve Hanson over 1 year ago

  • Target version set to DFDL v1.0

Updated by Michael Beckerle over 1 year ago

The property choiceChoiceBranchKey appears in a number of places and should be choiceBranchKey.

Updated by Michael Beckerle over 1 year ago

Section 15.1.2 the second sentence ends with ",." should be "."

Updated by Michael Beckerle over 1 year ago

In section 15, in the description of choiceBranchKey, there is a font inconsistency in the 4th paragraph. Should be consistent with the rest of the description.

Updated by Steve Hanson about 1 year ago

In sections 31.2, 31.3, 31.4 the examples specify dfdl:escapeEscapeCharacter="%". Should be "%%" (with a footnote explaining that % needs escaping when used as a literal character in DFDL properties).

Updated by Steve Hanson about 1 year ago

Section 14.2.1 requires that 'Trailing or Actually Trailing' definition needs 'Trailing or Actually Trailing' to be in bold and italics.

Updated by Michael Beckerle about 1 year ago

9.3.1.1 Known-to-exist
Last 4 lines of this section should be a numbered list.

Updated by Michael Beckerle about 1 year ago

Examples in the spec use fn:string(...) function call.

However, per section 23, the xs:string(...) function is supported, but not fn:string(...).

I am not sure the difference between the two functions, but the namespace prefix matters, and we need to consistently use xs:string(...).

So change all "fn:string(" to "xs:string(".

There is a handful of such occurrences.

Updated by Michael Beckerle 9 months ago

In description of encodingErrorPolicy property, a opening single-quote is missing in sentence:

"If error' then a processing error occurs."

Updated by Michael Beckerle 9 months ago

Section 13.7.1.1 has dfdl:binaryVirtualDecimalPoint - should be dfdl:binaryDecimalVirtualPoint.

Updated by Michael Beckerle 7 months ago

Spec has "the dfdl:separatorPosition of the sequence is 'postFix'"

Should be all lower case 'postfix'.

Updated by Michael Beckerle 2 months ago

Conforming DFDL v1.0 processors must accept at least 'UTF-8'', 'UTF-16', 'UTF-16BE', 'UTF-16LE', 'ASCII', and 'ISO-8859-1' as encoding names.

Notice the double quote after UTF-8. I believe it should be a single quote.

Updated by Michael Beckerle 20 days ago

Section 10 first page introductory material ends with this paragraph:

The property description defines which schema component that the property may be specified on.
In addition all the DFDL properties may be specified on a dfdl:format annotation.

The last sentence is wrong I think. You cannot put dfdl:inputValueCalc and dfdl:outputValueCalc on dfdl:format. There are a few others also I think.
I think the last sentence should say "most" not "all" as in "In addition most DFDL properties may be specified on a dfdl:format annotation"

Updated by Michael Beckerle 19 days ago

Section 9.3.1.1
Delete phrase "...this of course implies that....". Note that there is already a correction to create numbered bullets of 3 sentences. The sentence containing this phrase will be bullet #3 of that list.

Also available in: Atom PDF