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.2 Other Direct Constructors (PI and Comment) "its character content is converted to a string as in attribute content." Then it's odd that there isn't an invocation of [[]]_AttributeContent. But really, you don't want it converted as in attribute content, because that would (e.g.) map '&' to '&' and '{{' to '{', neither of which are correct for PI or Comment content. Norm / rule 1 Char* ?>" ]]_Expr Delete stray doublequote. Norm / rule (1|2) "processing-instruction NCName { Char* }" "comment { Char* }" In general, Char* does not constitute a valid Expr, and even when it does, it doesn't denote what you want it to. Putting Char* within quotes would be a good start, but then you have to worry about quotes in the Char* that then need to be escaped. Maybe introduce a []-form to accomplish the conversion. DErr "for direct processing-instruction constructors." Append "or comment constructors."
Fixed as suggested. Added an auxiliary normalization rule to convert Char* into an appropriate string. - Jerome
re the auxiliary normalization rule... [Char*]_Characters == fn:codepoints-to-string(Char*) As in Bug 1629 (4.7.1) and Bug 3896 (4.7.1.1), this doesn't work. Instead, just define []_Characters informally, e.g. "[]_Characters takes the character content of a PI or comment constructor and yields a corresponding StringLiteral."
Fixed as suggested. - Jerome