This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
4.7.1.1 Attributes Notation / prodn 2 [88 (Formal)] AttributeContentUnit ::= EscapeQuot | QuotAttrValueContent Norm / rule 3 [Prefix:LocalPart S? = S? " AttributeContentUnits "]_Attribute Note that these only handle quote-delimited attributes, not apos-delimited attributes. Norm / rule 1 In the RHS, there should be a comma before the ellipsis too. Norm / rule (2|3) [[...]]_Attribute (Prefix = xmlns) [[...]]_Attribute not(Prefix = xmlns) According to 3.2.2, there's supposed to be a comma before the extra premise. Norm / rule 6 fn:codepoints-to-string(( Char | CharRef | EscapeQuot | ... )+) See bug 1629... You can't just plop down a hunk of element content as the argument in a function call: it isn't well-formed syntax. E.g., you could get something like fn:codepoints-to-string(-0A ) Instead, you could handle it like 4.7.1 / Norm / rule 5, and introduce something like []_DirCharsUnit, defined informally. (You can't just reuse []_DirCharsUnit, because the semantics aren't quite the same.) Norm / rule 7 [[ { Expr1, ..., Exprn } ]]_AttributeContentUnit The syntax of an EnclosedExpr is just { Expr }. As in Bug 3895, change the rule to just [[ { Expr } ]]_AttributeContentUnit == [[ Expr ]]_Expr
The fix for this bug does not appear in the Recommendation of 23 January 2007. It will be considered for a future publication (either an Errata document or some possible future version of the specification).
(In reply to comment #0) > > Notation / prodn 2 > [88 (Formal)] AttributeContentUnit ::= EscapeQuot | QuotAttrValueContent > Norm / rule 3 > [Prefix:LocalPart S? = S? " AttributeContentUnits "]_Attribute > Note that these only handle quote-delimited attributes, not > apos-delimited attributes. > > Norm / rule 6 > fn:codepoints-to-string(( Char | CharRef | EscapeQuot | ... )+) > See bug 1629... > You can't just plop down a hunk of element content as the argument in > a function call: it isn't well-formed syntax. E.g., you could get > something like > fn:codepoints-to-string(-0A ) > Instead, you could handle it like 4.7.1 / Norm / rule 5, and introduce > something like []_DirCharsUnit, defined informally. (You can't just > reuse []_DirCharsUnit, because the semantics aren't quite the same.) These two points have been resolved by the fix for Bug 1641 (Erratum E001).
(In reply to comment #0) > > Norm / rule 7 > [[ { Expr1, ..., Exprn } ]]_AttributeContentUnit > The syntax of an EnclosedExpr is just { Expr }. > As in Bug 3895, change the rule to just > [[ { Expr } ]]_AttributeContentUnit == [[ Expr ]]_Expr That was folded into the fix for FS erratum E031.
This issue was marked resolved-fixed in what appears to be a random act of vandalism (see http://lists.w3.org/Archives/Public/public-html/2010Mar/0375.html), so I have reopened it. By the way, the following points remain unresolved: > Norm / rule 1 > In the RHS, there should be a comma before the ellipsis too. > > Norm / rule (2|3) > [[...]]_Attribute (Prefix = xmlns) > [[...]]_Attribute not(Prefix = xmlns) > According to 3.2.2, there's supposed to be a comma before the extra > premise.