W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1658] New: [FS] editorial: 4.7.2 Other Direct Constructors

From: <bugzilla@wiggum.w3.org>
Date: Sat, 16 Jul 2005 04:30:56 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DteKG-00050Z-2D@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1658

           Summary: [FS] editorial: 4.7.2 Other Direct Constructors
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Formal Semantics
        AssignedTo: simeon@us.ibm.com
        ReportedBy: jmdyck@ibiblio.org
         QAContact: public-qt-comments@w3.org


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 '&amp;' 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."
Received on Saturday, 16 July 2005 04:30:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC